Instiq
Chapter 5 · Data Protection·v2.0.0·Updated 6/5/2026·~10 min

What's changed: Deepened SCS-C02 Chapter 5 (added comparison tables, scenarios, FAQs, exam traps, deep-dive paragraphs to each section; localized figures to Japanese)

5.3Protecting Storage and Database Data

Key points

Understand protecting stores—S3 encryption (SSE-S3/SSE-KMS/DSSE), S3 public-access block/bucket policies, EBS/RDS encryption, backup protection, and data lifecycle. Store data securely.

Protect data stores with encryption and access control. S3 public-access prevention and encryption choices are especially common.

5.3.1Store protection

Diagram of storage/DB data protection: S3 protected by encryption (SSE-S3 = AWS-managed, SSE-KMS = CMK with auditability, DSSE = double encryption) and public-access prevention (Block Public Access, restrictive bucket policy, VPC endpoint policy); EBS/RDS encrypted at rest with KMS (snapshots encrypted too); backups protected in a separate account/region + WORM; and retention managed by lifecycle.
Protecting storage and database data
  • S3 encryption: choose from SSE-S3 (AWS-managed)/SSE-KMS (CMK, auditable)/DSSE (double).
  • S3 public-access prevention: prevent accidental exposure with Block Public Access + restrictive bucket policy.
  • EBS/RDS encryption: KMS at-rest encryption (snapshots encrypted too).
  • Backup protection: prevent tampering/deletion with a separate account/region + WORM.
Exam point

Common on SCS-C02: audit/control S3 keys = SSE-KMS, prevent accidental exposure = Block Public Access + bucket policy, EBS/RDS at-rest = KMS (incl. snapshots), backups in a separate account + WORM. Prevent S3 exposure by enabling Block Public Access at the account level.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.