OWASP SAMM, or the Software Assurance Maturity Model, is a framework for improving software security in a structured way. It helps organisations assess current practices, define a roadmap, and measure progress across governance, design, implementation, verification, and operations. The model is used to make security improvements repeatable, measurable, and easier to manage.
What OWASP SAMM Covers
OWASP SAMM is not a single control or checklist, it is a maturity model for understanding how well a software security programme is operating. Its value is that it gives teams a structured way to assess current practices, compare them with a target state, and turn security into an improvable management discipline rather than an ad hoc activity.
The model is useful because software security usually fails through inconsistency: one team has strong design reviews while another depends on informal code review, or one release train measures security work while another cannot show progress at all. SAMM creates a common language for those differences so leaders can see where the programme is immature, where it is improving, and where it still depends on individual heroics.
For the official model and terminology, the best starting point is the OWASP SAMM project itself.
How SAMM Organises Software Security Work
SAMM is built around business functions and security practices, which makes it useful for mapping security activity to how software is actually designed, built, verified, and operated. That matters because mature programmes do not treat security as one isolated team function, they distribute responsibility across governance, engineering, and delivery workflows.
The practical benefit of that structure is traceability. A team can ask whether its governance is setting policy and ownership, whether design work includes threat-aware decisions, whether implementation has secure coding expectations, whether verification proves those expectations, and whether operations can detect and respond when software behaviour changes. In other words, SAMM helps organisations see security as a lifecycle system.
When teams need a broader programme view, NHIMG's Application Security Guide is a useful companion because it places SAMM alongside threat modelling, testing, secure development, and the wider AppSec operating model.
How SAMM Supports Assessment and Roadmapping
A maturity model is only useful if it can support honest assessment. SAMM helps organisations score where they are today, identify gaps by practice area, and define a realistic roadmap instead of trying to fix everything at once. That makes it especially valuable for programme planning, executive reporting, and sequencing improvements across multiple teams.
The model also helps avoid the common mistake of equating tool adoption with maturity. A scanner, policy, or training programme may be necessary, but SAMM asks whether the organisation has repeatable practices, clear ownership, and measurable improvement. That distinction is important because security programmes often look active without actually becoming more dependable.
For teams that need a clearer way to compare SAMM with other maturity approaches, NHIMG's AppSec Maturity Model guide helps place SAMM in the broader maturity-model landscape and is especially useful when selecting a baseline for assessment.
Why SAMM Matters for Repeatable Security Improvement
SAMM is most valuable when organisations want security improvements that survive staffing changes, product growth, and shifting priorities. By framing security as a managed capability, it supports repeatability, measurement, and continuous improvement instead of one-off projects that fade after launch.
That also makes SAMM a good bridge between engineering and governance. Security leaders can use it to show progress in a way that product and platform teams can understand, while engineering teams can use it to justify investment in design, verification, and operational controls. The result is a more durable software security programme, not just a more visible one.
When organisations are turning maturity goals into operating practice, NHIMG's DevSecOps Guide is a strong follow-on because it shows how maturity objectives translate into pipeline controls, checks, and metrics.
Risk and Threat Considerations
Security maturity gaps create real exposure because weaknesses in governance, design, implementation, verification, and operations tend to compound. If an organisation cannot assess its current state, it can easily overestimate its resilience, leave critical practices unowned, or miss repeated failure patterns that attackers later exploit.
Failure mechanism: Inconsistent or immature software security practices create uneven control coverage, allowing defects, insecure design decisions, and weak verification to persist from one release to the next. Over time, that makes compromise easier because the organisation cannot reliably prevent or detect the same classes of weakness.
Impact: The result is a higher likelihood of vulnerable releases, delayed remediation, and security debt that scales with the codebase. In mature programmes, the risk is not only exploitation, but also the inability to prove improvement, prioritise investment, or respond quickly when a control breaks down.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP ASVS, NIST SP 800-53 Rev 5, CIS Controls v8 and SLSA set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V15 — Secure Coding and Architecture | SAMM measures maturity in secure design and implementation practices that ASVS helps verify. |
| Recommendation — Use ASVS to define verifiable secure coding and architecture requirements for the practices SAMM highlights. | ||
| NIST SP 800-53 Rev 5 | SA-11 — Developer Testing and Evaluation | SAMM emphasizes repeatable verification and evaluation across the software lifecycle. |
| Recommendation — Apply SA-11 to require security testing evidence that demonstrates the maturity gaps SAMM identifies. | ||
| CIS Controls v8 | CIS-16 — Application Software Security | SAMM is directly about improving application security processes and outcomes across delivery. |
| Recommendation — Use CIS-16 to anchor application security practices that SAMM tracks across the programme lifecycle. | ||
| SLSA | Supply chain integrity | SAMM maturity often includes software build and release assurance, which overlaps with provenance and artifact integrity. |
| Recommendation — Adopt SLSA practices where SAMM roadmaps require stronger build provenance and release integrity. | ||
| ISO/IEC 27001:2022 | A.8.25 — Secure development life cycle | SAMM materially supports secure development lifecycle governance and measurable improvement. |
| Recommendation — Map SAMM improvement targets to A.8.25 to formalise secure development lifecycle expectations. | ||
Practitioner Guidance
Governance implication: Treat SAMM as a programme management model, not as a compliance label. It works best when leadership assigns ownership for each practice area, defines a target maturity, and reviews progress on a regular cadence rather than using the model only during a one-time assessment.
What to watch for: The strongest signal that SAMM is being used well is when teams can explain which practices are immature, why they matter, and what improvement will happen next. If the model cannot drive a roadmap, it is being treated as documentation rather than a management tool.
Related resources from NHI Mgmt Group
- Guide: OWASP SAMM Guide
- How do organisations decide whether to use OWASP Top 10 2025, SAMM, DSOMM, or ASVS in an application security program?
- How should security teams implement OWASP SAMM across the software development lifecycle?
- What is the difference between OWASP SAMM governance and verification?
- Should organisations use OWASP SAMM or framework checklists to manage SDL maturity?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org