fix: remove duplicate 9.4.3 control#582
Merged
jmanico merged 1 commit intoOWASP:mainfrom Mar 24, 2026
Merged
Conversation
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
approved these changes
Mar 24, 2026
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 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 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 was a subset and is removed.
closes #577