CISA Secure by Design

CISA’s Secure by Design pledge progress report highlights vendor commitments to memory safety, vulnerability disclosure, and MFA defaults—signals customers can embed in procurement.

Kodi C.

Editor & Research Lead

Reviewed for accuracy by Kodi C.

Cybersecurity threat, control, and response briefings

At RSA Conference 2024, CISA published its first Secure by Design pledge progress report, summarizing how 68 vendors are implementing memory safety roadmaps, SBOM delivery, and secure default settings. Advised: organizations to align contract language and vendor scorecards with these published goals.

Market signals

Memory safety milestones. Vendors outlined timelines for migrating critical components to memory-safe languages; some committed to 50%+ coverage by 2025.
Default security. Multi-factor authentication and logging are being enabled by default across pledged products, reducing deployment friction.
Transparency. CISA will publish quarterly updates, naming vendors that miss milestones—raising accountability pressure.

Aligning your controls

NIST SP 800-218 SSDF PO.4. Incorporate secure-by-design criteria into supplier requirements and intake checklists.
FedRAMP / StateRAMP. Reference the pledge in authorization packages to demand evidence of memory safety and SBOM delivery.

What to watch for

Monitor vendor advisories for memory safety refactors that could affect performance or compatibility.
Ensure vulnerability disclosure timelines align with the 90-day reporting commitments outlined in the pledge.

Recommended actions

Update procurement scorecards to award points for vendors participating in the Secure by Design pledge.
Communicate the pledge milestones to executive teams so they understand how purchasing decisions influence software quality.

Key takeaways

CISA is tracking concrete milestones. The pledge obligates signatories to ship memory-safe rewrites, secure-by-default configurations, and vulnerability disclosure automation by December 2025, with quarterly reporting beginning July 2024.
Signatory list spans critical suppliers. Initial participants include AWS, Cloudflare, Google, Microsoft, Okta, and Rapid7, giving enterprises use to demand aligned roadmaps from their broader vendor portfolios.
Metrics will surface laggards. CISA’s roadmap calls for measuring default MFA coverage, incident response telemetry, and exploitability windows, so customers can codify those metrics into supplier contracts.

Maintaining vendor assessment templates that map Secure by Design commitments to measurable onboarding and renewal criteria.

Regulatory backdrop

This development represents a significant milestone in the broader regulatory environment affecting cybersecurity initiatives globally. Organizations must understand not only the immediate requirements but also the interconnected policy frameworks that influence implementation strategies and compliance obligations.

The regulatory environment continues to evolve as policymakers balance innovation enablement with risk mitigation and stakeholder protection. This particular development reflects ongoing efforts to establish clear governance frameworks that support responsible adoption while maintaining appropriate safeguards against potential misuse or unintended consequences.

Stakeholders across multiple sectors should consider how this development intersects with existing compliance obligations under frameworks such as GDPR, CCPA, SOC 2, ISO 27001, and industry-specific regulations. The interconnected nature of modern regulatory requirements means that addressing one area often has implications for related compliance domains.

What to consider

Organizations seeking to align with these requirements should begin with a thorough gap analysis comparing current capabilities against the specified standards. This assessment should encompass technical infrastructure, organizational processes, personnel competencies, and governance mechanisms.

A phased implementation approach typically proves most effective, beginning with foundational elements before progressing to more advanced capabilities. Priority should be given to areas presenting the greatest risk exposure or compliance urgency, while building sustainable practices that can adapt to evolving requirements.

Key implementation factors include resource allocation, timeline management, stakeholder coordination, and change management. Organizations should establish clear governance structures to oversee implementation progress and ensure accountability across relevant business units and functional areas.

Technical implementation should follow security-by-design principles, incorporating appropriate controls from the outset rather than attempting to retrofit security measures after deployment. This approach typically reduces overall implementation costs while improving security posture and compliance outcomes.

Managing risk

Effective risk management requires systematic identification, assessment, and treatment of risks associated with this development. Organizations should use established frameworks such as NIST RMF, ISO 31000, or COBIT to structure their risk management approach.

Risk identification should consider technical vulnerabilities, operational disruptions, regulatory penalties, reputational impacts, and strategic implications. Each identified risk should be assessed for likelihood and potential impact, with appropriate risk treatment strategies developed for high-priority items.

Continuous monitoring capabilities are essential for detecting emerging risks and evaluating the effectiveness of implemented controls. Organizations should establish key risk indicators and reporting mechanisms that provide timely visibility into risk exposure across relevant domains.

