A regulatory audit requests data-access and quality evidence.
Show the code version and rule version used to create the result, not only API events.
Which audit-log approach is most appropriate?
Correlate events, execution IDs, code and rule versions, manifests, and protected evidence in one traceable bundle.
Detailed explanation
A screenshot cannot prove actor, input, version, or integrity.
A screenshot cannot prove actor, input, version, or integrity.
Selective deletion violates retention and completeness.
Selective deletion violates retention and completeness.
The data, result, and processing context remain unknown.
The data, result, and processing context remain unknown.
Access, processing, quality, and output can be reconstructed and verified.
Access, processing, quality, and output can be reconstructed and verified.
Check official documentation
Compare the following points with the official documentation.
AWS CloudTrail、Glue job run、Step Functions execution、S3 Object Lockの公式説明を確認する。
What to confirm
スクリーンショットやイベント名だけと、再現可能な証拠束の違いを説明できる。
Key points
- Audit evidence
- Correlation ID
- Code version
- Manifest
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Reproducibility
Retain enough metadata to regenerate the result with the same inputs and rules.
Integrity
Protect evidence and record hashes, custodians, and retrieval time for submitted copies.