#93: retarget the 16 ATLAS rows whose own claim restates the ATLAS definition - #116
Merged
Merged
Conversation
…finition Category A of the ruling sheet posted on #93, approved by the maintainer. These are the rows where the text the author wrote in the row matches an ATLAS technique's published description, so the retarget follows the evidence rather than a judgment: "Data Poisoning" T0032 -> T0070 RAG Poisoning "Embedding Manipulation" T0063 -> T0066 Retrieval Content Crafting "Exploit Public-Facing ML Appl." T0057 -> T0049 Exploit Public-Facing Application "Data Leakage" T0021 -> T0057 LLM Data Leakage "Information Disclosure" T0030 -> T0057 LLM Data Leakage "Spearphishing via AI" T0049 -> T0052.000 Spearphishing via Social Engineering LLM "Model Inversion" T0027 -> T0024.001 Invert AI Model "Configuration Exposure" T0041 -> T0056 Extract LLM System Prompt "LLM Capability Escalation" T0015 -> T0053 AI Agent Tool Invocation "Network Service Scanning" T0043 -> T0006.002 Scan for Exposed AI Infrastructure Each row takes the technique's official name, its DRAFT marker comes off, and the quick-reference id lists follow the detail rows of the same entry. Five techniques the rulings now cite are transcribed into the registry from ATLAS 2026.09 (52 -> 57 items). Categories B (two defensible targets, 12 rows) and C (no ATLAS counterpart, 6 rows) keep their DRAFT markers and their entries in #93. Validator: 34 -> 18 flagged rows. Mappings unchanged at 3,771; no row removed, no severity, relationship or confidence touched. Consequence to note: LLM02 now carries two AML.T0057 rows, because "Data Leakage" and "Information Disclosure" both describe LLM Data Leakage. Their notes differ and merging them would discard one, so both are left. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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
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.
Applies category A of the ruling sheet on #93. Categories B and C stay DRAFT.
What category A is
The rows where the text the author already wrote in the row matches an ATLAS technique's published description. The retarget follows that evidence rather than a judgment about what the mapping should be:
T0032(no such id)T0070RAG PoisoningT0063T0066Retrieval Content CraftingT0057T0049Exploit Public-Facing ApplicationT0021T0057LLM Data LeakageT0030(no such id)T0057LLM Data LeakageT0049T0052.000Spearphishing via Social Engineering LLMT0027(no such id)T0024.001Invert AI ModelT0041T0056Extract LLM System PromptT0015T0053AI Agent Tool InvocationT0043T0006.002Scan for Exposed AI InfrastructureEach row takes the technique's official name, its DRAFT marker comes off, and the quick-reference id lists follow the detail rows of the same entry. Five techniques these rulings now cite are transcribed into the registry from ATLAS 2026.09: 52 → 57 items.
Left DRAFT, deliberately
T0018andT0110both fit).Both keep their inline markers and their entries in #93.
One consequence worth your eye
LLM02now carries twoAML.T0057rows — "Data Leakage" and "Information Disclosure" both describe LLM Data Leakage, so the two rulings converge. Their notes differ, and merging them would discard one, so I left both. (ASI03has a similar pre-existing pair onT0024.)Verification
node scripts/validate.js: 0 errors, 327 passed.npm run test:scripts: 85 passed. Stats current, generator reproduces.🤖 Generated with Claude Code