International

BSIMM

36 controls. 1 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

36 controls 1 frameworks share controls with it International verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you runShared controls
NIST SP 800-21836measure it →

Every control

CodeControlAlso in
AA1.1Perform security feature review1
AA1.4Use a risk-ranking methodology for applications1
AA2.1Perform architecture analysis using STRIDE or equivalent1
AM1.2Create a data classification scheme and inventory1
AM1.3Identify potential attackers1
AM1.5Gather and use attack intelligence1
CMVM1.1Create or use an incident response capability for software1
CMVM1.2Identify software defects found in operations and feed them back to development1
CMVM1.3Track software bugs found in operations through the fix process1
CMVM3.4Operate a bug bounty program1
CP1.1Unify regulatory pressures1
CP1.2Identify privacy (PII) obligations1
CP1.3Create software security policy1
CR1.2Perform opportunistic code review1
CR1.4Use automated code review tools (SAST)1
CR1.5Make code review mandatory for all projects1
PT1.1Use external penetration testers1
PT1.2Feed penetration test results to defect management1
PT1.3Use penetration testing tools internally1
SE1.2Ensure host and network security basics are in place1
SE1.3Implement cloud security controls1
SE3.6Enhance application inventory with an operations bill of materials1
SFD1.1Build and publish security features1
SFD1.2Engage architecture teams with security1
SM1.1Publish process and evolve as necessary1
SM1.3Educate executives on software security1
SM1.4Implement security checkpoints and associated governance gates1
SM2.2Enforce gates with measurements and track exceptions1
SR1.1Create security standards1
SR1.3Translate compliance constraints to requirements1
SR1.5Identify open source and manage its risk1
ST1.1Perform edge/boundary value condition testing1
ST1.3Drive tests with security requirements and features1
ST1.4Integrate opportunistic security testing into the pipeline1
T1.1Conduct software security awareness training1
T1.7Deliver on-demand individual training1

Tell me when BSIMM files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Role inventory + RACI
  • Metrics + management review
  • Annual cycle documentation
  • Supervisory dialogue records
  • Role inventory + RACI + DPO designation
  • Operational controls + tooling investment
  • Control testing plan
  • Test results
  • Effectiveness metrics
  • Remediation plan

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for BSIMM, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition