Commitment to Excellence: How Phoenix Security Embodies the CISA Secure by Design Pledge

CISA PLEDGE WIDE SQ

The effort that CISA has recently made to change the way software security companies do security and responsibly is admirable. That’s why Phoenix Security’s commitment to the Cybersecurity and Infrastructure Security Agency’s (CISA) Secure by Design Pledge is a significant stride towards a more secure future. This article delves into how Phoenix Security is not just committing and adhering to but also helping clients accelerate the achievement of the principle in the CISA Pledge, particularly focusing on the comprehensive controls currently in place.

cisa, cisa pledge. phoenix security, cisa kev, kev, secure by design

Understanding the CISA Secure by Design Pledge

The CISA Secure by Design Pledge is a voluntary initiative that encourages software manufacturers to implement proactive security measures in their development processes. By signing this pledge, companies commit to a series of goals aimed at enhancing the security and integrity of their software products and services. These goals include increasing the use of Multi-Factor Authentication (MFA), eliminating default passwords, and accelerating the deployment of security patches. More about the pledge can be found on the CISA Pledge Page.

cisa, cisa pledge. phoenix security, cisa kev, kev, secure by design

Phoenix Security’s Role in Advancing Cybersecurity

Phoenix Security has stepped up as a frontrunner in embracing and implementing the principles of the CISA Pledge. Here’s a closer look at the controls and strategies Phoenix has in place:

1. Proactive Vulnerability and Breach Disclosure

  • Vulnerability Disclosure: Phoenix Security promotes a transparent approach by allowing controlled exposure of vulnerabilities. This not only aligns with CISA’s expectations for vulnerability disclosure but also enhances them by incorporating comprehensive risk assessment workflows.
  • Breach Disclosure: Compliance with breach notification standards is not just about adhering to legal requirements; it’s about trust and transparency. Phoenix’s breach disclosure practices ensure all stakeholders are informed promptly, maintaining a clear and trustworthy communication channel.

2. Eliminating Default Passwords

  • In a bold move to secure identity management, Phoenix has eradicated the use of default passwords. By generating custom and random credentials via their robust identity platform, Phoenix ensures each software instance begins with a secure foundation, significantly reducing the risk of unauthorized access.

3. Mandatory Multi-Factor Authentication

  • Phoenix doesn’t just support MFA; it mandates its use across all critical systems. This policy extends to recommending and enforcing MFA for all Phoenix clients, thereby fortifying the security posture against potential breaches significantly.

4. Enhanced Patch Management

  • Phoenix Security identifies and prioritizes patches through an analysis that considers exploitability and alignment with the CISA Known Exploited Vulnerabilities (KEV) list. By accelerating the patching process, Phoenix ensures vulnerabilities are addressed swiftly, reducing the attack surface effectively. For further insight, read Phoenix’s analysis on the CISA KEV.

5. Comprehensive Reporting and Rapid Remediation

  • Committing to rapid CVE reporting, Phoenix enriches vulnerability records with CWE and CPE details, providing clarity and actionable information that aids in swift remediation efforts.

Conclusion

attack graph phoenix security
ASPM

Phoenix Security’s commitment to the CISA Secure by Design Pledge is more than just a compliance checklist; it’s a cornerstone of their security strategy. By aligning with CISA’s guidelines and going beyond them, Phoenix not only protects its products and services but also contributes to the broader goal of helping its customers enhance accelerate and demonstrate adherence to the principle. Phoenix Security remains committed to protecting the companies in the United States, United Kingdom and across the world by producing secure software and reacting quickly to vulnerabilities.

Get in control of your Application Security posture and Vulnerability management

Francesco is an internationally renowned public speaker, with multiple interviews in high-profile publications (eg. Forbes), and an author of numerous books and articles, who utilises his platform to evangelize the importance of Cloud security and cutting-edge technologies on a global scale.

Discuss this blog with our community on Slack

Join our AppSec Phoenix community on Slack to discuss this blog and other news with our professional security team

From our Blog

