A Score You Can Track And Budget
SAMM turns application security from a list of findings into a maturity profile with a target, so leadership can fund improvement and see it move.
OWASP SAMM, the Software Assurance Maturity Model, is an open framework for assessing and improving how an organisation builds secure software. It defines five business functions — Governance, Design, Implementation, Verification and Operations — each with three security practices, giving fifteen practices in all. Every practice has two streams scored on three maturity levels, so the result is a measurable profile and a roadmap rather than a pass-or-fail audit.
Each business function holds three security practices, and each practice is scored on two streams across three maturity levels. Select a function to see its practices — and what XcellHost delivers for them.
How the organisation manages software security as a whole: Strategy & Metrics, Policy & Compliance, and Education & Guidance. This is where ownership, budgets, policies and developer training are decided and measured.
How security is built into what gets made before code exists: Threat Assessment, Security Requirements and Secure Architecture. Covers threat modelling, requirement setting for teams and suppliers, and reusable secure patterns.
How software is built, deployed and fixed: Secure Build, Secure Deployment and Defect Management. Spans dependency control, pipeline integrity, secrets handling and the process for tracking and closing security defects.
How the organisation checks its work: Architecture Assessment, Requirements-driven Testing and Security Testing. Includes design reviews, test cases derived from requirements, and automated plus manual security testing.
How software is run securely after release: Incident Management, Environment Management and Operational Management. Covers detection and response, hardening and patching of environments, and data and legacy system handling.
SAMM turns application security from a list of findings into a maturity profile with a target, so leadership can fund improvement and see it move.
RBI expects a security-embedded application life cycle for digital payment systems; a SAMM profile shows how that life cycle actually works.
Global customers ask Indian software exporters how security is built in; a scored SAMM assessment answers the question better than a questionnaire.
SAMM is technology and process-agnostic, so it works equally for agile product teams, outsourced development and regulated waterfall projects without rework.
No Indian regulator mandates SAMM, and CERT-In's audit guidelines reference the OWASP DevSecOps Maturity Model for pipeline assessments rather than SAMM. SAMM still earns its place: it is the broadest way to show that the secure development practices Indian regulators expect exist and are maturing.
| Aspect | OWASP SAMM | BSIMM |
|---|---|---|
| Approach | Prescriptive: what you should do at each level | Descriptive: what other firms actually do |
| Ownership | Open, free, community-maintained by OWASP | Vendor-run study with a commercial assessment |
| Structure | 5 functions, 15 practices, 3 levels | 4 domains, 12 practices, observed activities |
| Best for | Building a roadmap from any starting point | Benchmarking against industry peers |
One team for assessment, remediation, 24×7 operations and audit evidence — run from Mumbai by a company certified to ISO/IEC 27001 and ISO/IEC 20000-1.
Talk to our security team →Interview teams, gather evidence and score all fifteen practices to produce the current profile.
Weeks 1–4Agree target maturity per practice and a phased roadmap with owners and budget.
Weeks 4–6Deliver the first phase: pipeline controls, threat modelling, testing and training.
Months 2–8Re-score annually, report progress and reset targets as products and regulations change.
OngoingXcellHost is certified to ISO/IEC 27001 and ISO/IEC 20000-1 and has protected Indian businesses since 1999 — so your OWASP SAMM work is run by a team that lives these controls every day.
Benchmark your software security initiative against peers
Application SecuritySecure software development practices for any SDLC
Application SecurityVerifiable security requirements for web apps and APIs
Application SecurityIndustry-proven secure development practices
Application SecurityThe ten most critical web application risks
Application SecuritySearch the complete master list across 12 domains.
Framework explorer