detections: AgentAvow static-analysis mappings (candidate) - #233
Open
kenneives wants to merge 1 commit into
Open
detections: AgentAvow static-analysis mappings (candidate)#233kenneives wants to merge 1 commit into
kenneives wants to merge 1 commit into
Conversation
…date) Fills the static modality, which secure-agentic-framework#227 noted has zero native mappings. AgentAvow is a static scanner (examines a tool/MCP server's artifacts without executing them). Adds a provider manifest (providers/agentavow.yml, MIT) and 46 candidate mappings across 31 Framework Model v2 techniques from 16 detection rules, spanning the supply-chain (T10xx), injection (T11xx/T14xx), credential (T15xx), recon (T16xx), lateral (T17xx), collection (T18xx) and exfiltration (T19xx) families. All relationships are partial (a static rule flags the code/config pattern that enables a technique; runtime confirms exploitation) except two composite flows marked adjacent (toxic_flow, lethal_trifecta). status: candidate for every entry per the contract — none counts as validated coverage until SAF reconciles the rule IDs and targets. rule/evidence URLs point at the public safety-model page; per-technique anchors can follow. Coverage matrix regenerated. Requested in secure-agentic-framework#222; follows the contract in secure-agentic-framework#227. Signed-off-by: Kenne Ives <kennethives@gmail.com>
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.
Following #222 and the external contribution contract merged in #227, this adds AgentAvow as the static-analysis external provider — the modality #227 flagged as having zero native mappings.
AgentAvow is a static scanner: it examines a tool / MCP server's artifacts without executing them, and emits a signed, independently-recomputable safety verdict. So its detections map into the
staticlane.What's here
detections/providers/agentavow.yml— provider manifest (MIT).detections/external-mappings.yml— 46 candidate mappings across 31 Framework Model v2 techniques from 16 detection rules, spanning supply-chain (T10xx), injection (T11xx / T14xx), credential (T15xx), recon (T16xx), lateral (T17xx), collection (T18xx) and exfiltration (T19xx).detections/COVERAGE.md.Relationship calibration — all
partial(a static rule flags the code/config pattern that enables a technique; runtime confirms exploitation), except two composite flows markedadjacent(toxic_flow,lethal_trifecta). Nothing claimeddirect.Status — every entry is
status: candidate. Per the contract, none counts as validated coverage until SAF reconciles the rule IDs and targets; SAF owns mapping integrity, AgentAvow stays authoritative for rule correctness.rule_url/evidence_urlpoint at the public safety-model page for now; per-technique anchors can follow.Validation (local):
Happy to adjust naming, relationships, or the URL granularity to whatever you prefer before reconciliation.