|
| 1 | +# CISA Secure by Design Cheat Sheet |
| 2 | + |
| 3 | +## Introduction |
| 4 | +CISA’s *Secure by Design* initiative defines seven principles that guide organizations toward building software with security as a core business requirement. |
| 5 | +This cheat sheet provides developers, architects, and security teams with practical, actionable steps to align with these principles. |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +## 1. Take Ownership of Customer Security Outcomes |
| 10 | +- Ship products with **secure defaults** (e.g., MFA, encryption at rest & in transit). |
| 11 | +- Provide clear documentation of security features and configurations. |
| 12 | +- Deliver timely patches and updates, not leaving customers to defend themselves. |
| 13 | + |
| 14 | +--- |
| 15 | + |
| 16 | +## 2. Embrace Radical Transparency and Accountability |
| 17 | +- Publish **vulnerability advisories** openly with remediation timelines. |
| 18 | +- Share **SBOMs (Software Bill of Materials)** with customers. |
| 19 | +- Document secure configuration baselines. |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +## 3. Lead with Security as a Business Priority |
| 24 | +- Make **security a core KPI**, not just a compliance checkbox. |
| 25 | +- Integrate **threat modeling and security reviews** early in the design process. |
| 26 | +- Ensure executive buy-in and accountability for security outcomes. |
| 27 | + |
| 28 | +--- |
| 29 | + |
| 30 | +## 4. Understand and Address Harm Across the Product Lifecycle |
| 31 | +- Identify and mitigate **misuse/abuse cases** during design. |
| 32 | +- Provide secure **end-of-life and deprecation policies**. |
| 33 | +- Consider the **human and societal impacts** of insecure defaults. |
| 34 | + |
| 35 | +--- |
| 36 | + |
| 37 | +## 5. Ensure Default Secure Configurations |
| 38 | +- Disable insecure or legacy options by default. |
| 39 | +- Enforce **least privilege** and **role-based access control**. |
| 40 | +- Ship products with **logging and monitoring enabled** out of the box. |
| 41 | + |
| 42 | +--- |
| 43 | + |
| 44 | +## 6. Implement Security Controls at Scale |
| 45 | +- Automate patching, vulnerability scanning, and CI/CD security checks. |
| 46 | +- Use vetted, secure coding frameworks and libraries. |
| 47 | +- Standardize secure configurations across environments. |
| 48 | + |
| 49 | +--- |
| 50 | + |
| 51 | +## 7. Prioritize Security Investments for Maximum Impact |
| 52 | +- Focus first on **exploitable, high-risk vulnerabilities**. |
| 53 | +- Invest in developer education and secure coding training. |
| 54 | +- Track and measure the ROI of security improvements. |
| 55 | + |
| 56 | +--- |
| 57 | + |
| 58 | +## References |
| 59 | +- [CISA Secure by Design Alert](https://www.cisa.gov/news-events/alerts/2023/04/13/shifting-balance-cybersecurity-risk-principles-secure-design) |
| 60 | +- [CISA Secure by Design PDF](https://www.cisa.gov/sites/default/files/2023-04/principles_secure_by_design_secure_by_default_508c.pdf) |
| 61 | +- [OWASP Secure Product Design Cheat Sheet](Secure_Product_Design_Cheat_Sheet.md) |
| 62 | + |
| 63 | +--- |
0 commit comments