Repository navigation
Conversation
Regenerated with scripts/generate-atr-galaxy.py from the rules at
agent-threat-rules v4.3.0. Every existing value keeps its UUID; 131
values are added and none removed.
Generator changes:
- add the model-security category, which ATR has had since 3.x; a rule
in it was otherwise filed under skill-compromise
- ATR 4.x lists OWASP LLM references as bare IDs ("LLM01:2025"); map
them back to "ID - name" using the 2025 Top 10 names, which also
corrects older values that carried 2023 names
- describe the galaxy without a rule count, so the text does not go
stale between refreshes
- keep the category and sub_category fields added to the galaxy file
- version 3 -> 4 for the galaxy and the cluster
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.
Refreshes the Agent Threat Rules galaxy from ATR 3.5.6 to ATR 4.3.0, regenerated with this repo's
scripts/generate-atr-galaxy.pyagainst therules/directory at thev4.3.0tag.What changes
clusters/agent-threat-rules.json: 713 -> 844 values. Every existing value keeps its UUID (UUID5 from the rule ID); 131 values are added and none are removed. Kill-chain assignments of the existing values are unchanged.relatedrelationships, 7 have revised descriptions and 1 has a new CVE. Relationships across the cluster go from 1,310 to 1,725, all resolved against the currentmitre-atlas-attack-patternandmitre-attack-patternclusters.galaxies/agent-threat-rules.jsonand the cluster: version 3 -> 4.README.md: regenerated withtools/update_README_with_index.py; only the ATR total changes.Generator changes (
scripts/generate-atr-galaxy.py)model-securitycategory to the kill chain. A rule in that category (ATR-2026-02662) would otherwise fall back toskill-compromise.LLM01:2025). The generator maps them toID - nameusing the 2025 Top 10 names, so the field keeps its earlier format. This also corrects 135 existing values that carried names from the 2023 list or a mismatched ID and name, for exampleLLM02:2025 - Insecure Output HandlingorLLM08:2025 - Excessive Agency.categoryandsub_categoryfields that were added to the galaxy file by hand, so regeneration keeps them.Validation
./jq_all_the_things.shleaves only these four files changed.schema_clusters.jsonandschema_galaxies.json.Disclosure: I maintain Agent Threat Rules. This was done with Claude Code.