Back to Security and compliance
DORA
141 complying controls out of 141
Last synchronised :
The counter is the number of controls our continuous monitoring platform Aikido Security reports as satisfied, out of every control it assesses for this framework. They are all listed below, one by one.
Assessment, type and control names are those of the original frameworks.
Request the security audit report
Has deletion protection for cloud resources
| 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 |
Uses load balancers
| Control | Status |
|---|---|
| Load Balancers only accept HTTPS connections | complying |
Configured monitoring for domains
| Control | Status |
|---|---|
| Connected public facing domains | complying |
Has connected cloud environments
| Control | Status |
|---|---|
| Cloud environments are connected | complying |
Has connected code repositories
| Control | Status |
|---|---|
| Code repositories are connected | complying |
Has connected container repositories
| Control | Status |
|---|---|
| Container repositories are connected | complying |
Cloud Infrastructure Configuration
| 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 |
| Azure Cognitive Services Network ACLs do not have IP rules configured | 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 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 |
| Kubernetes master endpoint is not publicly available | complying |
| Vertex AI notebook instance has a public IP address | complying |
Data Protection and Encryption
| Control | Status |
|---|---|
| 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 Cosmos DB is publicly reachable | complying |
| Azure Key Vault allows public network access | 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 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 |
| 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 |
| Profiling endpoint automatically exposed on /debug/pprof | complying |
| Pub/Sub topic 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 |
| SQL Server is publicly reachable | complying |
Encryption at Rest Enabled
| 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 |
Enforces HTTPS traffic to cloud instances
| Control | Status |
|---|---|
| Cloud functions require HTTPS invocations | complying |
| Load Balancers only accept HTTPS connections | complying |
Identity and Access Management (IAM)
| Control | Status |
|---|---|
| Users are logging in securely | complying |
Network Security
| Control | Status |
|---|---|
| Compute instances do not have public IP addresses | 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 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 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 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 |
| 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 |
Storage and Backup Security
| Control | Status |
|---|---|
| Azure Storage Account allow public access | complying |
| Azure Storage Accounts does not enforce latest TLS version | complying |
| Azure Storage blobs do not restrict public access for nested items | complying |
| Firewall rules restrict public ingress to port 3020 | 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 |
| Storage buckets have uniform bucket-level access enabled | complying |
Use of Cryptography: Enforces SSL
| Control | Status |
|---|---|
| Cloud SQL db not enforcing SSL | complying |
| Deprecated SSL Protocol Usage Detected | complying |
| Deprecated SSL Protocol Usage Detected | complying |
| NodeJS talks to database without encryption | complying |
| SSL certificate verification turned off during requests | complying |
| SSL certificate verification turned off during requests | complying |
Use of Cryptography: Enforces TLS
| Control | Status |
|---|---|
| API Gateway stages are not using TLS 1.2 or higher | 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 |
Use of Cryptography: Secure Cookies
| Control | Status |
|---|---|
| Cookie missing HttpOnly flag | complying |
| Laravel cookies can be sent unencrypted | complying |
Cloud Resource Logging Enabled
| 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 |
Does not have any issues outside of their SLA
| Control | Status |
|---|---|
| Configure SLAs | complying |
| No critical issues outside of SLA | complying |
| No high severity issues outside of SLA | complying |
| No low severity issues outside of SLA | complying |
| No medium severity issues outside of SLA | complying |
Has email notifications set up
| Control | Status |
|---|---|
| Email notifications are enabled | complying |
Has enabled security notifications
| Control | Status |
|---|---|
| Security notifications are enabled | complying |
Has backups for stateful cloud resources
| Control | Status |
|---|---|
| Databases have automated backups enabled | complying |
Is GDPR Compliant
| Control | Status |
|---|---|
| GDPR Compliance | complying |
Does not have any issues outside of their SLA
| Control | Status |
|---|---|
| Configure SLAs | complying |
| No critical issues outside of SLA | complying |
| No high severity issues outside of SLA | complying |
| No low severity issues outside of SLA | complying |
| No medium severity issues outside of SLA | complying |
Has email notifications set up
| Control | Status |
|---|---|
| Email notifications are enabled | complying |
Has enabled security notifications
| Control | Status |
|---|---|
| Security notifications are enabled | complying |
Configured monitoring for code repositories
| Control | Status |
|---|---|
| Configured monitoring for all code repositories | complying |
Configured monitoring for container images
| Control | Status |
|---|---|
| Configured monitoring for all container images | complying |