Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account
SEC08-BP03 Automate data at rest protection - AWS Well-Architected Framework
Implementation guidance Resources

SEC08-BP03 Automate data at rest protection

PDFRSS

Use automation to validate and enforce data at rest controls.  Use automated scanning to detect misconfiguration of your data storage solutions, and perform remediations through automated programmatic response where possible.  Incorporate automation in your CI/CD processes to detect data storage misconfigurations before they are deployed to production.

Desired outcome: Automated systems scan and monitor data storage locations for misconfiguration of controls, unauthorized access, and unexpected use.  Detection of misconfigured storage locations initiates automated remediations.  Automated processes create data backups and store immutable copies outside of the original environment.

Common anti-patterns:

  • Not considering options to enable encryption by default settings, where supported.

  • Not considering security events, in addition to operational events, when formulating an automated backup and recovery strategy.

  • Not enforcing public access settings for storage services.

  • Not monitoring and audit your controls for protecting data at rest.

Benefits of establishing this best practice: Automation helps to prevent the risk of misconfiguring your data storage locations. It helps to prevent misconfigurations from entering your production environments. This best practice also helps with detecting and fixing misconfigurations if they occur. 

Level of risk exposed if this best practice is not established: Medium

Implementation guidance 

Automation is a theme throughout the practices for protecting your data at rest. SEC01-BP06 Automate deployment of standard security controls describes how you can capture the configuration of your resources using infrastructure as code (IaC) templates, such as with AWS CloudFormation.  These templates are committed to a version control system, and are used to deploy resources on AWS through a CI/CD pipeline.  These techniques equally apply to automating the configuration of your data storage solutions, such as encryption settings on Amazon S3 buckets.  

You can check the settings that you define in your IaC templates for misconfiguration in your CI/CD pipelines using rules in AWS CloudFormation Guard.  You can monitor settings that are not yet available in CloudFormation or other IaC tooling for misconfiguration with AWS Config.  Alerts that Config generates for misconfigurations can be remediated automatically, as described in SEC04-BP04 Initiate remediation for non-compliant resources.

Using automation as part of your permissions management strategy is also an integral component of automated data protections. SEC03-BP02 Grant least privilege access and SEC03-BP04 Reduce permissions continuously describe configuring least-privilege access policies that are continually monitored by the AWS Identity and Access Management Access Analyzer to generate findings when permission can be reduced.  Beyond automation for monitoring permissions, you can configure Amazon GuardDuty to watch for anomalous data access behavior for your EBS volumes (by way of an EC2 instance), S3 buckets, and supported Amazon Relational Database Service databases.

Automation also plays a role in detecting when sensitive data is stored in unauthorized locations. SEC07-BP03 Automate identification and classification describes how Amazon Macie can monitor your S3 buckets for unexpected sensitive data and generate alerts that can initiate an automated response.

Follow the practices in REL09 Back up data to develop an automated data backup and recovery strategy. Data backup and recovery is as important for recovering from security events as it is for operational events.

Implementation steps

  1. Capture data storage configuration in IaC templates.  Use automated checks in your CI/CD pipelines to detect misconfigurations.

    1. You can use for AWS CloudFormation your IaC templates, and AWS CloudFormation Guard for checking templates for misconfiguration.

    2. Use AWS Config to run rules in a proactive evaluation mode. Use this setting to check the compliance of a resource as a step in your CI/CD pipeline before creating it.

  2. Monitor resources for data storage misconfigurations.

    1. Set AWS Config to monitor data storage resources for changes in control configurations and generate alerts to invoke remediation actions when it detects a misconfiguration.

    2. See SEC04-BP04 Initiate remediation for non-compliant resources for more guidance on automated remediations.

  3. Monitor and reduce data access permissions continually through automation.

    1. IAM Access Analyzer can run continually to generate alerts when permissions can potentially be reduced.

  4. Monitor and alert on anomalous data access behaviors.

    1. GuardDuty watches for both known threat signatures and deviations from baseline access behaviors for data storage resources such as EBS volumes, S3 buckets, and RDS databases.

  5. Monitor and alert on sensitive data being stored in unexpected locations.

    1. Use Amazon Macie to continually scan your S3 buckets for sensitive data.

  6. Automate secure and encrypted backups of your data.

    1. AWS Backup is a managed service that creates encrypted and secure backups of various data sources on AWS.  Elastic Disaster Recovery allows you to copy full server workloads and maintain continuous data protection with a recovery point objective (RPO) measured in seconds.  You can configure both services to work together to automate creating data backups and copying them to failover locations.  This can help keep your data available when impacted by either operational or security events.

Resources

Related best practices:

Related documents:

Related examples:

Related tools:

Need help?

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.