[karauda]

What this PR changes

Adds Guardana to the tool list and to the LLM01 / ASI01 sections of the MITRE ATLAS mappings. I maintain Guardana; it's an Apache-2.0 CLI in beta.

The rule catalog documents its direct and indirect prompt-injection checks. The two entry JSON files and the webapp bundle were regenerated from the mappings.

Type of change

• New mapping file
• Update to existing mapping (content, controls, CVE refs)
• Bug fix (broken link, typo, incorrect cross-ref)
• New recipe (shared/RECIPES.md)
• New tool (shared/TOOLS.md)
• Infrastructure (scripts, CI, templates)
• Translation (i18n/)

Source / evidence

• Rule catalog at 1.0.0rc2: guardana.prompt.injection.ignore_previous, guardana.scenario.indirect_injection and guardana.agent.tool_result_injection, with LLM01:2026 / ASI01:2026 mappings.
• Detection limits.

Checklist

Content

• Existing file structure retained; tools, references and changelogs updated.
• Severity ratings and technique mappings unchanged.
• No new cross-references between framework files.
• Referenced vulnerability IDs are valid: LLM01 and ASI01.
• Existing CC BY-SA 4.0 headers retained.

Links & data

• Internal links pass validation.
• New external URLs return 200.
• Generated entries remain compatible with the data schema.

Project hygiene

• Changelog entry added to every edited Markdown file.
• No new mapping file; root CHANGELOG.md and README mapping counts need no change.
• Tool-category count updated in shared/TOOLS.md.
• Both edited mapping files pass node scripts/validate.js --file <path>.

For new mapping files only

Not applicable: this PR adds no mapping file, framework or control.

Notes for reviewers

npm run build passes. npm test passes all 137 tests, with none skipped. The validator reports 92 warnings; I ran it on the unchanged base as well and the warning list is identical. Both edited mappings validate with zero errors and zero warnings.

[emmanuelgjr]

Thanks, @karauda, and sorry for the wait. This is a clean, well-scoped contribution.

What checks out

• Guardana meets the inclusion bar in shared/TOOLS.md: Apache-2.0, actively maintained, and directly relevant to LLM01 and ASI01.
• The edits stay out of the ATLAS technique rows. Guardana goes only into the tools tables, references and changelogs, so this doesn't collide with the open ATLAS id work in MITRE ATLAS: 81 of 117 mapping rows pair an id with another technique's name; 6 ids do not exist (checked against ATLAS 2026.08) #93.
• The tool-category count is right: Adversarial Testing has 13 rows on this branch.
• The entry JSON and docs/data.js additions match the Markdown tables.
• The conflict of interest is disclosed in the PR body, and the beta status is stated in the description.

Before it can merge

1. Note the COI in the changelog rows. GOVERNANCE.md (Conflict of interest) asks for a disclosed COI to be recorded in the mapping file's changelog entry, not only in the PR. Something like Konrad Karauda (Guardana maintainer, COI disclosed) in the three changelog rows would cover it.
2. CI hasn't run yet. This is a fork PR, so a maintainer has to approve the workflow run. That's on our side.
3. The LLM01 / ASI01 tagging needs a maintainer sign-off. Per project rules, risk mappings are confirmed by a human SME rather than taken from the tool's own catalogue. That's routine, and not a request to change anything.

A small optional point: shared/TOOLS.md hasn't had a Changelog section before. It's reasonable to add one, but a maintainer may prefer the root CHANGELOG.md.

[karauda]

Thanks for the review, @emmanuelgjr. Commit ee4d50d records my disclosed conflict of interest in the three changelog rows, as GOVERNANCE.md asks: agentic-top10/Agentic_MITREATLAS.md, llm-top10/LLM_MITREATLAS.md and shared/TOOLS.md now name me as Konrad Karauda (Guardana maintainer, COI disclosed). The Changelog section in shared/TOOLS.md stays as it is; if the maintainers prefer the root CHANGELOG.md, I will move the entry there. Workflow approval and SME sign-off on the LLM01 / ASI01 tagging are on the maintainers' side, and I am not requesting any change to either.