Personal information and public data are mixed in S3.
Apply encryption, retention, and access controls according to data importance.
What should be defined first?
Define data classifications and handling levels, then map each classification to encryption, retention, access, and audit controls.
Detailed explanation
Classification based on sensitivity and regulation provides the basis for subsequent controls.
Classification based on sensitivity and regulation provides the basis for subsequent controls.
Compute instance type is not a data-classification criterion.
Compute instance type is not a data-classification criterion.
A DNS name does not express data sensitivity or handling requirements.
A DNS name does not express data sensitivity or handling requirements.
TTL controls delivery caching and does not classify stored data.
TTL controls delivery caching and does not classify stored data.
Check official documentation
Compare the following points with the official documentation.
AWS data classification and data protection best practicesの公式説明を確認する。
What to confirm
データ分類が後続のセキュリティ制御の基準になる理由を説明できる。
Key points
- Data classification
- Confidentiality
- Retention policy
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current behavior in the official SOA-C03 guide and AWS service documentation.
Foundation review
Control mapping
A classification is useful when it consistently drives technical and operational controls.
Mixed data
Different classifications may require separation or fine-grained access within a shared store.