NIST 800-53: Cloud Security Controls
AWS 58 automated checks
Security and privacy controls mapped to NIST SP 800-53 Rev. 5 for AWS resources
Access Control (AC)
- IAM root user must not have access keys
- IAM group should be used for permission management
- IAM policy must be attached and in use
- S3 bucket must block public ACLs
- Organization should establish access control policies (AC-1)
- Organization should manage information system accounts (AC-2)
- Organization should enforce separation of duties (AC-5)
Audit & Accountability (AU)
Audit and Accountability (AU)
Awareness & Training (AT)
Awareness and Training (AT)
Configuration Management (CM)
Contingency Planning (CP)
Identification & Authentication (IA)
Incident Response (IR)
Planning (PL)
Program Management (PM)
Risk Assessment (RA)
Security Assessment (CA)
System & Communications Protection (SC)
- Load balancer listener must use a secure SSL policy
- CloudFront distribution must use TLS 1.2 minimum
- Elasticsearch domain must enforce HTTPS
- ElastiCache replication group must have in-transit encryption enabled
- Security group must not allow unrestricted ingress (0.0.0.0/0)
- RDS instance must not be publicly accessible
- Redshift cluster must not be publicly accessible
- S3 bucket must block all public access
- EKS cluster must disable public API endpoint access
- Lambda function should be deployed in a VPC
- S3 bucket encryption should use SSE-KMS with a customer-managed key
- RDS instance must have storage encryption enabled
- EBS volume must be encrypted
- DynamoDB table must have server-side encryption enabled
System & Information Integrity (SI)
System and Services Acquisition (SA)
Measure your NIST 800-53: Cloud Security Controls posture
CGPulse maps live Azure and AWS findings to these controls and tracks drift over time.