That means software manufacturers should ensure security is a core consideration from the onset of development.
To that end the Cybersecurity and Infrastructure Security Agency (CISA) and the Federal Bureau of Investigation (FBI) released joint guidance on what not to do, or an overview of product security bad practices deemed exceptionally risky, particularly for software manufacturers who produce software used in service of critical infrastructure or national critical functions (NCFs).
The guidance also provides recommendations for software manufacturers to mitigate these risks.
A goal with the guidance is to urge software manufacturers to reduce customer risk by prioritizing security throughout the product development process.
CISA and the FBI divided the bad practices into three categories.
- Product properties, which describe the observable, security-related qualities of a software product.
- Security features, which describe the security functionalities that a product supports.
- Organizational processes and policies, which describe the actions taken by a software manufacturer to ensure strong transparency in its approach to security.
For product properties, bad practices include:
- Development in memory unsafe languages
- Inclusion of user-provided input in SQL query strings
- Inclusion of user-provided input in operating system command strings
- Presence of default passwords
- Presence of known exploited vulnerabilities
- Presence of open source software with known exploitable vulnerabilities
In terms of security features, bad practices include:
- Lack of multifactor authentication
- Lack of capability to gather evidence of intrusions
When looking at organizational processes and policies, bad practices include:
- Failing to publish timely CVEs with CWEs
- Failing to publish a vulnerability disclosure policy
Click here for more on the guidance.

