Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5be0feb425
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| name: Agent Configuration Tampering | ||
| tactic: Persistence | ||
| atlas: AML.T0010.002 | ||
| atlas: AML.T0081 |
There was a problem hiding this comment.
Keep ATLAS mapping table in sync with threat ID
Changing T-PERSIST-003 to AML.T0081 here leaves atlas_technique_mapping inconsistent, because the same threat is still listed under AML.T0010.002 (see threats.yaml lines 850-852). This creates conflicting ATLAS classifications for one threat, so consumers that render/group from the mapping block will keep showing the old technique and not reflect the new one.
Useful? React with 👍 / 👎.
I've just stumbled across this threat and noticed that it references the wrong ATLAS ID.
previously: "AI Supply Chain Compromise: Data" (AML.T0010.002)
now: "Modify AI Agent Configuration" (AML.T0081)