fix: remove duplicate C14.3.2 (tamper-evident logs)#322
Merged
ottosulin merged 1 commit intoOWASP:mainfrom Mar 23, 2026
Merged
Conversation
C14.3.2 required audit logs to be tamper-evident and include integrity verification mechanisms. This is already fully covered by C13.1.6, which requires log integrity protection via cryptographic signatures or write-only storage for all AI system logs. C14.3.2 added no unique security value: it applied the identical technical requirement (immutable/tamper-evident logs) to the same artifact (audit logs) without any meaningful scope differentiation. C13.1.6 is the authoritative general control; implementers applying C13 already satisfy the intent of C14.3.2.
RicoKomenda
force-pushed
the
fix/remove-duplicate-C14.3.2-log-integrity
branch
from
1bdf133 to
0b14c1f
Compare
ottosulin
approved these changes
Mar 23, 2026
Collaborator
ottosulin
left a comment
ottosulin
left a comment
There was a problem hiding this comment.
Agreed C13 is the right place for that control.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
C14.3.2 required audit logs to be tamper-evident and include integrity verification mechanisms. This is already fully covered by C13.1.6, which requires log integrity protection via cryptographic signatures or write-only storage for all AI system logs.
C14.3.2 added no unique security value: it applied the identical technical requirement (immutable/tamper-evident logs) to the same artifact (audit logs) without any meaningful scope differentiation. C13.1.6 is the authoritative general control; implementers applying C13 already satisfy the intent of C14.3.2.