AIMA
Maturity modelOWASP AI Maturity Assessment (AIMA) · OWASP Foundation
OWASP AIMA grades an organization's AI-program maturity qualitatively across eight lifecycle domains, while AITBM operationalizes that maturity quantitatively - turning the maturity grade into Tiered Assessment Pathway eligibility and, through the ACI components (Pc/Ec/Tf), into the confidence and freshness of a per-system ERS.
| AIMA Domain | Primary AITBM Sub-Metrics | Evidence Use / Notes |
|---|---|---|
| Responsible AI | Fa-1Fa-2Fa-3Fa-4Tr-1 | Fairness/explainability artifacts; raises Ec |
| Governance | Tr-3Tr-4 | Pc and deployment-tier assignment |
| Data Management | Pr-1Pr-3Ro-4 | Data lineage is the canonical Pc source |
| Privacy | Pr-1Pr-2Pr-3Pr-4 | Privacy-by-design; Ec and tier assignment |
| Design | Cn-1Cn-2Ro-2 | Threat modeling sets containment boundaries |
| Implementation | Cn-3Cn-4Cn-5 | Secure build provenance; agentic identity binding |
| Verification | Ro-1Ro-3Cn-3Cn-5 | Red-team/eval reports; strongest Ec + Tf driver |
| Operations | Tr-3 | Monitoring keeps Tf fresh; incident-response improves Rf |
Key findings
- AIMA maturity provides organizational-process context. It does not assign an AITBM pathway or ACI range; only the system's applicable provenance, evaluation, monitoring, and freshness evidence determines those values.
- The two-organization example is a dated illustration. An AIMA level alone cannot justify its displayed ACI or ERS; a current assessment must score the underlying evidence independently.
- AIMA practices may produce evaluation, monitoring, and provenance artifacts relevant to ACI. Practice maturity is contextual and never substitutes for AITBM admissibility, coverage, or freshness checks.
- The frameworks operate at different levels: AIMA assesses organizational maturity and process, while AITBM assesses a deployed system. AIMA v1.0 and Toolkit 1.0.1 use eight lifecycle domains and do not define an ERS, IVP/ORP/ACI profile, or Cn-5 metric.