NIST SP 800-53 Revision 5 in Security Hub CSPM
NIST Special Publication 800-53 Revision 5 (NIST SP 800-53 Rev. 5) is a cybersecurity and compliance framework developed by the National
Institute of Standards and Technology (NIST), an agency that's part of the U.S. Department
of Commerce. This compliance framework provides a catalog of security and privacy
requirements for protecting the confidentiality, integrity, and availability of information
systems and critical resources. U.S. federal government agencies and contractors must comply
with these requirements to protect their systems and organizations. Private organizations
can also voluntarily use the requirements as a guiding framework for reducing cybersecurity
risk. For more information about the framework and its requirements, see NIST SP 800-53 Rev. 5
AWS Security Hub CSPM provides security controls that support a subset of NIST SP 800-53 Revision 5 requirements. The controls perform automated security checks for certain AWS services and resources. To enable and manage these controls, you can enable the NIST SP 800-53 Revision 5 framework as a standard in Security Hub CSPM. Note that the controls don't support NIST SP 800-53 Revision 5 requirements that require manual checks.
Unlike other frameworks, the NIST SP 800-53 Revision 5 framework isn't prescriptive about how its requirements should be evaluated. Instead, the framework provides guidelines. In Security Hub CSPM, the NIST SP 800-53 Revision 5 standard and controls represent the service's understanding of these guidelines.
Topics
Configuring resource recording for controls that apply to the standard
To optimize coverage and the accuracy of findings, it's important to enable and configure resource recording in AWS Config before you enable the NIST SP 800-53 Revision 5 standard in AWS Security Hub CSPM. When you configure resource recording, also be sure to enable it for all the types of AWS resources that are checked by controls that apply to the standard. This is primarily for controls that have a change triggered schedule type. However, some controls with a periodic schedule type also require resource recording. If resource recording isn't enabled or configured correctly, Security Hub CSPM might not be able to evaluate the appropriate resources, and generate accurate findings for controls that apply to the standard.
For information about how Security Hub CSPM uses resource recording in AWS Config, see Enabling and configuring AWS Config for Security Hub CSPM. For information about configuring resource recording in AWS Config, see Working with the configuration recorder in the AWS Config Developer Guide.
The following table specifies the types of resources to record for controls that apply to the NIST SP 800-53 Revision 5 standard in Security Hub CSPM.
| AWS service | Resource types |
|---|---|
|
Amazon API Gateway |
|
|
AWS AppSync |
|
|
AWS Backup |
|
|
Amazon Bedrock AgentCore |
|
|
AWS Certificate Manager (ACM) |
|
|
AWS CloudFormation |
|
|
Amazon CloudFront |
|
|
Amazon CloudWatch |
|
|
AWS CodeBuild |
|
|
AWS Database Migration Service (AWS DMS) |
|
|
Amazon DynamoDB |
|
|
Amazon Elastic Compute Cloud (Amazon EC2) |
|
|
Amazon EC2 Auto Scaling |
|
|
Amazon Elastic Container Registry (Amazon ECR) |
|
|
Amazon Elastic Container Service (Amazon ECS) |
|
|
Amazon Elastic File System (Amazon EFS) |
|
|
Amazon Elastic Kubernetes Service (Amazon EKS) |
|
|
AWS Elastic Beanstalk |
|
|
Elastic Load Balancing |
|
|
Amazon ElasticSearch |
|
|
Amazon EMR |
|
|
Amazon EventBridge |
|
|
AWS Glue |
|
|
AWS Identity and Access Management (IAM) |
|
|
AWS Key Management Service (AWS KMS) |
|
|
Amazon Kinesis |
|
|
AWS Lambda |
|
|
Amazon Managed Streaming for Apache Kafka (Amazon MSK) |
|
|
Amazon MQ |
|
|
AWS Network Firewall |
|
|
Amazon OpenSearch Service |
|
|
Amazon Relational Database Service (Amazon RDS) |
|
|
Amazon Redshift |
|
|
Amazon RouteĀ 53 |
|
|
Amazon Simple Storage Service (Amazon S3) |
|
|
AWS Service Catalog |
|
|
Amazon Simple Notification Service (Amazon SNS) |
|
|
Amazon Simple Queue Service (Amazon SQS) |
|
| Amazon EC2 Systems Manager (SSM) |
|
|
Amazon SageMaker AI |
|
|
AWS Secrets Manager |
|
|
AWS Transfer Family |
|
|
AWS WAF |
|
Determining which controls apply to the standard
The following list specifies the controls that support NIST SP 800-53 Revision 5 requirements and apply to the NIST SP 800-53 Revision 5 standard in AWS Security Hub CSPM. For details about specific requirements that a control supports, choose the control. Then refer to the Related requirements field in the details for the control. This field specifies each NIST requirement that the control supports. If the field doesn't specify a particular NIST requirement, the control doesn't support the requirement.
-
[Account.1] Security contact information should be provided for an AWS account
-
[Account.2] AWS accounts should be part of an AWS Organizations organization
-
[ACM.1] Imported and ACM-issued certificates should be renewed after a specified time period
-
[APIGateway.1] API Gateway REST and WebSocket API execution logging should be enabled
-
[APIGateway.3] API Gateway REST API stages should have AWS X-Ray tracing enabled
-
[APIGateway.4] API Gateway should be associated with a WAF Web ACL
-
[APIGateway.5] API Gateway REST API cache data should be encrypted at rest
-
[APIGateway.8] API Gateway routes should specify an authorization type
-
[APIGateway.9] Access logging should be configured for API Gateway V2 Stages
-
[AppSync.5] AWS AppSync GraphQL APIs should not be authenticated with API keys
-
[AutoScaling.1] Auto Scaling groups associated with a load balancer should use ELB health checks
-
[AutoScaling.2] Amazon EC2 Auto Scaling group should cover multiple Availability Zones
-
[AutoScaling.9] Amazon EC2 Auto Scaling groups should use Amazon EC2 launch templates
-
[Backup.1] AWS Backup recovery points should be encrypted at rest
-
[BedrockAgentCore.3] Bedrock AgentCore Memory should be encrypted with customer managed AWS KMS keys
-
[CloudFront.1] CloudFront distributions should have a default root object configured
-
[CloudFront.3] CloudFront distributions should require encryption in transit
-
[CloudFront.4] CloudFront distributions should have origin failover configured
-
[CloudFront.5] CloudFront distributions should have logging enabled
-
[CloudFront.6] CloudFront distributions should have WAF enabled
-
[CloudFront.7] CloudFront distributions should use custom SSL/TLS certificates
-
[CloudFront.8] CloudFront distributions should use SNI to serve HTTPS requests
-
[CloudFront.9] CloudFront distributions should encrypt traffic to custom origins
-
[CloudFront.12] CloudFront distributions should not point to non-existent S3 origins
-
[CloudTrail.2] CloudTrail should have encryption at-rest enabled
-
[CloudTrail.4] CloudTrail log file validation should be enabled
-
[CloudTrail.5] CloudTrail trails should be integrated with Amazon CloudWatch Logs
-
[CloudWatch.15] CloudWatch alarms should have specified actions configured
-
[CloudWatch.16] CloudWatch log groups should be retained for a specified time period
-
[CloudWatch.17] CloudWatch alarm actions should be activated
-
[CodeBuild.1] CodeBuild Bitbucket source repository URLs should not contain sensitive credentials
-
[CodeBuild.2] CodeBuild project environment variables should not contain clear text credentials
-
[CodeBuild.4] CodeBuild project environments should have a logging AWS Configuration
-
[Config.1] AWS Config should be enabled and use the service-linked role for resource recording
-
[DataFirehose.1] Firehose delivery streams should be encrypted at rest
-
[DMS.1] Database Migration Service replication instances should not be public
-
[DMS.6] DMS replication instances should have automatic minor version upgrade enabled
-
[DMS.7] DMS replication tasks for the target database should have logging enabled
-
[DMS.8] DMS replication tasks for the source database should have logging enabled
-
[DMS.10] DMS endpoints for Neptune databases should have IAM authorization enabled
-
[DMS.11] DMS endpoints for MongoDB should have an authentication mechanism enabled
-
[DMS.12] DMS endpoints for Redis OSS should have TLS enabled
-
[DocumentDB.1] Amazon DocumentDB clusters should be encrypted at rest
-
[DocumentDB.2] Amazon DocumentDB clusters should have an adequate backup retention period
-
[DocumentDB.3] Amazon DocumentDB manual cluster snapshots should not be public
-
[DocumentDB.4] Amazon DocumentDB clusters should publish audit logs to CloudWatch Logs
-
[DocumentDB.5] Amazon DocumentDB clusters should have deletion protection enabled
-
[DynamoDB.1] DynamoDB tables should automatically scale capacity with demand
-
[DynamoDB.2] DynamoDB tables should have point-in-time recovery enabled
-
[DynamoDB.3] DynamoDB Accelerator (DAX) clusters should be encrypted at rest
-
[DynamoDB.4] DynamoDB tables should be present in a backup plan
-
[DynamoDB.6] DynamoDB tables should have deletion protection enabled
-
[DynamoDB.7] DynamoDB Accelerator clusters should be encrypted in transit
-
[EC2.1] Amazon EBS snapshots should not be configured to be publicly restorable
-
[EC2.2] VPC default security groups should not allow inbound or outbound traffic
-
[EC2.3] Attached Amazon EBS volumes should be encrypted at-rest
-
[EC2.4] Stopped EC2 instances should be removed after a specified time period
-
[EC2.8] EC2 instances should use Instance Metadata Service Version 2 (IMDSv2)
-
[EC2.9] Amazon EC2 instances should not have a public IPv4 address
-
[EC2.13] Security groups should not allow ingress from 0.0.0.0/0 or ::/0 to port 22
-
[EC2.15] Amazon EC2 subnets should not automatically assign public IP addresses
-
[EC2.16] Unused Network Access Control Lists should be removed
-
[EC2.18] Security groups should only allow unrestricted incoming traffic for authorized ports
-
[EC2.19] Security groups should not allow unrestricted access to ports with high risk
-
[EC2.20] Both VPN tunnels for an AWS Site-to-Site VPN connection should be up
-
[EC2.21] Network ACLs should not allow ingress from 0.0.0.0/0 to port 22 or port 3389
-
[EC2.23] Amazon EC2 Transit Gateways should not automatically accept VPC attachment requests
-
[EC2.24] Amazon EC2 paravirtual instance types should not be used
-
[EC2.25] Amazon EC2 launch templates should not assign public IPs to network interfaces
-
[EC2.51] EC2 Client VPN endpoints should have client connection logging enabled
-
[EC2.55] VPCs should be configured with an interface endpoint for ECR API
-
[EC2.56] VPCs should be configured with an interface endpoint for Docker Registry
-
[EC2.57] VPCs should be configured with an interface endpoint for Systems Manager
-
[EC2.60] VPCs should be configured with an interface endpoint for Systems Manager Incident Manager
-
[ECR.1] ECR private repositories should have image scanning configured
-
[ECR.2] ECR private repositories should have tag immutability configured
-
[ECR.3] ECR repositories should have at least one lifecycle policy configured
-
[ECR.5] ECR repositories should be encrypted with customer managed AWS KMS keys
-
[ECS.2] ECS services should not have public IP addresses assigned to them automatically
-
[ECS.3] ECS task definitions should not share the host's process namespace
-
[ECS.8] Secrets should not be passed as container environment variables
-
[ECS.9] ECS task definitions should have a logging configuration
-
[ECS.10] ECS Fargate services should run on the latest Fargate platform version
-
[ECS.17] ECS task definitions should not use host network mode
-
[EFS.1] Elastic File System should be configured to encrypt file data at-rest using AWS KMS
-
[EKS.1] EKS cluster endpoints should not be publicly accessible
-
[EKS.2] EKS clusters should run on a supported Kubernetes version
-
[EKS.3] EKS clusters should use encrypted Kubernetes secrets
-
[ElastiCache.1] ElastiCache (Redis OSS) clusters should have automatic backups enabled
-
[ElastiCache.2] ElastiCache clusters should have automatic minor version upgrades enabled
-
[ElastiCache.3] ElastiCache replication groups should have automatic failover enabled
-
[ElastiCache.4] ElastiCache replication groups should be encrypted at rest
-
[ElastiCache.5] ElastiCache replication groups should be encrypted in transit
-
[ElastiCache.7] ElastiCache clusters should not use the default subnet group
-
[ElasticBeanstalk.1] Elastic Beanstalk environments should have enhanced health reporting enabled
-
[ElasticBeanstalk.2] Elastic Beanstalk managed platform updates should be enabled
-
[ELB.1] Application Load Balancer should be configured to redirect all HTTP requests to HTTPS
-
[ELB.3] Classic Load Balancer listeners should be configured with HTTPS or TLS termination
-
[ELB.4] Application Load Balancer should be configured to drop invalid http headers
-
[ELB.5] Application and Classic Load Balancers logging should be enabled
-
[ELB.6] Application, Gateway, and Network Load Balancers should have deletion protection enabled
-
[ELB.7] Classic Load Balancers should have connection draining enabled
-
[ELB.9] Classic Load Balancers should have cross-zone load balancing enabled
-
[ELB.10] Classic Load Balancer should span multiple Availability Zones
-
[ELB.13] Application, Network and Gateway Load Balancers should span multiple Availability Zones
-
[ELB.16] Application Load Balancers should be associated with an AWS WAF web ACL
-
[EMR.1] Amazon EMR cluster primary nodes should not have public IP addresses
-
[EMR.2] Amazon EMR block public access setting should be enabled
-
[EMR.3] Amazon EMR security configurations should be encrypted at rest
-
[EMR.4] Amazon EMR security configurations should be encrypted in transit
-
[ES.1] Elasticsearch domains should have encryption at-rest enabled
-
[ES.2] Elasticsearch domains should not be publicly accessible
-
[ES.3] Elasticsearch domains should encrypt data sent between nodes
-
[ES.4] Elasticsearch domain error logging to CloudWatch Logs should be enabled
-
[ES.5] Elasticsearch domains should have audit logging enabled