feat: ramparts-to-ave crosswalk + numbering-mismatch caution - #147
Merged
Merged
Conversation
From issue #138's mechanism-level verification, not label matching. Also documents the MCP01-MCP10 numbering-mismatch caution discovered during that verification in scaling-and-governance.md, so the lesson outlives one closed issue.
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.
Ten mechanism-verified matches from issue #138. Includes the near-miss (CommandInjection) and bidirectional gaps in the
notefield rather than as mappings, since they're not confirmed matches. Also adds a durable caution toscaling-and-governance.mdabout OWASP MCP Top 10 numbering not being stable across independently-drafted crosswalks, referencing #138 as the concrete case that surfaced it.Summary
crosswalks/ramparts-to-ave.json: ten Ramparts findings mapped to nine AVE records (EnvironmentVariableLeakagesplits across two AVE mechanisms depending on which internal condition fires). All titles, the record count (76), static_record_count (57), and ramparts' commit SHA pulled live, not typed from memory.docs/specs/scaling-and-governance.mdSection 4 (new): the MCP01-MCP10 numbering-mismatch caution -- Ramparts' MCP03 (Excessive Agency) and AVE's MCP03 (Tool Poisoning) are unrelated despite sharing a number, since OWASP's MCP Top 10 isn't formally ratified yet and gets independently interpreted by early adopters. States the rule this crosswalk had to follow: match by category meaning, never by tag number.Test plan
python3 scripts/validate_crosswalks.py-- 5/5 valid,ramparts-to-ave.jsonresolves clean againstschema/crosswalk-1.0.0.schema.jsonpython3 scripts/validate_records.py-- 76/76 records valid (unaffected, no record changes in this PR)pytest tests/ -x -q-- 305 passed