C9.4: dedup 9.4.3 - remove generic tamper-evidence clause, keep agent-specific content#222
Merged
ottosulin merged 1 commit intoOWASP:mainfrom Mar 23, 2026
Conversation
…-specific content 9.4.3 and 14.3.2 were duplicating the tamper-evidence principle: - 9.4.3: "audit logs are tamper-evident (append-only/WORM/immutable log store) AND ..." - 14.3.2: "audit logs cannot be tampered with and include integrity verification mechanisms" Fix: Remove the generic tamper-evidence opening from 9.4.3 (covered by 14.3.2 as the general principle across all AI system audit logs). Retain what is unique to 9.4.3: the rich agent-action-specific content requirements (delegation scope, authorization decision with policy version, tool parameters, approval records, outcomes) plus the specific storage requirement (append-only/write-once) which is more prescriptive than 14.3.2's general "integrity verification mechanisms".
RicoKomenda
added a commit
to RicoKomenda/AISVS
that referenced
this pull request
Mar 24, 2026
9.4.3 was listed twice following a merge conflict between PR OWASP#222 (which removed the generic tamper-evidence clause from 9.4.3) and PR OWASP#145 (which added cryptographic hash chaining as a tamper-evidence option by inserting a new row, not replacing the existing one). Both rows covered the same requirement. The first row (introduced by PR OWASP#145) is kept as it is the more complete version: it covers all tamper-evidence mechanisms (WORM/append-only, hash chaining, equivalent guarantees) plus all agent-specific context fields. The second row (the PR OWASP#222 remnant) was a subset and is removed.
jmanico
pushed a commit
that referenced
this pull request
Mar 24, 2026
9.4.3 was listed twice following a merge conflict between PR #222 (which removed the generic tamper-evidence clause from 9.4.3) and PR #145 (which added cryptographic hash chaining as a tamper-evidence option by inserting a new row, not replacing the existing one). Both rows covered the same requirement. The first row (introduced by PR #145) is kept as it is the more complete version: it covers all tamper-evidence mechanisms (WORM/append-only, hash chaining, equivalent guarantees) plus all agent-specific context fields. The second row (the PR #222 remnant) was a subset and is removed.
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.
9.4.3 and 14.3.2 were duplicating the tamper-evidence principle:
Fix: Remove the generic tamper-evidence opening from 9.4.3 (covered by 14.3.2 as the general principle across all AI system audit logs). Retain what is unique to 9.4.3: the rich agent-action-specific content requirements (delegation scope, authorization decision with policy version, tool parameters, approval records, outcomes) plus the specific storage requirement (append-only/write-once) which is more prescriptive than 14.3.2's general "integrity verification mechanisms".