Secure by Design: A Guide for Manufacturers (CISA)

Principle 2: Embrace radical transparency and accountability – Secure by Design: A Guide for Manufacturers (CISA)

Secure by Design: A Guide for Manufacturers (CISA) P2-BP4: Publish results, including setbacks

Share internal successes, costly wins and unexpected setbacks from changing the SDLC so the wider industry can learn from what worked and what did not.

Maintained by Gerard BlokdykVerified against the published standard 31 May 2026Control text last updated 21 May 2026

Other controls in Principle 2: Embrace radical transparency and accountability – Secure by Design: A Guide for Manufacturers (CISA)

P2-BP1 Publicly name a secure by design executive sponsor
P2-BP2 Publish a secure by design roadmap
P2-BP3 Publish a memory safety roadmap
P2-PD1 Establish and publish internal security controls
P2-PD2 Publish high-level threat models
P2-PD3 Publish detailed secure SDLC self-attestations
P2-PD4 Embrace vulnerability transparency
P2-PD5 Publish software bills of materials

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpoint All Secure by Design: A Guide for Manufacturers (CISA) controls