Add OWASP AISVS 1.0 mapping across all three source lists (25 → 26 frameworks)

[emmanuelgjr]

Summary

This adds OWASP AISVS 1.0 as a mapped framework, taking the count from 25 to 26.

Registry	data/frameworks/owasp-aisvs.json: all 191 AISVS 1.0 requirements, one control each, inventory complete
Agentic Top 10	agentic-top10/Agentic_AISVS.md: 83 mappings, ASI01–ASI10
DSGAI 2026	dsgai-2026/DSGAI_AISVS.md: 141 mappings, DSGAI01–DSGAI21
LLM Top 10 2026	llm-top10/LLM_AISVS.md: 82 mappings, LLM01–LLM10. The source's 74 rows were re-keyed to 2026, and 8 rows were added; see below

That's 306 mappings over 41 entries.

The totals move from 3,497 to 3,803 mappings, 74 to 77 mapping files, 25 to 26 frameworks (both mapped and registered), 1,372 to 1,563 controls, and 2 to 3 "current" in the freshness count.

Compatibility findings

• LLM Top 10: re-keyed to 2026. LLM_AISVS.md was written against the 2025 list. It was moved to the 2026 list using the MIGRATION.md map in a single pass:

  • Sections were renumbered and renamed (LLM03 Excessive Agency, LLM04 Supply Chain, LLM08 Hidden Context Exposure, LLM10 Improper Output Handling, and so on).

  • Cross-references were renumbered.

  • Severities follow the 2026 re-baselining (LLM03 Critical, LLM06 and LLM07 High).

  • Otto's 74 rows are otherwise unchanged. The 2026 scope changes add 8 AISVS requirements, each marked (2026 scope) in its row:

    Entry	2026 scope change	Added
    LLM01	Cross-modal injection	2.2.3, 2.2.4
    LLM04	Artifact provenance / namespace reuse	3.1.3, 3.1.1
    LLM05	Fine-tuning subversion (adapters, fine-tunes)	6.1.2, 3.5.1
    LLM08	Hidden context incl. tool/function schemas	10.2.4
    LLM10	Insecure generated code	9.3.7. AISVS has no requirement that scans generated code itself, and the section says so

  @ottosulin, a review of the 8 added rows would be welcome.

• ASI and DSGAI: IDs and names match exactly (all 31 checked). Header block, H1, source-list links and footer now match the sibling files.

• LLM cross-references inside the ASI/DSGAI files were renumbered from 2025 to 2026 using the MIGRATION.md map (91 IDs). generate.js merges these into crossrefs.llm_top10, so leaving them as they were would have attached the wrong LLM IDs to ASI and DSGAI entries.

• The registry format has changed since the source was written. framework-schema.json now requires kind on every control and stats.js throws without it. kind: control was added to all 191 items, plus an inventory_completeness block. The file validates with ajv against the schema and with ingest-framework.mjs --validate.

• Checked against upstream: requirement IDs, text and levels match OWASP/AISVS 1.0/en on 2026-09-14 for all 191.

• markdownlint: prose is wrapped to 120 columns and blank lines were added before lists. The mapping rows themselves are unchanged. The generated AISVS rows match the monorepo output field for field (control_id, control_name, tier, scope, notes).

Registration (following 2338d1a)

• FRAMEWORK_FILES in generate.js
• framework-sources.json entry
• COMPLETE_BY_DEFINITION in inventory-completeness.js, so npm run inventory doesn't downgrade AISVS to unknown
• REPORT_FRAMEWORKS and FW_META in compliance-report.js
• README: coverage matrix (now ✅ for all three lists), file tables and repository tree
• Framework counts in docs/index.html, the agentic landing page, ai-standards-crosswalk (new table row, and its stale 23 / 3,211 figures corrected) and llms.txt
• package.json description, FRESHNESS_SLA, CHANGELOG

The i18n READMEs are older snapshots (they don't list CoSAI either), so I left them alone.

Verification

Re-run after merging main (#91, #92) and adding the LLM file: validate.js passes, stats:check is current, unit tests pass 50/50, a second generator run leaves no drift, and markdownlint is clean on the changed files.

• node scripts/generate.js: 10/10 and 21/21 entries extracted, 0 WARN. A second run leaves no diff in data/entries, docs/data.js or docs/incidents.js.
• npm run stats:check passes, and git diff --exit-code -- README.md data/stats.json is clean.
• node scripts/validate.js: 0 errors. The warning set is identical to main (84), with 312 → 320 checks passed.
• npm run test:scripts: 50/50, and the tree is clean afterwards. One earlier run hit a parallel-run race: exports.test read an entry file while generate.test was rewriting it. It passed on re-run and with --test-concurrency=1.
• markdownlint-cli2 0.13: 0 errors.
• inventory-completeness --check passes.
• Commit is signed.

Merge notes

• Fix: the last entry in a mapping file swallowed the file's closing tables (22 junk mappings, 22 junk registry controls) #90 and fix(atlas): correct eleven MITRE ATLAS technique citations #92 (the ATLAS fix) also touch data/entries/*, data/backlinks.json, docs/*.js and stats.json. Expect conflicts in generated files. Resolve them by re-running node scripts/generate.js && npm run stats on the merged tree, not by editing by hand.
• Pre-existing issue: the Generated: date in the docs bundles makes the generator CI job date-dependent (T-ENG03: make the webapp data bundles deterministic #37).

Ported from GenAI-Security-Project/GenAI-Data-Security-Initiative#64 by @ottosulin (that copy of crosswalk/ has since been removed)

🤖 Generated with Claude Code

https://claude.ai/code/session_01KJVKF6raJCNKBWjTkDSqR4