It is no secret in the cyber world, software manufacturers need to ensure security is a core consideration from the onset of software development and throughout the entire lifecycle.

To that end, the Cybersecurity and Infrastructure Security Agency’s (CISA’s) and the Federal Bureau of Investigation (FBI) created a guidance in its Secure by Design initiative, and one aspect of that is to discuss and eliminate bad product security practices.

This voluntary guidance – created in October and now updated – provides an overview of product security bad practices that are considered exceptionally risky, particularly for software manufacturers who produce software used in service of critical infrastructure or national critical functions (NCFs).

This guidance also offers recommendations for software manufacturers to mitigate these risks.

The goal behind the guidance is to urge software manufacturers to reduce customer risk by prioritizing security throughout the product lifecycle. This document is for software manufacturers who develop software products and services, including on-premises software, cloud services, and software as a service (SaaS).

Schneider Bold
Eye on Bad Practices

This also applies to software products that run on operational technology (OT) products or embedded systems. CISA and FBI encourage all software manufacturers to avoid these product security bad practices. By following the recommendations in this guidance, manufacturers will show they are taking ownership of customer security outcomes, a key secure by design principle. The guidance contained in this document is non-binding, and while the authoring organizations encourage avoiding these bad practices, this document imposes no requirement to do so.

The bad practices are divided into three categories.

  1. Product properties, which describe the observable, security-related qualities of a software product
  2. Security features, which describe the security functionalities that a product supports
  3. Organizational processes and policies, which describe the actions taken by a software manufacturer to ensure strong transparency in its approach to security

Product properties: The development of new product lines for use in service of critical infrastructure or NCFs in a memory-unsafe language where readily available alternative memory-safe languages could end up used is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety.

For existing products written in memory-unsafe languages, not having a published memory safety roadmap is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety.

Security features: For use in service of critical infrastructure or national critical functions, Information technology (IT) products that do not support multi-factor authentication (MFA), including phishing-resistant MFA, in the baseline version of the product are dangerous and significantly elevate risk to national security, national economic security, and national public health and safety.

Additionally, IT products that do not enable MFA by default for administrator accounts are dangerous and significantly elevate risk to national security, national economic security, and national public health and safety.

Processes and Policies

Organizational processes and policies: It is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety for the software manufacturer of products used in service of critical infrastructure or NCFs to not issue CVEs in a timely manner for, at minimum, all critical or high impact vulnerabilities.

Additionally, it is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety to not include the CWE field in every CVE record.

Click here for more on the guidance on product security bad practices.

Pin It on Pinterest

Share This