Most enterprises drown in vulnerability data yet starve for attribution. By mapping ownership, location, exposure, and business impact, Phoenix Security’s ASPM turns that swamp into a laser‑focused task list. Only then do three autonomous agents—Researcher, Analyzer, and Remediator—kick in, collaborating to recommend fixes and workflow automation that 10× security‑engineering output. Skip the context and you’ll waste money, requests, tokens, carbon, and human patience on hallucinated advice. For startups, the focus is clear—establish visibility and ensure core security practices are in place. Application Security Posture Management (ASPM) tools provide a straightforward, automated approach to detecting vulnerabilities and enforcing policies. These solutions help reduce risk quickly without overburdening small security teams. Mature organizations, on the other hand, are tackling a different set of problems. With the sheer number of vulnerabilities and an increasingly complicated threat landscape, enterprises need to fine-tune their approach. The goal shifts toward intelligent remediation, leveraging real-time threat intelligence and advanced risk prioritization. ASPM tools at this stage do more than just detect vulnerabilities—they provide context, enable proactive decision-making, and streamline the entire remediation process. The emergence of AI-assisted code generation has further complicated security in both environments. These tools, while speeding up development, are often responsible for introducing new vulnerabilities into applications at a faster pace than traditional methods. The challenge is clear: AI-generated code can hide flaws that are difficult to catch in the rush of innovation. Both startups and enterprises need to adjust their security posture to account for these new risks. ASPM platforms, like Phoenix Security, provide automated scanning of code before it hits production, ensuring that flaws don’t make it past the first line of defense. Meanwhile, organizations are also grappling with the backlog crisis in the National Vulnerability Database (NVD). A staggering number of CVEs remain unprocessed, leaving many businesses with limited data on which to base their patching decisions. While these delays leave companies vulnerable, Phoenix Security steps in by cross-referencing CVE data with known exploits and live threat intelligence, helping organizations stay ahead despite the lag in official vulnerability reporting. Whether just starting their security program or managing a complex infrastructure, organizations need a toolset that adapts with them. Phoenix Security enables businesses of any size to prioritize vulnerabilities based on actual risk, not just theoretical impact, helping security teams navigate the evolving threat landscape with speed and accuracy.
Francesco Cipollone
Shai Hulud weaponised npm’s trust model: stolen maintainer creds, poisoned tarballs, and stealthy GitHub Actions that exfiltrate secrets and persist in CI. 500+ packages were touched in days, starting with @ctrl/tinycolor. This analysis maps the blast radius and delivers a practical remediation plan—pin versions, block direct npm with a proxy, rotate tokens, and strip backdoor workflows—grounded in ASPM and reachability.
Francesco Cipollone
A coordinated npm compromise hit @ctrl/tinycolor and dozens of related packages. The payload auto-trojanizes maintainers’ projects, scans for GitHub/NPM/cloud creds using TruffleHog, plants a backdoor GitHub Actions workflow, and exfiltrates to a webhook. This piece breaks down the attack chain and lays out decisive DevSecOps and ASPM actions to contain and harden.
Francesco Cipollone
Derek

Derek Fisher

Head of product security at a global fintech

Derek Fisher – Head of product security at a global fintech. Speaker, instructor, and author in application security.

Derek is an award winning author of a children’s book series in cybersecurity as well as the author of “The Application Security Handbook.” He is a university instructor at Temple University where he teaches software development security to undergraduate and graduate students. He is a speaker on topics in the cybersecurity space and has led teams, large and small, at organizations in the healthcare and financial industries. He has built and matured information security teams as well as implemented organizational information security strategies to reduce the organizations risk.

Derek got his start in the hardware engineering space where he learned about designing circuits and building assemblies for commercial and military applications. He later pursued a computer science degree in order to advance a career in software development. This is where Derek was introduced to cybersecurity and soon caught the bug. He found a mentor to help him grow in cybersecurity and then pursued a graduate degree in the subject.

Since then Derek has worked in the product security space as an architect and leader. He has led teams to deliver more secure software in organizations from multiple industries. His focus has been to raise the security awareness of the engineering organization while maintaining a practice of secure code development, delivery, and operations.

In his role, Jeevan handles a range of tasks, from architecting security solutions to collaborating with Engineering Leadership to address security vulnerabilities at scale and embed security into the fabric of the organization.

Jeevan Singh

Jeevan Singh

Founder of Manicode Security

Jeevan Singh is the Director of Security Engineering at Rippling, with a background spanning various Engineering and Security leadership roles over the course of his career. He’s dedicated to the integration of security practices into software development, working to create a security-aware culture within organizations and imparting security best practices to the team.
In his role, Jeevan handles a range of tasks, from architecting security solutions to collaborating with Engineering Leadership to address security vulnerabilities at scale and embed security into the fabric of the organization.

James

James Berthoty

Founder of Latio Tech

James Berthoty has over ten years of experience across product and security domains. He founded Latio Tech to help companies find the right security tools for their needs without vendor bias.

christophe

Christophe Parisel

Senior Cloud Security Architect

Senior Cloud Security Architect

Chris

Chris Romeo

Co-Founder
Security Journey

Chris Romeo is a leading voice and thinker in application security, threat modeling, and security champions and the CEO of Devici and General Partner at Kerr Ventures. Chris hosts the award-winning “Application Security Podcast,” “The Security Table,” and “The Threat Modeling Podcast” and is a highly rated industry speaker and trainer, featured at the RSA Conference, the AppSec Village @ DefCon, OWASP Global AppSec, ISC2 Security Congress, InfoSec World and All Day DevOps. Chris founded Security Journey, a security education company, leading to an exit in 2022. Chris was the Chief Security Advocate at Cisco, spreading security knowledge through education and champion programs. Chris has twenty-six years of security experience, holding positions across the gamut, including application security, security engineering, incident response, and various Executive roles. Chris holds the CISSP and CSSLP certifications.

jim

Jim Manico

Founder of Manicode Security

Jim Manico is the founder of Manicode Security, where he trains software developers on secure coding and security engineering. Jim is also the founder of Brakeman Security, Inc. and an investor/advisor for Signal Sciences. He is the author of Iron-Clad Java: Building Secure Web Applications (McGraw-Hill), a frequent speaker on secure software practices, and a member of the JavaOne Rockstar speaker community. Jim is also a volunteer for and former board member of the OWASP foundation.

Join our Mailing list!

Get all the latest news, exclusive deals, and feature updates.

The IKIGAI concept
x  Powerful Protection for WordPress, from Shield Security
This Site Is Protected By
ShieldPRO