docs(conformance): add runtime-enforcement-mapping addendum (OWASP#802)#177
Open
docs(conformance): add runtime-enforcement-mapping addendum (OWASP#802)#177
Conversation
…ess thresholds, assumption ledger, and simulator validation (39 tests)
… T0/T1 autonomy and local buffer replay (50 tests)
…apability delegation, handoff receipts, and quorum rules (37 tests)
Maps each of the 30 ASI fixture vectors to the four runtime integrity invariants converging in OWASP#802 (transmission / authorization-at- execution / execution / intent). Rationale: - Implementations should claim coverage against a specific invariant, not the broader OWASP category — a regex heuristic is not the same conformance guarantee as a monotonic-delegation check - Keeps the cryptographic layer (deterministic) separate from the intent layer (advisory, fail-open) so conformance claims can't overclaim intent integrity as runtime-enforceable - Addresses the "pin each layer to concrete control-class IDs" suggestion raised in the thread Links companion doc from owasp-asi-mapping.md header. Refs: OWASP/www-project-top-10-for-large-language-model-applications#802 Refs: #175 (transmission-integrity fixture gap tracked separately)
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
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.
Summary
Adds
docs/conformance/runtime-enforcement-mapping.md— an invariant-level companion toowasp-asi-mapping.mdthat maps each of the 30 ASI fixture vectors to the four runtime integrity invariants converging in OWASP/www-project-top-10-for-large-language-model-applications#802.Follow-through on the commitment made in the OWASP thread to contribute this addendum.
Structure
request_authorized == request_executed.Why this matters for conformance
Implementations claiming "ASI02 coverage" should specify the invariant (
authorization-integrity-at-execution, fixtures X/Y/Z) rather than just the control ID. Intent-layer coverage should be explicitly scoped as heuristic and fail-open. This doc gives that level of granularity without changing any existingowasp-asi-mapping.mdcontent.Files changed
docs/conformance/runtime-enforcement-mapping.md(new, 130 lines)docs/conformance/owasp-asi-mapping.md(+1 line — header link to new doc)Test plan
./runtime-enforcement-mapping.mdfrom owasp-asi-mapping.md)Refs