Cloud Security Maturity Model·AWS v3.0.0

Drag to explore · pinch to zoom

Foundational Data protection

c2.18 Back up data and make it immutable

Ransomware makes reliable, tamper-proof backups essential. Centralize backups with AWS Backup, isolate copies in a separate account, and make them immutable with Vault Lock or a logically air-gapped vault so an attacker cannot delete or encrypt them.

Implementation guidance

Centralize with AWS Backup

AWS Backup is a managed, policy-based service that centralizes and automates backups across AWS services — Amazon EBS, EC2, RDS, DynamoDB, EFS, S3, and more — replacing per-service scripts. Define backup schedules and retention as policy, and monitor activity centrally.

Make backups immutable and isolated

Backups only help if an attacker cannot destroy them:

  • AWS Backup Vault Lock enforces WORM (write-once-read-many) immutability; in compliance mode the lock cannot be removed for the retention period.
  • Logically air-gapped vault stores immutable, encrypted copies that are locked by default and can be shared for cross-account recovery.
  • Keep backup copies in a separate account with tight access control so a compromise of the workload account does not reach them.

Scan backups for malware

An immutable backup still fails you if it already contained the ransomware. Amazon GuardDuty Malware Protection for AWS Backup scans your recovery points — EBS snapshots, EC2 AMIs, and S3 recovery points — after each backup completes, so you can restore from a copy known to be clean rather than reinfecting during recovery.

Backup on-premises to the cloud

Consider backing up on-premises infrastructure to the cloud to benefit from low-cost storage classes such as Amazon S3 Glacier. If your backup tool runs on-premises, evaluate a cloud-deployable option to avoid egress data-transfer costs.

How it fits together

Workload account EBS · EC2 RDS · DynamoDB EFS · S3 AWS Backup policy-based schedules & retention, centralized copy Separate backup account · tight access Immutable vault AWS Backup Vault Lock (WORM) compliance mode · cannot be removed Logically air-gapped vault locked by default · encrypted shareable for cross-account recovery A workload-account compromise cannot delete or encrypt these copies
AWS Backup centralizes backups across services by policy, then copies them into an immutable (Vault Lock / WORM) or logically air-gapped vault held in a separate, tightly controlled account — so a compromise of the workload account cannot delete or encrypt the backups.

Watch

Official AWS video: managing AWS Backup policies centrally across your organization with AWS Organizations, so backup schedules and retention are enforced consistently.

How to validate

  • Are you backing up your critical applications — and ideally all of them?
  • Are backups stored in a separate account with restricted access?
  • Are backups immutable (Vault Lock or logically air-gapped vault)?
  • Do your retention policy and backups meet your Recovery Point and Recovery Time Objectives (RPO/RTO)?

Threats addressed

  • Data destruction: an adversary who reaches your backups can delete them, removing your ability to recover.
  • Data encrypted for impact (ransomware): without immutable, isolated backups, encrypted production data may be unrecoverable.

AWS services

AWS Backup Amazon GuardDuty Amazon S3

Pricing

Framework mappings

AWS CAF

Well-Architected

NIST CSF

References