Companies in the stages of needing to purchase software to advance their organization’s manufacturing enterprise, often know they need the technology, but don’t know the security behind all the code.

That is why organizations buying software need to better understand a software manufacturer’s approach to cybersecurity and ensure the manufacturer makes secure by design a core consideration.

To that end, the Cybersecurity and Infrastructure Security Agency (CISA) and the Federal Bureau of Investigation (FBI)created a guidance is a counterpart to its Secure by Design guidance for technology manufacturers, which lays out three secure by design principles:

  1. Take ownership of customer security outcomes
  2. Embrace radical transparency and accountability
  3. Build organizational structure and leadership to achieve these goals

When companies perform due diligence of their software manufacturers, they often focus on the enterprise security measures of the manufacturers, such as by ensuring the manufacturers meet various compliance standards.

While enterprise security is important, customers also need to focus on how a manufacturer approaches product security. Enterprise security refers to practices to protect a company’s own infrastructure and operations, while product security refers to actions the software manufacturer takes to ensure the products they deliver are secure against attackers.

Schneider Bold

There are plenty of compliance standards that organizations use during procurement that focus on enterprise security; conversely, relatively few focus on product security. This guide attempts to bridge that gap by offering resources organizations can leverage to assess product security maturity and whether a manufacturer follows secure by design principles.

Organizations can integrate product security considerations into various stages of the procurement lifecycle:

Before procurement: Posing questions to understand each candidate software manufacturer’s approach to product security

During procurement: Integrating product security requirements into contract language, as appropriate

Following procurement: Continually assessing software manufacturers’ product security and security outcomes

The following are questions organizations can use as a starting point for assessing a software manufacturer’s approach to product security:

  • Has the manufacturer taken CISA’s Secure by Design Pledge?
  • What progress reports has the manufacturer published in line with its commitments to the pledge?
  • How does the manufacturer make it simple for customers to install security patches?
  • Does it offer support for security patches on a widespread basis and enable functionality for automatic updates?
  • Does the manufacturer support integrating standards-based single sign-on (SSO) for customers at no additional cost?
  • If the software manufacturer manages authentication, does it enable multi-factor authentication (MFA) or other phishing-resistant forms of authentication like passkeys by default, and at no cost?
  • Has the software manufacturer eliminated default passwords in its products? If not, is it working to reduce the use of default passwords across its product lines?
  • What classes of vulnerability has the software manufacturer systematically addressed in their products?
  • For those that they haven’t yet addressed, do they have a roadmap showing how they plan to eliminate those classes of vulnerability?

Click here for more on the Secure by Demand guidance.

Pin It on Pinterest

Share This