OWASP SAMM Assessment

We assess your secure software development practices and create an achievable roadmap to improve SSDLC maturity.

What OWASP SAMM measures

OWASP SAMM is an open framework for assessing secure software development across 15 security practices and planning measurable improvements.

Assessment process

OWASP SAMM gives teams a way to assess current software assurance practices, define a target state, and turn gaps into an implementation roadmap.

1. Initial consultation

Purpose

Agree on the scope, owners, and timeline before assessment interviews begin.

Activities

Define the scope
Choose the scope of the assessment: the whole enterprise, one application, one project, or one team.
Identify stakeholders
Identify the stakeholders who own the assessment goals and need to provide evidence.
Plan the assessment
Confirm stakeholder availability, then share the action plan and timeline.

2. SAMM assessment

Purpose

Measure the maturity of your chosen scope across the 15 SAMM software security practices.

Activities

Evaluate current practices
Interview the stakeholders who know how work happens today. Teams with enough internal context can assess themselves. SAMM offers lightweight and detailed assessments; choose the detailed, evidence-based version when you need high confidence in the scores.
Determine maturity level
Score each security practice with the SAMM maturity scoring system. Activity scores come from multiple-choice answers, roll up into each practice area, and combine into the overall score.

3. Maturity report

Purpose

After the evaluation, we prepare a report that shows your current software assurance posture, strengths, gaps, and improvement areas.

Activities

Document current practices
Record the practices, evidence, and context behind each score.
Prepare a shareable report
Prepare an executive summary and detailed report with graphics that explain the current situation.

4. Improvement roadmap

Purpose

Choose a target score and select the activities that fit your risk, resources, and goals.

Activities

Activity prioritization
Identify the improvement opportunities that will reduce the most risk or unlock the most progress.
Define the target
Set or update the target by choosing the activities your organization should implement next. Most roadmaps include more lower-level activities than higher-level activities, and the final selection should account for dependencies between them.

The OWASP SAMM model

Each security practice contains two activity streams, and each stream has three maturity levels with defined objectives, activities, and success metrics.

How SAMM supports other requirements

SAMM can help teams assess and improve secure development practices used by other frameworks and regulations. It does not replace a compliance or conformity assessment.

NIST Secure Software Development Framework

NIST SSDF defines high-level secure development practices, while SAMM adds a maturity model for assessing current practices and planning improvements.

EU Cyber Resilience Act

The CRA sets product cybersecurity and vulnerability handling requirements across the product lifecycle. SAMM can support development-process improvements, while CRA conformity still requires product-specific risk assessment, technical documentation, and evidence against the applicable requirements.

ISO/IEC 27001

SAMM adds software-development detail to an information security management system. Teams should relate assessment findings to the controls and scope used for their ISO/IEC 27001 implementation.

OpenCRE mappings

OpenCRE links related sections across security standards and guidelines. Teams can use those mappings to compare coverage; a mapping does not make the sources or their obligations equivalent.

Teams we've worked with

OWASP SAMM Assessment packages

Choose the assessment depth and follow-up that fit your scope.

Compact

€5700 +VAT

High-level assessment of one selected scope with a visual report.

  • Initial consultation
  • Assessment of 5 business functions
  • Current SSDLC posture and gap report
  • Roadmap suggestion based on assessment interviews
Request a quote

Complete

€6900 +VAT

Assessment, documentation, and roadmap planning with post-assessment review calls.

  • Everything in Compact, plus:
  • Tailored roadmap planning based on the client's security risk appetite
  • 3 post-assessment calls to validate improvements and discuss strategy
Request a quote

Customized

Let's talk

A custom engagement for evidence review, project management, SSDLC policy writing, or other needs specific to your organization.

Schedule a call

Next steps

Implement controls

We work with Codific to deliver and implement SAMMY, Codific’s platform for assessments, roadmap planning, and maturity program tracking.

Codific SAMMY assessment flow, horizontal

Tell us what you need to implement next.

Schedule a call

Details

FAQ

1. How do ISO and SAMM complement each other?
ISO/IEC 27001 defines requirements for an information security management system. OWASP SAMM gives software teams a maturity model for secure development practices. Organizations can use the two together to connect management-system risks and controls with the work of designing, building, verifying, and operating software.
2. How do we determine an assessment scope?
Start with the goal of the assessment and the decisions the results need to inform. For a first SAMM assessment, one team or one product often gives the clearest signal. Consider customer type, geography, regulatory obligations, development model, and management style. Document the context so the same scope can be reassessed later and compared honestly.
3. How does SAMM map to other standards?
OWASP SAMM guidance includes mappings to standards and other models, while OpenCRE links related sections across security standards and guidelines. These mappings help teams compare coverage and find related requirements. They do not make the sources interchangeable or turn a SAMM score into evidence of compliance.
4. How does SAMM relate to NIST SSDF?

OWASP SAMM provides a detailed mapping to NIST SSDF, so teams can see how SAMM streams relate to SSDF tasks.

SAMM turns SSDF into a maturity path. Teams assess current maturity, choose a target state, and prioritize the activities that move them toward it.

The mapping uses Informative References to connect SAMM activities with SSDF tasks and supporting materials.

5. What is the difference between SAMM and BSIMM?

BSIMM is descriptive. It observes and reports software security activities across organizations, which makes it suited to benchmarking and industry comparison.

SAMM is prescriptive. It gives organizations defined maturity levels for assessing, building, and measuring software security practices.

BSIMM gives teams a common vocabulary for comparison. SAMM gives teams a roadmap for improvement.

Request a quote

Tell us which products, teams, or business units you want to assess so we can prepare a quote for your purchasing team.

Prefer email? Write to us and we'll get back within one business day.

Email [email protected]