Risk tolerance thresholds should be established at the organizational level, with clear escalation procedures for risks that exceed acceptable levels. This governance framework ensures appropriate oversight while enabling agile responses to changing risk conditions.

Roadmap to compliance

Developing a structured compliance roadmap helps organizations systematically address requirements while managing resource constraints and competing priorities. The roadmap should establish clear milestones, responsible parties, and success criteria for each compliance objective.

Near-term priorities typically focus on addressing imminent compliance deadlines and high-risk gaps. Medium-term initiatives build sustainable compliance capabilities through process improvements, technology investments, and workforce development. Long-term strategic planning ensures continued alignment as requirements evolve.

Documentation requirements should be addressed throughout the compliance journey, establishing evidence trails that demonstrate due diligence and support audit activities. Organizations should implement document management practices that ensure accessibility, version control, and appropriate retention.

Regular compliance assessments help organizations verify progress against roadmap objectives and identify areas requiring additional attention. These assessments should incorporate both internal reviews and independent third-party evaluations where appropriate.

Who is affected

This development affects multiple stakeholder groups, each with distinct interests, concerns, and information needs. Effective stakeholder management requires understanding these perspectives and developing appropriate engagement strategies.

Internal stakeholders including executive leadership, board members, operational teams, and employee populations require tailored communications that address their specific concerns and responsibilities. Clear role definitions and accountability structures support effective internal coordination.

External stakeholders such as customers, partners, regulators, and industry peers also have legitimate interests in organizational responses to this development. Transparent communication and demonstrated commitment to compliance build trust and support collaborative relationships.

Investor and analyst communities focus on governance, risk management, and compliance capabilities as indicators of organizational resilience and long-term value creation. Organizations should consider how their response to this development affects external perceptions and stakeholder confidence.

Infrastructure needs

Technology plays a critical enabling role in addressing the requirements associated with this development. Organizations should evaluate current technology capabilities against anticipated needs and develop enhancement plans where gaps exist.

Core technology considerations typically include data management systems, security infrastructure, monitoring and analytics platforms, and integration capabilities. Organizations should assess whether existing technology investments can be used or whether new capabilities are required.

Automation opportunities should be identified and prioritized based on efficiency gains, error reduction, and scalability benefits. Robotic process automation, artificial intelligence, and machine learning technologies may offer valuable capabilities for specific use cases.

Technology vendor relationships should be evaluated to ensure appropriate support for compliance requirements. Contractual provisions, service level agreements, and vendor security practices all merit attention as part of technology governance.

Emerging trends

The regulatory and policy environment continues to evolve rapidly, with several emerging trends likely to influence future developments in this area. Organizations should maintain awareness of these trends and build adaptive capabilities that support ongoing compliance.

Regulatory convergence across jurisdictions creates both challenges and opportunities for multinational organizations. While harmonization efforts reduce compliance complexity in some areas, divergent national approaches require careful planning in others.

Technology evolution continues to create new capabilities and new risks requiring regulatory attention. Organizations should anticipate that current requirements will be supplemented or modified as policymakers respond to technological changes and emerging best practices.

Industry collaboration through standards bodies, professional associations, and informal networks provides valuable opportunities for sharing implementation experiences and influencing policy development. Active engagement in these forums supports more effective compliance outcomes.

Visit pillar hub

Latest guides

Network Security Fundamentals Explained Practically
A practitioner-focused guide to network security fundamentals covering firewalls, segmentation, IDS/IPS, DNS security, VPNs, wireless security, zero trust architecture, and traffic…
Complete Beginner Cybersecurity Guide for Home Users
A practical cybersecurity guide designed for non-technical home users. Covers threat awareness, home network security, password management, multi-factor authentication, device…
Cybersecurity Operations Playbook
Use our research to align NIST CSF 2.0, CISA KEV deadlines, and sector mandates across threat intelligence, exposure management, and incident response teams.

References

Industry Standards and Best Practices — International Organization for Standardization
CISA Cybersecurity Resources

Comments

Community

We publish only high-quality, respectful contributions. Every submission is reviewed for clarity, sourcing, and safety before it appears here.

First name

Last name (optional)

Comment

Submissions showing "Awaiting moderation" are in review. Spam, low-effort posts, or unverifiable claims will be rejected. We verify submissions with the email you provide, and we never publish or sell that address.

Verification

Complete the CAPTCHA to submit.