SEC08-BP03 Automate data at rest protection
Manual data protection controls drift out of compliance as storage grows and changes. Automation enforces those controls continuously, catches misconfigurations before deployment, and remediates drift at runtime. It also creates the backups and detective coverage that protect data through operational failures and security events.
Desired outcome:
-
Your data storage locations are scanned continuously for misconfigured controls, unauthorized access, and unexpected use.
-
You remediate detected misconfigurations automatically, without waiting for a human operator.
-
Your pipelines block noncompliant storage configurations before they reach production.
-
Your automated processes create encrypted backups and store immutable copies outside the original environment.
Common anti-patterns:
-
Teams skip encrypt-by-default settings on storage services where those settings are available.
-
Teams plan backup and recovery for operational failures only, and overlook security events such as ransomware.
-
Teams leave public access settings unenforced on storage resources.
-
Teams configure controls once and never monitor or audit them for drift.
Benefits of establishing this best practice:
-
Automated checks keep misconfigured storage out of production, which shortens exposure windows.
-
Continuous monitoring detects and corrects drift that manual review would miss.
-
Immutable, off-environment backups support recovery from both operational and security events.
-
Consistent enforcement scales protection across accounts without proportional operator effort.
Level of risk exposed if this best practice is not established: Medium
Implementation guidance
Data at rest protection usually fails because someone forgets to apply a control or a later change removes it. Automation solves these problems by enforcing controls without human action. Preventive controls stop a noncompliant resource from being created. Detective controls find resources that became noncompliant after creation. Use both controls to cover the full lifecycle of a storage resource.
Infrastructure as code (IaC) is the foundation for preventive control. When storage configuration lives in version-controlled templates, you can inspect and reject noncompliant changes before deployment, which is cheaper than responding to an incident. Coverage is limited, as not every setting is expressible in a template, and resources created outside the pipeline escape this gate. Pipeline checks and runtime controls are useful checks for these issues.
Runtime monitoring tools such as
AWS Config
Amazon GuardDuty
Implementation steps
-
Define storage configuration as code and check it in the pipeline: Capture encryption, access, and public-access settings for your storage in AWS CloudFormation
or another IaC tool. Validate those templates against policy with AWS CloudFormation Guard, and run AWS Config rules in proactive mode to check a resource for compliance before it is created. -
Monitor deployed storage for configuration drift: Use AWS Config to track control changes on storage resources, and configure automatic remediation so a detected misconfiguration is corrected without manual action.
-
Continuously reduce data access permissions: Run IAM Access Analyzer
to generate findings when permissions to data or keys can be reduced, and route those findings to the team that owns the resource. -
Detect anomalous access to storage: Enable Amazon GuardDuty to alert on threat signatures and deviations from baseline access for resources such as Amazon EBS volumes, Amazon S3 buckets, and Amazon RDS databases.
-
Find sensitive data in unexpected locations: Use Amazon Macie to scan your object storage for sensitive data, and initiate an automated response when it appears where it does not belong.
-
Automate encrypted, recoverable backups: Use AWS Backup to create encrypted backups of your data sources on a schedule, and use Elastic Disaster Recovery
for continuous replication with a recovery point objective measured in seconds. Store copies outside the source environment so they survive unauthorized access to the original.
Resources
Related best practices:
Related documents:
Related videos:
Related examples:
Related tools: