Azure Foundation v1.1.0
CIS Benchmarks have released a new CIS Microsoft Azure Foundations Version 1.1.0. New Benchmarks for Azure are deployed in Cloudaware Compliance Engine.
Setup and Developer Console Links Permissions
Setup and Developer Console links are now viewable for admin users only. If you don't have access to them, you won't see them in the menu.
TunHub is a secure proxy connection built to link customer's assets located in private cloud to Cloudaware using Breeze Agent. Fine tune the ingress points for Breeze to access SCCM, vCenter, private JIRA, private Kubernetes Clusters and more.
G Suite Directory Integration
Cloudaware supports Google Directory API to allow you to track users who have access to your Google Cloud and Google Projects with Cloudaware G Suite Integration.
Azure Application Gateway
Azure Express Route
Azure App Service
New fields added on objects Azure VM, Google GCE Instance and CloudAware Physical server:
Zabbix: Is Monitored
Zabbix: Incidents, 30-Day
Zabbix: Memory Free, N-Day
Zabbix: Memory Total, N-Day
You can clone a policy and make updates to its code. Once the new policy is saved and/or deployed, track the history of the policy versioning and use Compare Mode for a side-to-side comparison view of policy revisions.
Diff Utility Tool
Diff Utility, the native Cloudaware Compliance Engine tool, allows you to compare two compliance policies that have a common input object. As a result, you can get a list of objects and see where the status differs.
Benchmarks Account and Application Filters
CIS Benchmark section can now be filtered by accounts and applications. Use the dropdown menu to keep track of your CIS compliance on a more granular level directly from the UI.
Compliance Engine policies can now be created according to a certain type of input and output objects.
New policies for Heroku Cloud
New Heroku Cloud polices are available in Built-In Policy Templates:
Ensure Heroku Application Custom Domains Use Secure Protocol.
Ensure Heroku Team Invite Acceptance Feature Is Turned On.
Ensure Heroku Team Member Two-Factor Authentication is Enabled.
Ensure Heroku Team Membership Capacity Is Not Near Limit.
Ensure No Heroku Applications Use Deprecated Protocol TLS 1.0.
Ensure no Heroku Private Spaces have an Unrestricted Outbound Access on All Ports.
Heroku Deprecated Stack Cedar-14 is in Use.
Heroku Services Credit Recharge Alert (1 day until expiration).
Heroku Services Credit Recharge Alert (14 days until expiration).
Heroku Services Credit Recharge Alert (7 days until expiration).
Heroku Space Peering Connection Request Expiration Alert - 24 Hours.