Macie finds personal data in a bucket that may be publicly accessible.
Notify the owner and correct unnecessary exposure.
Which governance approach is most appropriate?
Route Macie findings to an event workflow for owner notification, classification, policy correction, and retesting.
Detailed explanation
Discovery leads to a tracked correction, isolation, and verification path.
Discovery leads to a tracked correction, isolation, and verification path.
API history does not inspect object contents.
API history does not inspect object contents.
Evidence and business data may be lost without correcting the permission.
Evidence and business data may be lost without correcting the permission.
The exposure continues despite detection.
The exposure continues despite detection.
Check official documentation
Compare the following points with the official documentation.
Amazon Macie findings、EventBridge、S3 public access blockの公式説明を確認する。
What to confirm
検出結果の保存だけと、是正まで含むプライバシー運用の違いを説明できる。
Key points
- Macie findings
- PII
- EventBridge
- Public access block
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Automation boundary
Automatically block high-risk exposure and route business-sensitive changes for approval.
Prevention
Apply discovery and tagging to new buckets, copies, and permission changes as well.