Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is OWASP SAMM?

OWASP SAMM is an open maturity model for software assurance, measuring 15 security practices across five business functions on a three-level scale to build an improvement roadmap.

Illustration for the cybersecurity term OWASP SAMM
Home / Blog / Cybersecurity Terms / What Is OWASP SAMM?
17 November 2026

What Is OWASP SAMM?

What Is OWASP SAMM?

OWASP SAMM, the Software Assurance Maturity Model, is an open framework for measuring and improving how securely an organisation builds software. Version 2, released in January 2020, structures the whole of secure development into five business functions, 15 security practices, and 30 activity streams, each scored on a three-level maturity scale.

Its appeal is that it is prescriptive without being a checklist. SAMM does not ask whether you own a particular scanner; it asks whether defect findings reach developers in a form they act on, and whether that happens by habit or by accident.

The Five Business Functions

SAMM groups practices by the part of the software lifecycle they serve:

Each of those 15 practices splits into two streams. Threat Assessment, for example, separates application risk profiling from threat modelling, so an organisation that classifies its applications but never models attacks against them cannot hide that gap behind a single score.

How Maturity Levels Work

Every stream has three levels, described as outcomes rather than tools:

LevelCharacterExample in Security Testing
1Ad hoc, driven by individualsAutomated scanning runs against high-risk applications before release
2Defined and repeatable across teamsScanning is embedded in the pipeline, with manual testing for sensitive features
3Measured and continuously improvedTesting depth is tuned by risk, false positives are managed, and coverage is reported

Assessment uses a published questionnaire: each activity gets a yes, partial, or no answer, which produces a fractional score per stream. The official SAMM toolbox spreadsheet totals these into a radar chart per business function, giving you a picture of where development assurance is strong and where it is theoretical.

Running an Assessment

A first assessment is usually a half-day workshop per product team with the engineering lead, a developer, and whoever owns release management. Two habits make it useful:

  1. Score what happens, not what is written down. A policy requiring code review does not earn a level if reviewers approve without reading.
  2. Assess per stream of work, not per company. A payments team and an internal tooling team rarely deserve the same score, and averaging them hides the risk.

The output is a baseline, a target profile for the next 12 months, and a roadmap of specific activities. SAMM deliberately does not expect level 3 everywhere; a sensible target for a mid-sized organisation might be level 2 in Defect Management and Secure Build, level 1 in Architecture Assessment, with the DevSecOps pipeline work sequenced accordingly.

SAMM, BSIMM and the Alternatives

The usual comparison is with BSIMM. BSIMM is descriptive: it reports what a set of observed firms actually do, so it answers “how do I compare with my peers”. SAMM is prescriptive and free: it states what good looks like, so it answers “what should I do next”. BSIMM participation requires a commercial assessment; SAMM can be run internally in a day with the published spreadsheet.

SAMM also pairs cleanly with other references. Its Security Testing stream is where the OWASP Top 10 and OWASP ASVS do their work, and its Policy and Compliance practice is where ISO 27001 Annex A controls on secure development land. The model, assessment toolbox, and guidance are published free by OWASP.

Why Programmes Stall

Two failure modes recur. The first is assessing once, producing a satisfying radar chart, and never reassessing, which turns a maturity model into a slide. The second is pursuing uniform level 3, which consumes budget on low-risk applications while a customer-facing service still has no threat model. Reassess every six to twelve months, keep the target profile risk-driven, and tie each roadmap item to a named owner inside engineering rather than inside security.

If you want the verification side of SAMM evidenced independently, our web application security services provide the testing results that feed the Verification function.

FAQ – Frequently Asked Questions

How Long Does a SAMM Assessment Take?

A first assessment for one development team typically takes half a day of workshop time plus a day of preparation and write-up. Larger organisations run several team-level assessments and roll the results up. Reassessments are much faster, usually two to three hours, because the evidence is already understood and only changes since the last round need discussion.

What Is the Difference Between OWASP SAMM and BSIMM?

SAMM is prescriptive and open: it describes target activities at three maturity levels and is free to use. BSIMM is descriptive and commercial: it records what participating firms actually do and lets you benchmark against that population. SAMM is better for planning improvement; BSIMM is better for answering how you compare with peers in your industry.

Do We Need to Reach Level 3 in Every Practice?

No, and trying to is a common waste of budget. SAMM expects you to set a target profile driven by risk, so a payments platform might aim for level 3 in Threat Assessment and Security Testing while internal tooling stays at level 1. Reaching uniform level 3 is rarely justified outside heavily regulated or safety-critical software.

Does SAMM Help With ISO 27001 or PCI DSS?

Indirectly, yes. SAMM activities produce much of the evidence those standards ask for on secure development: documented requirements, code review records, testing results, and defect tracking. ISO 27001 Annex A includes controls on secure development lifecycle and secure coding, and PCI DSS Requirement 6 covers much the same ground, so a SAMM roadmap usually closes audit gaps as a side effect.

Related Terms

You May Be Interested In These

What Skills Does an OT Security Engineer Need?

Cybersecurity Terms

17 November 2026

What Skills Does an OT Security Engineer Need?

Read More
What Are State-Sponsored Attackers?

Cybersecurity Terms

17 November 2026

What Are State-Sponsored Attackers?

Read More
What Is Aircrack-ng?

Cybersecurity Terms

17 November 2026

What Is Aircrack-ng?

Read More