International (CISA-led joint guidance; eighteen authoring organisations)

Secure by Design: A Guide for Manufacturers (CISA)

103 controls. 106 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.

103 controls 106 frameworks share controls with it International (CISA-led joint guidance; eighteen authoring organisations) 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.

Every control

CodeControlAlso in
CISABD-1Take Ownership of Customer Security Outcomes77
CISABD-2Embrace Radical Transparency and Accountability21
CISABD-3Build Organizational Structure and Leadership for Secure Outcomes32
SBD-10CVE Issuance with Complete Detail0
SBD-11Evidence of Intrusion in Logs0
SBD-12Secure Software Development Lifecycle0
SBD-13SBOM and Software Provenance0
SBD-14Open Source Software Stewardship0
SBD-15Customer Security Outcome Metrics0
SBD-16Eliminate Hardcoded Secrets0
SBD-17Authentication for Local and Network Interfaces0
SBD-18Loss-Free Recovery and Backups0
SBD-19Reduce Hardening Guide Length0
SBD-20Sign the Secure by Design Pledge0
SBD-5Mandate MFA, Especially for Privileged Users0
SBD-6Reduce Entire Classes of Vulnerabilities0
SBD-7Increase Use of Secure Defaults0
SBD-8Patch Adoption0
SBD-9Establish a Vulnerability Disclosure Policy0
SBD-DEV-01Memory-Safe Programming Languages0
SBD-DEV-02Parameterized Queries0
SBD-DEV-03Web Template Frameworks with Auto-Escaping0
SBD-DEV-04Phishing-Resistant Authentication57
SBD-DEV-05Secure Software Development Framework18
SBD-DEV-06Threat Modeling6
SBD-DEV-07Dependency Management and SBOM27
APRIL2023Changes between the April 2023 and October 2023 editions0
CR-1Hold suppliers accountable through purchasing criteria0
CR-2Fund core enterprise IT services as critical functions0
CR-3Build strategic relationships with key IT suppliers0
CR-4Coordinate with peers and understand cloud shared responsibility0
DEFINITIONSSecure by design and secure by default0
DF-1Eliminate default passwords0
DF-2Mandate MFA for privileged users0
DF-3Single sign-on0
DF-4Secure logging0
DF-5Software authorization profiles0
DF-6Forward-looking security over backwards compatibility0
DF-7Track and reduce hardening guide size0
DF-8Weigh the user experience cost of security settings0
DF-9Replace hardening guides with loosening guides0
DOCUMENTThe Secure by Design guidance, its editions and its status0
DT-1Memory safe programming languages (SSDF PW.6.1)0
DT-10CVE completeness0
DT-11Defense in depth0
DT-12Satisfy the Cybersecurity Performance Goals0
DT-2Secure hardware foundation0
DT-3Secure software components (SSDF PW.4.1)0
DT-4Web template frameworks (SSDF PW.5.1)0
DT-5Parameterized queries (SSDF PW.5.1)0
DT-6Static and dynamic application security testing (SSDF PW.7.2, PW.8.2)0
DT-7Code review (SSDF PW.7.1, PW.7.2)0
DT-8Software bill of materials (SSDF PS.3.2, PW.4.1)0
DT-9Vulnerability disclosure programmes (SSDF RV.1.3)0
P1Principle 1: Take ownership of customer security outcomes0
P1-BP1Provide security logging at no additional charge0
P1-BP2Eliminate hidden security taxes0
P1-BP3Embrace open standards0
P1-BP4Provide upgrade tooling0
P1-PD1Document conformance to a secure SDLC framework0
P1-PD2Document conformance to the CISA CPGs or an equivalent0
P1-PD3Run vulnerability management as a quality programme0
P1-PD4Use open source software responsibly0
P1-PD5Provide secure defaults for developers0
P1-PD6Foster a developer workforce that understands security0
P1-PD7Test SIEM and SOAR integration0
P1-PD8Align with zero trust architecture0
P1-SD1Eliminate default passwords0
P1-SD2Conduct security-focused field tests0
P1-SD3Reduce the size of hardening guides0
P1-SD4Actively discourage unsafe legacy features0
P1-SD5Implement attention-grabbing alerts0
P1-SD6Create secure configuration templates0
P2Principle 2: Embrace radical transparency and accountability0
P2-BP1Publicly name a secure by design executive sponsor0
P2-BP2Publish a secure by design roadmap0
P2-BP3Publish a memory safety roadmap0
P2-BP4Publish results, including setbacks0
P2-PD1Establish and publish internal security controls0
P2-PD2Publish high-level threat models0
P2-PD3Publish detailed secure SDLC self-attestations0
P2-PD4Embrace vulnerability transparency0
P2-PD5Publish software bills of materials0
P2-PD6Publish a vulnerability disclosure policy0
P2-SD1Publish aggregate security statistics and trends0
P2-SD2Publish patching statistics0
P2-SD3Publish data on unused privileges0
P3Principle 3: Lead from the top0
P3-1Report the secure by design programme in corporate financial reports0
P3-2Report product security regularly to the board0
P3-3Empower the secure by design executive0
P3-4Create meaningful internal incentives0
P3-5Create a secure by design council0
P3-6Create and evolve customer councils0
PLEDGESecure by Design Pledge (May 2024): seven goals0
PLEDGE-1Pledge goal 1: Multi-factor authentication0
PLEDGE-2Pledge goal 2: Default passwords0
PLEDGE-3Pledge goal 3: Reducing entire classes of vulnerability0
PLEDGE-4Pledge goal 4: Security patches0
PLEDGE-5Pledge goal 5: Vulnerability disclosure policy0
PLEDGE-6Pledge goal 6: CVEs0
PLEDGE-7Pledge goal 7: Evidence of intrusions0
RELATEDRelated CISA secure by design and secure by demand material held but not modelled0

Tell me when Secure by Design: A Guide for Manufacturers (CISA) 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.

  • Memory safe language adoption plan
  • SAST evidence
  • Threat model artifacts
  • Threat models / architecture-analysis records (STRIDE or equivalent)
  • Identified threats and mitigations
  • Threat model

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 Secure by Design: A Guide for Manufacturers (CISA), 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