Reports for Every Cloud
Purpose-built reports that answer the questions cloud and security teams actually ask — across AWS, Azure, and Google Cloud.
58
Curated Reports
1705+
Controls Checked
3
Cloud Providers
5 min
To First Results
Container Security
18 controls
5 services covered
Checks AKS access control, authorization, Azure Policy, network policy, runtime settings, secret rotation, node density, and container registry controls such as disabled admin user, trust policy, and quarantine policy.
What we check
AKS Access Control5
- Role-Based Access Control (RBAC) should be used on Azure Kubernetes Services Cluster
- Ensure that the --authorization-mode Argument is Not Set to AlwaysAllow
- Ensure that a Client CA File is Configured
- Disable Anonymous Requests to the Kubelet Server
- Kubernetes Clusters Should Disable Automounting API Credentials
AKS Runtime Security5
- Kubernetes Clusters Should Not Grant CAPSYSADMIN Security Capabilities
- Containers Should Not Run as Root User
- Azure Kubernetes Services Cluster Key Vault Secret Rotation should be Enabled
- Azure Kubernetes Services Cluster Node Pool Should Have Maximum Number of 50 Pods
- Azure Kubernetes Services Cluster Uses Standard SKU
AKS Policy and Network4
- Azure Policy Add-on should be enabled on Azure Kubernetes Services Cluster
- Azure Kubernetes Services Cluster has Network Policy Enabled
- Kubernetes clusters HTTP application routing should be disabled
- Kubernetes clusters should have Azure network plugin
Container Registry Security3
- Container Registries Have Local Admin Account Disabled
- Container Registry Trust Policy is Enabled
- Container Registries have Quarantine Policy enabled
Container Instance Security1
- Container Instance Container Groups Use Secured Environment Variables
Run these reports on your own cloud
Connect an account and get your first set of reports in minutes — free to start, no credit card required.