NIST SSDF, Microsoft SDL, and BSIMM are often compared as if they were rivals, but they do different jobs. The NIST Secure Software Development Framework (SSDF) defines the outcomes that secure development should achieve. The Microsoft Security Development Lifecycle (SDL) prescribes a set of practices to follow. The Building Security In Maturity Model (BSIMM) measures what real software security programs do, so you can see where yours stands.

In short, SSDF tells you what good looks like, SDL tells you how one large vendor does it, and BSIMM tells you where you are. Many organizations end up using one of the first two to build their program and BSIMM to assess it.

SSDF vs SDL vs BSIMM at a glance

NIST SSDF, Microsoft SDL and BSIMM compared
NIST SSDFMicrosoft SDLBSIMM
Published byNIST, as Special Publication 800-218MicrosoftThe BSIMM project, now run by Black Duck
TypeOutcome-based frameworkPrescriptive set of practicesDescriptive maturity model
StructureFour practice groups: Prepare the Organization, Protect the Software, Produce Well-Secured Software, Respond to VulnerabilitiesA defined set of security practices applied across the development life cycleFour domains (Governance, Intelligence, SSDL Touchpoints, Deployment) containing 12 practices
Tells youWhat secure development should achieveHow to do it, based on Microsoft’s experienceWhat other organizations actually do, and how you compare
Vendor neutralityNeutral by design, and maps to other standardsUsable anywhere, but grew out of one company’s engineering cultureNeutral, because it is based on observed data
Best forBuilding or formalizing a program, and meeting U.S. federal supplier expectationsTeams that want concrete practices they can adoptAssessing an existing program and setting priorities for improvement

NIST SSDF: outcomes, not instructions

SSDF (NIST SP 800-218) is a set of high-level secure development practices organized into four groups:

  • Prepare the Organization (PO): define requirements, roles, training, and toolchains before code is written.
  • Protect the Software (PS): protect code, releases, and repositories from tampering and unauthorized access.
  • Produce Well-Secured Software (PW): design, threat model, code, review, and test so that fewer vulnerabilities ship.
  • Respond to Vulnerabilities (RV): identify vulnerabilities, remediate them, and address their root causes.

SSDF deliberately says what should happen and leaves the how to you. NIST designed it to fit into any software development life cycle, and it maps each practice to established sources, BSIMM and Microsoft SDL among them. That makes it easy to adopt in a mixed environment and useful as a common language between teams, suppliers, and auditors. It also carries regulatory weight, because U.S. federal guidance following Executive Order 14028 asks software suppliers to attest to secure development practices that are drawn from SSDF.

Microsoft SDL: a worked-out way of doing it

Microsoft introduced the SDL in the early 2000s and has published it for others to use. It is prescriptive: a concrete set of practices covering training, security requirements, threat modeling, secure design, cryptography standards, supply chain and third-party component risk, static and dynamic analysis, penetration testing, and incident response.

Its strength is that it is specific. A team that wants to be told what to do will get more from SDL than from SSDF. The cost is fit. SDL reflects a mature engineering organization, and a small team building process from scratch has to decide which practices to take on first.

BSIMM: a measuring stick

BSIMM is different in kind. It is a descriptive model, built by observing the software security initiatives of real organizations and recording which activities they perform. It does not say what you should do. It says what is being done, and how common each activity is.

It is organized into four domains (Governance, Intelligence, SSDL Touchpoints, and Deployment) and 12 practices: Strategy and Metrics, Compliance and Policy, Training, Attack Models, Security Features and Design, Standards and Requirements, Architecture Analysis, Code Review, Security Testing, Penetration Testing, Software Environment, and Configuration Management and Vulnerability Management. You use it to assess your current state and compare it with your peers, which makes it a way to set priorities.

How to choose

  1. If you are building a secure development program from nothing, start with SSDF. It gives a new team structure without tying it to a platform, and its four groups map naturally onto roles.
  2. If you sell software to U.S. federal agencies, you need SSDF whatever else you use, because supplier attestation is based on it.
  3. If your team wants concrete practices more than outcomes, use Microsoft SDL as the implementation guide underneath SSDF. The two are compatible, and SSDF itself references SDL.
  4. If you already have a program and want to know how mature it is, use BSIMM to assess it and find the weakest practices.
  5. Whichever you pick, settle the question of fit first. Team size, maturity, and the technology you run matter more than which framework is “best”.

Two worked examples

I have applied two of these to course case studies. For a fast-growing online retailer setting up its first three-developer team, I compared SSDF and Microsoft SDL and chose SSDF. SDL was not rejected as weak. It was simply a heavier framework to introduce to a team starting from scratch, and the retailer’s environment spanned AWS, WordPress, on-premise servers, and custom tools.

For a fictional university that had recently had an application security incident, the question was the other kind: where do we stand? I used BSIMM to map current practices across all four domains. The assessment found early-stage maturity, with review and testing processes that existed but did not look at security.

Frequently asked questions

What is the difference between NIST SSDF and BSIMM?
NIST SSDF is an outcome-based framework that describes what secure software development should achieve. BSIMM is a descriptive maturity model that records what organizations actually do, so you can measure your own program against it. SSDF is used to build a program, and BSIMM is used to assess one.
Is NIST SSDF mandatory?
Not in general. It is voluntary guidance. However, U.S. federal guidance issued after Executive Order 14028 requires software suppliers to federal agencies to attest that they follow secure development practices drawn from SSDF.
Can you use Microsoft SDL and NIST SSDF together?
Yes. SSDF defines outcomes and maps its practices to other sources, including Microsoft SDL. A common approach is to use SSDF as the framework and SDL as detailed guidance for how to implement specific practices.
Which framework is best for a small development team?
NIST SSDF is usually the easiest starting point for a small or new team, because it is vendor-neutral, works with any development life cycle, and translates cleanly into roles and checkpoints.

Sources