Public, internal, confidential, and personal data are stored in S3.
Apply different encryption, retention, access, and audit rules by classification.
Which governance approach is most appropriate?
Register classification and ownership as metadata and connect the values to access, encryption, retention, and audit policies.
Detailed explanation
Copies and renames can lose a name-based label.
Copies and renames can lose a name-based label.
Sensitive and public data cannot be distinguished.
Sensitive and public data cannot be distinguished.
Protection and handling requirements can be applied consistently to each asset.
Protection and handling requirements can be applied consistently to each asset.
An API event does not describe data sensitivity or ownership.
An API event does not describe data sensitivity or ownership.
Check official documentation
Compare the following points with the official documentation.
AWS data classification、Lake Formation LF-Tags、Amazon Macieの公式説明を確認する。
What to confirm
名前規則と分類メタデータをポリシーへ連動するガバナンスの違いを説明できる。
Key points
- Data classification
- Owner
- LF-Tag
- Policy
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Responsibility
Separate owners, custodians, users, and exception approvers.
Discovery
Use Macie or other checks to find unclassified or misclassified assets.