On October 12, 2024, the Cybersecurity and Infrastructure Security Agency (CISA) and the Federal Bureau of Investigation (FBI) released a critical document for public comment: the “Product Security Bad Practices” catalog. This initiative, aimed at strengthening national cybersecurity, highlights harmful software development practices that expose critical infrastructure and organizations to malicious cyberattacks. By encouraging software manufacturers to avoid these risky practices, especially in systems supporting critical national functions (NCFs), this guidance is an essential step toward improving software security.
This announcement underscores the growing concern over the software vulnerabilities that continue to fuel cyberattacks against hospitals, schools, government facilities, and other key sectors. The public comment period runs until December 2, 2024, offering stakeholders the opportunity to contribute their insights to shape the future of cybersecurity.
The Push for Secure by Design
The “Product Security Bad Practices” catalog is part of CISA’s broader “Secure by Design” initiative, which promotes the development of secure software by default. With increasing attacks on critical infrastructure, ranging from healthcare facilities to energy providers, the emphasis on software manufacturers taking accountability for the security of their products is greater than ever.
In the last year alone, cybercriminals have exploited software vulnerabilities, leading to high-profile attacks like the disruption of hospital services and network breaches in major industries. Jen Easterly, Director of CISA, noted: “In 2024, preventable software defects should no longer be the norm, yet they continue to wreak havoc. The bad practices outlined in this catalog are all too common, but they pose unacceptable risks.”
Similarly, Bryan Vorndran, Assistant Director of the FBI’s Cyber Division, emphasized the national security implications of insecure software: “Bad practices in software development expose our infrastructure to vulnerabilities that are routinely exploited by malicious actors. Software manufacturers must take immediate action to prevent these vulnerabilities from being baked into their products.”
The Catalog: Three Key Categories of Bad Practices
CISA’s new catalog identifies specific software development pitfalls that need to be avoided to bolster security. The practices are divided into three primary categories:
- Product Properties: These refer to the inherent qualities of the software that can create security risks. Examples include software lacking secure default settings or those with unprotected default credentials.
- Security Features: The catalog also points out weaknesses in security functionalities, such as inadequate encryption mechanisms, lack of multifactor authentication, or insufficient patch management systems.
- Organizational Processes and Policies: This category targets the governance side of software development, urging manufacturers to foster transparency, implement security-first policies, and ensure continuous security assessments throughout the software development lifecycle.
A Collective Effort for Safer Products
The “Secure by Design” initiative already has over 220 software manufacturers committed to making security a priority. This latest step aims to expand that commitment globally. By encouraging public feedback, CISA and the FBI hope to further refine this list of bad practices and provide even more comprehensive guidance to software developers worldwide.
These bad practices are particularly critical in sectors that impact national critical functions (NCFs), such as telecommunications, healthcare, finance, and energy. The focus on public comment allows cybersecurity professionals, software developers, and stakeholders to share their expertise and help craft a robust final document that is both effective and practical.
Ten Tips to Avoid Security Risks in Software Development:
To prevent software vulnerabilities and reduce the threat of cyberattacks, software manufacturers and organizations can follow these essential practices:
- Adopt Secure by Design Principles: Integrate security into the development process from the beginning rather than adding it as an afterthought.
- Regular Security Audits: Conduct frequent security audits to identify and patch vulnerabilities in code before attackers can exploit them.
- Implement Multifactor Authentication (MFA): Ensure that products support and require MFA for all access points, making unauthorized access more difficult.
- Use Strong Encryption: Implement robust encryption protocols for data both in transit and at rest, minimizing the risk of data breaches.
- Frequent Patch Management: Establish a rapid patch management process to address vulnerabilities as soon as they are discovered.
- Test for Default Credentials: Ensure that default passwords and credentials are removed or changed, as these are frequently exploited by attackers.
- Provide Transparency in Security Practices: Communicate openly with users about security features and updates to build trust and empower users to protect their systems.
- Emphasize Threat Modeling: Conduct regular threat modeling to anticipate potential attack vectors and preemptively address weaknesses.
- Foster a Security Culture: Encourage a strong security-first mindset throughout the organization, with continuous training and awareness programs.
- Establish a Bug Bounty Program: Engage with ethical hackers through bug bounty programs to identify vulnerabilities that internal teams may overlook.
Conclusion:
CISA and the FBI’s “Product Security Bad Practices” catalog is an essential tool in the ongoing battle to secure our critical infrastructure and digital systems. By providing a clear framework for identifying and avoiding dangerous software development practices, this guidance not only supports the cybersecurity community but also reinforces the shared responsibility between software manufacturers and end-users.
As cyber threats continue to evolve, collaborative efforts between government agencies, the private sector, and the cybersecurity industry are vital. The public comment period represents a unique opportunity for professionals to contribute to the creation of stronger, more secure software, ensuring that products critical to national security are safeguarded against evolving threats.
Want to stay on top of cybersecurity news? Follow us on Facebook – X (Twitter) – Instagram – LinkedIn – for the latest threats, insights, and updates!
