Secure by Design: A Guide for Manufacturers (CISA)
CISA's Secure by Design initiative establishes principles for technology manufacturers to build security into their products from the ground up, rather than relying on customers to implement security after deployment. The guidance calls on manufacturers to take ownership of customer security outcomes, embrace radical transparency, and build organizational structures that prioritize security. Developed jointly with international cybersecurity agencies.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (14)
Commitment
| Code | Title |
|---|---|
| SBD-20 | Sign the Secure by Design Pledge |
Measurement
| Code | Title |
|---|---|
| SBD-15 | Customer Security Outcome Metrics |
Principle 1
| Code | Title |
|---|---|
| SBD-1 | Take Ownership of Customer Security Outcomes |
Principle 1 - Take Ownership of Customer Security Outcomes
Manufacturers should take responsibility for the security outcomes of their customers
| Code | Title |
|---|---|
| SBD-1.1 | Secure by Default Configuration |
| SBD-1.2 | Eliminate Default Passwords |
| SBD-1.3 | Free Security Features for All Tiers |
| SBD-1.4 | Automatic Security Updates |
| SBD-1.5 | Guided Secure Configuration |
Principle 2
| Code | Title |
|---|---|
| SBD-2 | Embrace Radical Transparency |
Principle 2 - Embrace Radical Transparency
Manufacturers should be transparent about security vulnerabilities, practices, and product security posture
| Code | Title |
|---|---|
| SBD-2.1 | Vulnerability Disclosure Program |
| SBD-2.2 | CVE and CWE Issuance |
| SBD-2.3 | Software Bill of Materials (SBOM) |
| SBD-2.4 | Transparent Security Advisories |
| SBD-2.5 | Publish Security Roadmaps |
Principle 3
| Code | Title |
|---|---|
| SBD-3 | Lead from the Top |
Principle 3 - Build Organizational Structure and Leadership
Manufacturers should build organizational structures and leadership that prioritize security
| Code | Title |
|---|---|
| SBD-3.1 | Executive Accountability for Security |
| SBD-3.2 | Security Investment Prioritization |
| SBD-3.3 | Internal Security Culture |
| SBD-3.4 | Customer Security Feedback Integration |
Process
| Code | Title |
|---|---|
| SBD-12 | Secure Software Development Lifecycle |
Resilience
| Code | Title |
|---|---|
| SBD-18 | Loss-Free Recovery and Backups |
Secure Development Practices
Technical practices for building secure products throughout the development lifecycle
| Code | Title |
|---|---|
| SBD-DEV-01 | Memory-Safe Programming Languages |
| SBD-DEV-02 | Parameterized Queries |
| SBD-DEV-03 | Web Template Frameworks with Auto-Escaping |
| SBD-DEV-04 | Phishing-Resistant Authentication |
| SBD-DEV-05 | Secure Software Development Framework |
| SBD-DEV-06 | Threat Modeling |
| SBD-DEV-07 | Dependency Management and SBOM |
Supply Chain
| Code | Title |
|---|---|
| SBD-13 | SBOM and Software Provenance |
| SBD-14 | Open Source Software Stewardship |
Tactical
| Code | Title |
|---|---|
| SBD-10 | CVE Issuance with Complete Detail |
| SBD-11 | Evidence of Intrusion in Logs |
| SBD-16 | Eliminate Hardcoded Secrets |
| SBD-17 | Authentication for Local and Network Interfaces |
| SBD-4 | Eliminate Default Passwords |
| SBD-5 | Mandate MFA, Especially for Privileged Users |
| SBD-6 | Reduce Entire Classes of Vulnerabilities |
| SBD-7 | Increase Use of Secure Defaults |
| SBD-8 | Patch Adoption |
| SBD-9 | Establish a Vulnerability Disclosure Policy |
Usability
| Code | Title |
|---|---|
| SBD-19 | Reduce Hardening Guide Length |
Your Compliance Coverage
If you comply with Secure by Design: A Guide for Manufacturers (CISA), you already cover:
OWASP DevSecOps Maturity Model (DSOMM)
24%
10 controls mapped
Compare →CNCF Security Technical Advisory Group (TAG)
22%
9 controls mapped
Compare →FAA Cybersecurity Framework for Aviation
22%
9 controls mapped
Compare →+ 406 more: Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 (22%), O-RAN Alliance Security Specifications (O-RAN.WG11) (22%)
See all 409 mapped frameworks ↓Maps to 409 other frameworks
Frequently Asked Questions
What is Secure by Design: A Guide for Manufacturers (CISA)?
Secure by Design: A Guide for Manufacturers (CISA) is a compliance framework from United States (Federal) with 14 domains and 41 controls. CISA's Secure by Design initiative establishes principles for technology manufacturers to build security into their products from the ground up, rather than relying on customers to implement security after deployment. The guidance calls on manufacturers to take ownership of customer security outcomes, embrace radical transparency, and build organizational structures that prioritize security. Developed jointly with international cybersecurity agencies. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does Secure by Design: A Guide for Manufacturers (CISA) have?
Secure by Design: A Guide for Manufacturers (CISA) has 41 controls organised across 14 domains. The largest domains are Tactical (10 controls), Secure Development Practices (7 controls), Principle 1 - Take Ownership of Customer Security Outcomes (5 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does Secure by Design: A Guide for Manufacturers (CISA) map to?
Secure by Design: A Guide for Manufacturers (CISA) maps to 409 other compliance frameworks. The top mapping partners are OWASP DevSecOps Maturity Model (DSOMM) (24% coverage), CNCF Security Technical Advisory Group (TAG) (22% coverage), FAA Cybersecurity Framework for Aviation (22% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with Secure by Design: A Guide for Manufacturers (CISA) compliance?
Start your Secure by Design: A Guide for Manufacturers (CISA) compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about Secure by Design: A Guide for Manufacturers (CISA) requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 41 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 768 frameworks.
Get Started Free →Free forever — no credit card required