CISABD-1 | Take Ownership of Customer Security Outcomes | 77 |
CISABD-2 | Embrace Radical Transparency and Accountability | 21 |
CISABD-3 | Build Organizational Structure and Leadership for Secure Outcomes | 32 |
SBD-10 | CVE Issuance with Complete Detail | 0 |
SBD-11 | Evidence of Intrusion in Logs | 0 |
SBD-12 | Secure Software Development Lifecycle | 0 |
SBD-13 | SBOM and Software Provenance | 0 |
SBD-14 | Open Source Software Stewardship | 0 |
SBD-15 | Customer Security Outcome Metrics | 0 |
SBD-16 | Eliminate Hardcoded Secrets | 0 |
SBD-17 | Authentication for Local and Network Interfaces | 0 |
SBD-18 | Loss-Free Recovery and Backups | 0 |
SBD-19 | Reduce Hardening Guide Length | 0 |
SBD-20 | Sign the Secure by Design Pledge | 0 |
SBD-5 | Mandate MFA, Especially for Privileged Users | 0 |
SBD-6 | Reduce Entire Classes of Vulnerabilities | 0 |
SBD-7 | Increase Use of Secure Defaults | 0 |
SBD-8 | Patch Adoption | 0 |
SBD-9 | Establish a Vulnerability Disclosure Policy | 0 |
SBD-DEV-01 | Memory-Safe Programming Languages | 0 |
SBD-DEV-02 | Parameterized Queries | 0 |
SBD-DEV-03 | Web Template Frameworks with Auto-Escaping | 0 |
SBD-DEV-04 | Phishing-Resistant Authentication | 57 |
SBD-DEV-05 | Secure Software Development Framework | 18 |
SBD-DEV-06 | Threat Modeling | 6 |
SBD-DEV-07 | Dependency Management and SBOM | 27 |
APRIL2023 | Changes between the April 2023 and October 2023 editions | 0 |
CR-1 | Hold suppliers accountable through purchasing criteria | 0 |
CR-2 | Fund core enterprise IT services as critical functions | 0 |
CR-3 | Build strategic relationships with key IT suppliers | 0 |
CR-4 | Coordinate with peers and understand cloud shared responsibility | 0 |
DEFINITIONS | Secure by design and secure by default | 0 |
DF-1 | Eliminate default passwords | 0 |
DF-2 | Mandate MFA for privileged users | 0 |
DF-3 | Single sign-on | 0 |
DF-4 | Secure logging | 0 |
DF-5 | Software authorization profiles | 0 |
DF-6 | Forward-looking security over backwards compatibility | 0 |
DF-7 | Track and reduce hardening guide size | 0 |
DF-8 | Weigh the user experience cost of security settings | 0 |
DF-9 | Replace hardening guides with loosening guides | 0 |
DOCUMENT | The Secure by Design guidance, its editions and its status | 0 |
DT-1 | Memory safe programming languages (SSDF PW.6.1) | 0 |
DT-10 | CVE completeness | 0 |
DT-11 | Defense in depth | 0 |
DT-12 | Satisfy the Cybersecurity Performance Goals | 0 |
DT-2 | Secure hardware foundation | 0 |
DT-3 | Secure software components (SSDF PW.4.1) | 0 |
DT-4 | Web template frameworks (SSDF PW.5.1) | 0 |
DT-5 | Parameterized queries (SSDF PW.5.1) | 0 |
DT-6 | Static and dynamic application security testing (SSDF PW.7.2, PW.8.2) | 0 |
DT-7 | Code review (SSDF PW.7.1, PW.7.2) | 0 |
DT-8 | Software bill of materials (SSDF PS.3.2, PW.4.1) | 0 |
DT-9 | Vulnerability disclosure programmes (SSDF RV.1.3) | 0 |
P1 | Principle 1: Take ownership of customer security outcomes | 0 |
P1-BP1 | Provide security logging at no additional charge | 0 |
P1-BP2 | Eliminate hidden security taxes | 0 |
P1-BP3 | Embrace open standards | 0 |
P1-BP4 | Provide upgrade tooling | 0 |
P1-PD1 | Document conformance to a secure SDLC framework | 0 |
P1-PD2 | Document conformance to the CISA CPGs or an equivalent | 0 |
P1-PD3 | Run vulnerability management as a quality programme | 0 |
P1-PD4 | Use open source software responsibly | 0 |
P1-PD5 | Provide secure defaults for developers | 0 |
P1-PD6 | Foster a developer workforce that understands security | 0 |
P1-PD7 | Test SIEM and SOAR integration | 0 |
P1-PD8 | Align with zero trust architecture | 0 |
P1-SD1 | Eliminate default passwords | 0 |
P1-SD2 | Conduct security-focused field tests | 0 |
P1-SD3 | Reduce the size of hardening guides | 0 |
P1-SD4 | Actively discourage unsafe legacy features | 0 |
P1-SD5 | Implement attention-grabbing alerts | 0 |
P1-SD6 | Create secure configuration templates | 0 |
P2 | Principle 2: Embrace radical transparency and accountability | 0 |
P2-BP1 | Publicly name a secure by design executive sponsor | 0 |
P2-BP2 | Publish a secure by design roadmap | 0 |
P2-BP3 | Publish a memory safety roadmap | 0 |
P2-BP4 | Publish results, including setbacks | 0 |
P2-PD1 | Establish and publish internal security controls | 0 |
P2-PD2 | Publish high-level threat models | 0 |
P2-PD3 | Publish detailed secure SDLC self-attestations | 0 |
P2-PD4 | Embrace vulnerability transparency | 0 |
P2-PD5 | Publish software bills of materials | 0 |
P2-PD6 | Publish a vulnerability disclosure policy | 0 |
P2-SD1 | Publish aggregate security statistics and trends | 0 |
P2-SD2 | Publish patching statistics | 0 |
P2-SD3 | Publish data on unused privileges | 0 |
P3 | Principle 3: Lead from the top | 0 |
P3-1 | Report the secure by design programme in corporate financial reports | 0 |
P3-2 | Report product security regularly to the board | 0 |
P3-3 | Empower the secure by design executive | 0 |
P3-4 | Create meaningful internal incentives | 0 |
P3-5 | Create a secure by design council | 0 |
P3-6 | Create and evolve customer councils | 0 |
PLEDGE | Secure by Design Pledge (May 2024): seven goals | 0 |
PLEDGE-1 | Pledge goal 1: Multi-factor authentication | 0 |
PLEDGE-2 | Pledge goal 2: Default passwords | 0 |
PLEDGE-3 | Pledge goal 3: Reducing entire classes of vulnerability | 0 |
PLEDGE-4 | Pledge goal 4: Security patches | 0 |
PLEDGE-5 | Pledge goal 5: Vulnerability disclosure policy | 0 |
PLEDGE-6 | Pledge goal 6: CVEs | 0 |
PLEDGE-7 | Pledge goal 7: Evidence of intrusions | 0 |
RELATED | Related CISA secure by design and secure by demand material held but not modelled | 0 |