blog: OWASP agentic top 10 — what can be enforced (publish 7/20)#779
Open
amavashev wants to merge 2 commits into
Open
blog: OWASP agentic top 10 — what can be enforced (publish 7/20)#779amavashev wants to merge 2 commits into
amavashev wants to merge 2 commits into
Conversation
Tier-2 SEO post, publish date 2026-07-20. Category-by-category enforceability verdicts (4 yes / 3 partial / 3 no) with an explicit scoring reconciliation against the framework pillar's six-of-ten count; June 2026 OWASP report data (six-of-ten injection mapping, DORA/NIS2 windows, IBM-cited 37%) attributed via Help Net Security coverage. Review cycles 1-2 + codex (2 rounds + residue fix) applied. Depends on the lethal-trifecta PR for one link.
Apply 1 / modify 0 / skip 0 (reviewer round 1, Medium finding): - The enforceability test conflated "runtime-authority enforceable" with "enforceable at all", and mislisted sandboxes as probability- reducers. Test section now scopes the question to the runtime authority layer explicitly, table column renamed "Enforceable by runtime authority?", and the "nos" paragraph states that sandboxing enforces ASI05 deterministically at a different layer (likewise channels for ASI07, disclosure design for ASI09).
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
1 participant
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
OWASP Agentic Top 10: What Can Be Enforced? — publish date 2026-07-20. Tier-2 batch post 3/5.
Category-by-category enforceability verdicts for ASI01–ASI10 (4 enforceable / 3 partial / 3 no), with an explicit scoring reconciliation against the framework pillar's "six of ten directly addressable" count (stricter test: outcome unreachable by construction). Anchored on the June 2026 OWASP State of Agentic AI Security and Governance data (six-of-ten injection mapping, DORA/NIS2 windows, IBM-cited 37% shadow-AI stat), attributed via Help Net Security coverage.
Review trail
Fact-check (ASI names cross-checked against official list + both corpus posts; "universal joint" reattributed away from the report; "two years" corrected) + set-level style agent (cross-post de-duplication) + codex ×2 + residue fix.
Merge notes
Test plan