Securely enabling AI, grounded in risk
Understand where AI risk is introduced and exposed — then put in place what reduces it.
Built on the CoSAI Risk Map that succeeded Google’s SAIF, with MITRE D3FEND and ATLAS capabilities and the products that deliver them.
- IntroducedWhere the risk enters the system
- ExposedWhere it becomes visible or does damage
- MitigatedWhere controls can stop it
From risk to enablement
- 1RisksStep through every risk and watch it light up where it is introduced, exposed and mitigated.36 risks
- 2CapabilitiesThe MITRE D3FEND and ATLAS countermeasures that reduce each risk, grouped under the CoSAI controls they deliver.76 capabilities
- 3ArchitecturesHow each class of AI application is built and how data moves through it, with every capability pinned where it goes.18 architectures
- 4EnableOn each architecture: the foundations, the surface baseline and the use case's own additions, then how far each product covers them.52 products
See it happen: 20 real 2025–26 incidents walked step by step across their architectures, every step sourced.
Reference
Where the data comes from
CoSAI Risk Map
Components, risks, controls and personas, vendored at a pinned commit. Google donated SAIF to CoSAI, which grew it from 15 risks to 36.
cosai-oasis/secure-ai-tooling ↗Google SAIF
The three-phase walkthrough and the component highlights for the 15 original risks come from the public SAIF Map.
saif.google ↗MITRE D3FEND and ATLAS
The 59 capability identifiers and definitions, checksum-pinned. Their CoSAI mappings, the 17 specialisations and every architecture are authored here.
d3fend.mitre.org ↗The taxonomy is CoSAI’s; the composition is SAIF’s. Where the two disagree, the choice is declared on the component it affects. Source and full audit on GitHub ↗