Back to Security and compliance
CIS Controls v8
456 complying controls out of 456
Last synchronised :
The counter is the one produced by our continuous monitoring platform Aikido Security, and the detail lists the controls it reports as satisfied. The two figures may differ slightly.
Assessment, type and control names are those of the original frameworks.
Request the security audit report
Applies the least privilege principle for cloud resource
| Control | Status |
|---|---|
| Access Approval is enabled for the project | complying |
| AKS local admin account is still enabled | complying |
| Compute instances have OS Login enabled | complying |
| Dangerous Impersonate permission given to ServiceAccount or node | complying |
| GKE clusters have the Kubernetes Dashboard disabled | complying |
| Kubernetes pods are isolated | complying |
| No instance uses the default service account | complying |
| No user has both the Service Account User and Service Account Admin role | complying |
| Project-wide SSH keys are blocked | complying |
| Service accounts have strict access permissions | complying |
| ServiceAccount or node can read all secrets | complying |
| VM instances have strict access permissions | complying |
Applies the least privilege principle for cloud users
| Control | Status |
|---|---|
| Firewall rules restrict public ingress to port 636 | complying |
| Users are logging in securely | complying |
| Users are only allowed to use corporate emails | complying |
Applies the least privilege principle to cloud resources
| Control | Status |
|---|---|
| Access to BigQuery datasets are restricted | complying |
| AKS API server does not limit access by IP ranges | complying |
| Amazon EKS Clusters public endpoints should not allow traffic from any IP | complying |
| API Gateway endpoints do not require an API key or authorization | complying |
| AWS EKS Node groups have implicit SSH access from any IP | complying |
| Azure Cognitive Services allows unrestricted public network access | complying |
| Azure Cosmos DB is publicly reachable | complying |
| Azure Key Vault allows public network access | complying |
| Azure Storage Account allow public access | complying |
| Azure Storage blobs do not restrict public access for nested items | complying |
| BigQuery table is anonymously or publicly accessible | complying |
| Cloud functions are not publicly accessible | complying |
| Cloud functions have strict access policies | complying |
| Cloud Storage bucket does not enforce public access prevention | complying |
| Cloud Storage bucket does not enforce uniform bucket-level access | complying |
| Cloud Storage bucket is publicly accessible | complying |
| Dataproc cluster is anonymously or publicly accessible | complying |
| Default network exists in GCP project | complying |
| Firewall rule prevents Docker API access from anywhere | complying |
| Firewall rule prevents RDP access from anywhere | complying |
| Firewall rule prevents SSH access from anywhere | complying |
| Firewall rules allow RDP access from any public IP | complying |
| Firewall rules allow SSH from any public IP | complying |
| Firewall rules allow SSH from any public IP | complying |
| Firewall rules allow unrestricted RDP access | complying |
| Firewall rules allow unrestricted SSH access | complying |
| Firewall rules do not allow unrestricted ingress to all ports and protocols | complying |
| Firewall rules restrict public ingress to port 23 | complying |
| Firewall rules restrict public ingress to port 2379 | complying |
| Firewall rules restrict public ingress to port 3000 | complying |
| Firewall rules restrict public ingress to port 5500 | complying |
| Firewall rules restrict public ingress to port 5800 | complying |
| Key Vault is publicly accessible | complying |
| KMS cryptographic key policy allows public access | complying |
| KMS keys have strict access permissions | complying |
| Kubernetes dashboard might be deployed | complying |
| Kubernetes master endpoint is not publicly available | complying |
| Profiling endpoint automatically exposed on /debug/pprof | complying |
| Pub/Sub topic is anonymously or publicly accessible | complying |
| S3 bucket grants public access to all contents | complying |
| S3 Buckets should have block public access globally | complying |
| SQL instance root user has strict access permissions | complying |
| SQL instances do not have a public IP assigned | complying |
| SQL instances have strict access permission | complying |
| SQL Server is publicly reachable | complying |
| Storage Buckets have proper access rules | complying |
| Storage buckets have public access prevention enabled | complying |
| Vertex AI notebook instance has a public IP address | complying |
Enabled security logging for cloud instances
| Control | Status |
|---|---|
| Cloud SQL instances have deletion protection enabled | complying |
| Deletion protection is disabled for RDS database | complying |
| VM instances have deletion protection enabled | complying |
Enforces encryption of data in transit
| Control | Status |
|---|---|
| API Gateway stages are not using TLS 1.2 or higher | complying |
| App does not validate SSL certificates properly | complying |
| App uses an outdated TLS protocol | complying |
| App uses an outdated TLS protocol | complying |
| AWS ElastiCache Replication Group should encrypt data in transit and enable Redis AUTH | complying |
| Azure Network Security Rule allows plaintext HTTP connections | complying |
| Azure Network Security Rule allows plaintext HTTP connections | complying |
| Azure Storage Account allows plaintext HTTP connections | complying |
| Azure Storage Account allows plaintext HTTP connections | complying |
| Azure Storage Accounts does not enforce latest TLS version | complying |
| Cloud functions require HTTPS invocations | complying |
| Cloud SQL db not enforcing SSL | complying |
| Cloud SQL instance requires SSL connections | complying |
| Cookie missing HttpOnly flag | complying |
| Deprecated SSL Protocol Usage Detected | complying |
| Deprecated SSL Protocol Usage Detected | complying |
| DNSSEC is disabled | complying |
| DNSSEC is enabled for all managed zones | complying |
| Domain SSL Certificate Expiration | complying |
| Elasticsearch domain might have outdated TLS version | complying |
| Express is not emitting security headers | complying |
| Firewall rules restrict public ingress to port 2484 | complying |
| Firewall rules restrict public ingress to port 636 | complying |
| HSTS header has malformed content | complying |
| HSTS header has malformed Max-Age directive | complying |
| HSTS header is defined via meta tag | complying |
| HSTS header is disabled | complying |
| HSTS header is malformed directive | complying |
| HSTS header is missing | complying |
| HTTP Client misconfigured with SSL validation disabled | complying |
| Insecure gRPC connection can lead to remote code execution | complying |
| Insecure gRPC connection can lead to remote code execution | complying |
| Insecure HTTP Request detected | complying |
| Insecure TLS configuration detected | complying |
| Insecure usage of `requests` sends data over cleartext | complying |
| Insecure websocket connection sends data over cleartext | complying |
| Laravel cookies can be sent unencrypted | complying |
| Load balancer allows invalid HTTP headers | complying |
| Load balancer allows unencrypted or encrypted traffic with outdated TLS policy | complying |
| Load Balancers only accept HTTPS connections | complying |
| Multiple HSTS headers are being set | complying |
| NodeJS talks to database without encryption | complying |
| NodeJS talks to database without encryption | complying |
| Outbound Ansible connections are not encrypted | complying |
| Outbound Ansible connections are not encrypted | complying |
| Server certificates are not verified during SSL/TLS connections | complying |
| Server hostnames not verified during SSL/TLS connections | complying |
| Signature validation for dnf packages is off | complying |
| SQS queue data is not encrypted | complying |
| SSL certificate verification turned off during requests | complying |
| SSL certificate verification turned off during requests | complying |
| Storage account does not enforce HTTPS-only traffic | complying |
| TLS Certificate Validation Disabled | complying |
| TLS Certificate Validation Disabled | complying |
| TLS not enforced with valid HSTS header | complying |
| Turning off TLS verification enables man-in-the-middle attacks | complying |
| Usage of deprecated or broken encryption detected | complying |
| Use of broken or outdated encryption | complying |
| Use of broken or outdated encryption | complying |
| Use of broken or outdated encryption | complying |
| Using potentially unsafe FTP connections to move data | complying |
| Using potentially unsafe FTP connections to move data | complying |
| Weak SSL/TLS protocols used | complying |
Encrypts data at rest
| Control | Status |
|---|---|
| Amazon EKS Clusters should have secrets encryption enabled | complying |
| API Gateway REST API caching is unencrypted | complying |
| AWS ElastiCache Redis cluster should have encryption at rest enabled | complying |
| Docker image repository not encrypted at rest | complying |
| Elasticsearch domain is not encrypted at rest | complying |
| Ensure all data stored in the RDS is securely encrypted at rest | complying |
| KMS keys have key rotation enabled | complying |
| SNS topics are not encrypted at rest | complying |
| SQS queue data is not encrypted | complying |
| Virtual Machines have confidential computing enabled | complying |
Enabled security logging for cloud instances
| Control | Status |
|---|---|
| Amazon EKS Clusters should have control plane logging enabled | complying |
| Audit Configuration logging is enabled | complying |
| Logging and alerts are enabled for Project Ownership assignments | complying |
| Storage Permissions logging is enabled | complying |
| VPC Firewall has Rule logging enabled | complying |
Threat detection is enabled
| Control | Status |
|---|---|
| Alerting policies have a notification channel configured | complying |
Enforces encryption of data in transit
| Control | Status |
|---|---|
| Access to BigQuery datasets are restricted | complying |
| AKS API server does not limit access by IP ranges | complying |
| Amazon EKS Clusters public endpoints should not allow traffic from any IP | complying |
| Azure Cognitive Services allows unrestricted public network access | complying |
| Compute instances do not have public IP addresses | complying |
| Firewall rule prevents Docker API access from anywhere | complying |
| Firewall rules allow unrestricted RDP access | complying |
| Firewall rules allow unrestricted SSH access | complying |
| Firewall rules do not allow unrestricted ingress to all ports and protocols | complying |
| Firewall rules restrict public ingress to port 11214 | complying |
| Firewall rules restrict public ingress to port 11215 | complying |
| Firewall rules restrict public ingress to port 135 | complying |
| Firewall rules restrict public ingress to port 137 | complying |
| Firewall rules restrict public ingress to port 138 | complying |
| Firewall rules restrict public ingress to port 139 | complying |
| Firewall rules restrict public ingress to port 1433 | complying |
| Firewall rules restrict public ingress to port 1434 | complying |
| Firewall rules restrict public ingress to port 23 | complying |
| Firewall rules restrict public ingress to port 2379 | complying |
| Firewall rules restrict public ingress to port 2383 | complying |
| Firewall rules restrict public ingress to port 2484 | complying |
| Firewall rules restrict public ingress to port 27017 | complying |
| Firewall rules restrict public ingress to port 27018 | complying |
| Firewall rules restrict public ingress to port 27019 | complying |
| Firewall rules restrict public ingress to port 3000 | complying |
| Firewall rules restrict public ingress to port 3020 | complying |
| Firewall rules restrict public ingress to port 3306 | complying |
| Firewall rules restrict public ingress to port 389 | complying |
| Firewall rules restrict public ingress to port 4505 | complying |
| Firewall rules restrict public ingress to port 4506 | complying |
| Firewall rules restrict public ingress to port 5500 | complying |
| Firewall rules restrict public ingress to port 5800 | complying |
| Firewall rules restrict public ingress to port 61621 | complying |
| Firewall rules restrict public ingress to port 636 | complying |
| Firewall rules restrict public ingress to port 7001 | complying |
| Firewall rules restrict public ingress to port 8000 | complying |
| Firewall rules restrict public ingress to port 9200 | complying |
| Firewall rules restrict public ingress to port 9300 | complying |
| Kubernetes master endpoint is not publicly available | complying |
| No firewall rule allows access to Open Telemtry metrics endpoint from the internet | complying |
| No firewall rule allows access to port 1720 from the internet | complying |
| No firewall rule allows cPanel access from the internet | complying |
| No firewall rule allows etcd access from the internet | complying |
| No firewall rule allows MongoDB access from the internet | complying |
| No firewall rule allows NFS access from the internet | complying |
| No firewall rule allows Telnet access from the internet | complying |
| No firewall rule allows Tomcat Cluster Receiver access from the internet | complying |
| Vertex AI notebook instance has a public IP address | complying |
Prevents unauthorized public access to database
| Control | Status |
|---|---|
| BigQuery table is anonymously or publicly accessible | complying |
| SQL instance root user has strict access permissions | complying |
| SQL instances do not have a public IP assigned | complying |
| SQL instances have strict access permission | complying |
Prevents unauthorized public access to file storage
| Control | Status |
|---|---|
| Azure Storage Account allow public access | complying |
| Azure Storage blobs do not restrict public access for nested items | complying |
| S3 bucket grants public access to all contents | complying |
| S3 Buckets should have block public access globally | complying |
| Storage Buckets have proper access rules | complying |
| Storage buckets have public access prevention enabled | complying |
Threat detection is enabled
| Control | Status |
|---|---|
| Alerting policies have a notification channel configured | complying |
Enforces encryption of data in transit
| Control | Status |
|---|---|
| Access to BigQuery datasets are restricted | complying |
| AKS API server does not limit access by IP ranges | complying |
| Amazon EKS Clusters public endpoints should not allow traffic from any IP | complying |
| Azure Cognitive Services allows unrestricted public network access | complying |
| Compute instances do not have public IP addresses | complying |
| Firewall rule prevents Docker API access from anywhere | complying |
| Firewall rules allow unrestricted RDP access | complying |
| Firewall rules allow unrestricted SSH access | complying |
| Firewall rules do not allow unrestricted ingress to all ports and protocols | complying |
| Firewall rules restrict public ingress to port 11214 | complying |
| Firewall rules restrict public ingress to port 11215 | complying |
| Firewall rules restrict public ingress to port 135 | complying |
| Firewall rules restrict public ingress to port 137 | complying |
| Firewall rules restrict public ingress to port 138 | complying |
| Firewall rules restrict public ingress to port 139 | complying |
| Firewall rules restrict public ingress to port 1433 | complying |
| Firewall rules restrict public ingress to port 1434 | complying |
| Firewall rules restrict public ingress to port 23 | complying |
| Firewall rules restrict public ingress to port 2379 | complying |
| Firewall rules restrict public ingress to port 2383 | complying |
| Firewall rules restrict public ingress to port 2484 | complying |
| Firewall rules restrict public ingress to port 27017 | complying |
| Firewall rules restrict public ingress to port 27018 | complying |
| Firewall rules restrict public ingress to port 27019 | complying |
| Firewall rules restrict public ingress to port 3000 | complying |
| Firewall rules restrict public ingress to port 3020 | complying |
| Firewall rules restrict public ingress to port 3306 | complying |
| Firewall rules restrict public ingress to port 389 | complying |
| Firewall rules restrict public ingress to port 4505 | complying |
| Firewall rules restrict public ingress to port 4506 | complying |
| Firewall rules restrict public ingress to port 5500 | complying |
| Firewall rules restrict public ingress to port 5800 | complying |
| Firewall rules restrict public ingress to port 61621 | complying |
| Firewall rules restrict public ingress to port 636 | complying |
| Firewall rules restrict public ingress to port 7001 | complying |
| Firewall rules restrict public ingress to port 8000 | complying |
| Firewall rules restrict public ingress to port 9200 | complying |
| Firewall rules restrict public ingress to port 9300 | complying |
| Kubernetes master endpoint is not publicly available | complying |
| No firewall rule allows access to Open Telemtry metrics endpoint from the internet | complying |
| No firewall rule allows access to port 1720 from the internet | complying |
| No firewall rule allows cPanel access from the internet | complying |
| No firewall rule allows etcd access from the internet | complying |
| No firewall rule allows MongoDB access from the internet | complying |
| No firewall rule allows NFS access from the internet | complying |
| No firewall rule allows Telnet access from the internet | complying |
| No firewall rule allows Tomcat Cluster Receiver access from the internet | complying |
| Vertex AI notebook instance has a public IP address | complying |
Enforces HTTPS traffic to cloud instances
| Control | Status |
|---|---|
| Load Balancers only accept HTTPS connections | complying |
Enforces latest TLS version
| Control | Status |
|---|---|
| API Gateway stages are not using TLS 1.2 or higher | complying |
| Azure Storage Accounts does not enforce latest TLS version | complying |
| Elasticsearch domain might have outdated TLS version | complying |
| Load balancer allows unencrypted or encrypted traffic with outdated TLS policy | complying |
| Storage account does not enforce HTTPS-only traffic | complying |
Uses DNSSEC extensions
| Control | Status |
|---|---|
| DNSSEC is disabled | complying |
| DNSSEC is enabled for all managed zones | complying |
Applies the least privilege principle for cloud resource
| Control | Status |
|---|---|
| Access Approval is enabled for the project | complying |
| AKS local admin account is still enabled | complying |
| Compute instances have OS Login enabled | complying |
| Dangerous Impersonate permission given to ServiceAccount or node | complying |
| GKE clusters have the Kubernetes Dashboard disabled | complying |
| Kubernetes pods are isolated | complying |
| No instance uses the default service account | complying |
| No user has both the Service Account User and Service Account Admin role | complying |
| Project-wide SSH keys are blocked | complying |
| Service accounts have strict access permissions | complying |
| ServiceAccount or node can read all secrets | complying |
| VM instances have strict access permissions | complying |
Requires MFA for access to cloud resources
| Control | Status |
|---|---|
| Users are logging in securely | complying |
Requires MFA for access to cloud resources
| Control | Status |
|---|---|
| Users are logging in securely | complying |
Requires MFA for access to cloud resources
| Control | Status |
|---|---|
| Users are logging in securely | complying |
Configured SLAs to resolve issues
| Control | Status |
|---|---|
| Configure SLAs | complying |
Enabled security logging for cloud instances
| Control | Status |
|---|---|
| Alerting policies have a notification channel configured | complying |
| Amazon EKS Clusters should have control plane logging enabled | complying |
| Audit Configuration logging is enabled | complying |
| Logging and alerts are enabled for Project Ownership assignments | complying |
| Storage Permissions logging is enabled | complying |
| VPC Firewall has Rule logging enabled | complying |
No malware issues
| Control | Status |
|---|---|
| No open malware issues | complying |
Prevents unwanted write operations to filesystems
| Control | Status |
|---|---|
| Container processes can gain more privileges than its parent | complying |
| Container running as root can allow attacker to escalate attacks | complying |
| Default Kubernetes settings allow containers to eavesdrop on traffic. | complying |
| Default security context allows pods to access host system. | complying |
| Docker container configured to run as user with root privileges | complying |
| Docker container runs as default root user | complying |
| Filesystem for docker container should not be writeable | complying |
| Privileged container can allow attackers to escalate attacks | complying |
Threat detection is enabled
| Control | Status |
|---|---|
| Alerting policies have a notification channel configured | complying |
Uses Lockfiles to pin code dependencies
| Control | Status |
|---|---|
| Use lockfiles in repos | complying |
Has backups for stateful cloud resources
| Control | Status |
|---|---|
| Databases have automated backups enabled | complying |
| DynamoDB backups are off | complying |
Enforces HTTPS traffic to cloud instances
| Control | Status |
|---|---|
| Cloud functions require HTTPS invocations | complying |
| Load Balancers only accept HTTPS connections | complying |
Prevents unauthorized public access to database
| Control | Status |
|---|---|
| BigQuery table is anonymously or publicly accessible | complying |
| Firewall rules restrict public ingress to port 1433 | complying |
| Firewall rules restrict public ingress to port 1434 | complying |
| Firewall rules restrict public ingress to port 2383 | complying |
| Firewall rules restrict public ingress to port 2484 | complying |
| Firewall rules restrict public ingress to port 27017 | complying |
| Firewall rules restrict public ingress to port 27018 | complying |
| Firewall rules restrict public ingress to port 27019 | complying |
| Firewall rules restrict public ingress to port 3306 | complying |
| Firewall rules restrict public ingress to port 61621 | complying |
| Firewall rules restrict public ingress to port 7001 | complying |
| Firewall rules restrict public ingress to port 9200 | complying |
| Firewall rules restrict public ingress to port 9300 | complying |
| No firewall rule allows MongoDB access from the internet | complying |
| SQL instance root user has strict access permissions | complying |
| SQL instances do not have a public IP assigned | complying |
| SQL instances have strict access permission | complying |
Prevents unauthorized public access to networks and instances
| Control | Status |
|---|---|
| AWS EKS Node groups have implicit SSH access from any IP | complying |
| Compute instances have OS Login enabled | complying |
| Firewall rule prevents RDP access from anywhere | complying |
| Firewall rule prevents SSH access from anywhere | complying |
| Firewall rules allow RDP access from any public IP | complying |
| Firewall rules allow SSH from any public IP | complying |
| Firewall rules allow SSH from any public IP | complying |
| Firewall rules allow unrestricted SSH access | complying |
| Project-wide SSH keys are blocked | complying |
Enforces encryption of data in transit
| Control | Status |
|---|---|
| App does not validate SSL certificates properly | complying |
| App uses an outdated TLS protocol | complying |
| App uses an outdated TLS protocol | complying |
| AWS ElastiCache Replication Group should encrypt data in transit and enable Redis AUTH | complying |
| Azure Network Security Rule allows plaintext HTTP connections | complying |
| Azure Network Security Rule allows plaintext HTTP connections | complying |
| Azure Storage Account allows plaintext HTTP connections | complying |
| Azure Storage Account allows plaintext HTTP connections | complying |
| Cloud functions require HTTPS invocations | complying |
| Cloud SQL instance requires SSL connections | complying |
| Cookie missing HttpOnly flag | complying |
| DNSSEC is disabled | complying |
| DNSSEC is enabled for all managed zones | complying |
| Express is not emitting security headers | complying |
| Firewall rules restrict public ingress to port 2484 | complying |
| Firewall rules restrict public ingress to port 636 | complying |
| HTTP Client misconfigured with SSL validation disabled | complying |
| Insecure gRPC connection can lead to remote code execution | complying |
| Insecure gRPC connection can lead to remote code execution | complying |
| Insecure HTTP Request detected | complying |
| Insecure TLS configuration detected | complying |
| Insecure usage of `requests` sends data over cleartext | complying |
| Insecure websocket connection sends data over cleartext | complying |
| Laravel cookies can be sent unencrypted | complying |
| Load balancer allows invalid HTTP headers | complying |
| Load Balancers only accept HTTPS connections | complying |
| NodeJS talks to database without encryption | complying |
| Outbound Ansible connections are not encrypted | complying |
| Outbound Ansible connections are not encrypted | complying |
| Server certificates are not verified during SSL/TLS connections | complying |
| Server hostnames not verified during SSL/TLS connections | complying |
| Signature validation for dnf packages is off | complying |
| SQS queue data is not encrypted | complying |
| TLS Certificate Validation Disabled | complying |
| TLS Certificate Validation Disabled | complying |
| Turning off TLS verification enables man-in-the-middle attacks | complying |
| Usage of deprecated or broken encryption detected | complying |
| Use of broken or outdated encryption | complying |
| Use of broken or outdated encryption | complying |
| Use of broken or outdated encryption | complying |
| Using potentially unsafe FTP connections to move data | complying |
| Using potentially unsafe FTP connections to move data | complying |
| Weak SSL/TLS protocols used | complying |
Prevents unauthorized public access to networks and instances
| Control | Status |
|---|---|
| AWS EKS Node groups have implicit SSH access from any IP | complying |
| Compute instances have OS Login enabled | complying |
| Firewall rule prevents RDP access from anywhere | complying |
| Firewall rule prevents SSH access from anywhere | complying |
| Firewall rules allow RDP access from any public IP | complying |
| Firewall rules allow SSH from any public IP | complying |
| Firewall rules allow SSH from any public IP | complying |
| Firewall rules allow unrestricted SSH access | complying |
| Project-wide SSH keys are blocked | complying |
Uses secure communications protocols
| Control | Status |
|---|---|
| API Gateway stages are not using TLS 1.2 or higher | complying |
| Azure Storage Accounts does not enforce latest TLS version | complying |
| Cloud SQL db not enforcing SSL | complying |
| Deprecated SSL Protocol Usage Detected | complying |
| Deprecated SSL Protocol Usage Detected | complying |
| Elasticsearch domain might have outdated TLS version | complying |
| Load balancer allows unencrypted or encrypted traffic with outdated TLS policy | complying |
| NodeJS talks to database without encryption | complying |
| SSL certificate verification turned off during requests | complying |
| SSL certificate verification turned off during requests | complying |
| Storage account does not enforce HTTPS-only traffic | complying |
Enabled security logging for cloud instances
| Control | Status |
|---|---|
| Alerting policies have a notification channel configured | complying |
| Amazon EKS Clusters should have control plane logging enabled | complying |
| Audit Configuration logging is enabled | complying |
| Logging and alerts are enabled for Project Ownership assignments | complying |
| Storage Permissions logging is enabled | complying |
| VPC Firewall has Rule logging enabled | complying |
Tracks progress via an issue tracker
| Control | Status |
|---|---|
| Integration with issue tracker enabled | complying |
Configured SLAs to resolve issues
| Control | Status |
|---|---|
| Configure SLAs | complying |
No risky licenses in 3rd party dependencies
| Control | Status |
|---|---|
| No risky licenses in dependencies | complying |
no_issues_outside_of_sla
| Control | Status |
|---|---|
| No issues outside of sla | complying |
Has separate production and test environments
| Control | Status |
|---|---|
| No cloud environment used for mixed purposes (eg production and staging) | complying |
Configured monitoring for code repositories
| Control | Status |
|---|---|
| Configured monitoring for all code repositories | complying |