# CISA's Secure By Demand: Improving Product Security During Software Procurement

**Published on:** 2024-08-27T00:00:00.000Z

**Author:** null

[Supply chain security](https://www.packetlabs.net/posts/digital-supply-chain/) is the intersection of [enterprise cybersecurity](https://www.packetlabs.net/posts/what-is-new-in-the-nist-cybersecurity-framework-version-20/) and [third-party](https://www.packetlabs.net/posts/third-party-risk-management/) product security. Enterprise security focuses on protecting a company's [internal infrastructure](https://www.packetlabs.net/posts/internal-and-external-penetration-testing/) and daily operations from threats. It encompasses measures like [firewalls](https://www.packetlabs.net/posts/how-do-attackers-bypass-firewalls/), [intrusion detection systems](https://www.packetlabs.net/posts/intrusion-detection-system/), [data encryption](https://www.packetlabs.net/posts/encryption-encoding-and-hashing/), and employee training to safeguard [sensitive information](https://www.packetlabs.net/posts/secure-personally-identifiable-information/), ensure [business continuity](https://www.packetlabs.net/posts/responding-to-ransomware-attack/), and maintain [compliance with regulations](https://www.packetlabs.net/posts/how-to-prepare-for-new-cybersecurity-regulations/). The goal is to create a secure environment that prevents [unauthorized access](https://www.packetlabs.net/posts/protect-network-from-unauthorized-access/), [data breaches](https://www.packetlabs.net/posts/the-biggest-cyberattacks-in-canada/), and other cyber threats.

On the other hand, product security is about ensuring that the software or products a company [develops](https://www.packetlabs.net/services/devsecops/) and delivers are secure for users. According to CISA, organizations need to be active stakeholders in the product security posture of the vendors whose products they use.

This involves ensuring that vendors [secure coding practices](https://www.packetlabs.net/services/devsecops/), regular [security testing](https://www.packetlabs.net/posts/post-crowdstrike-fallout-a-review-of-15-key-application-security-testing/), and updates to [patch security flaws](https://www.packetlabs.net/posts/is-your-organization-prepared-for-vulnerability-disclosure/). The objective is to prevent attackers from [exploiting weaknesses](https://www.packetlabs.net/posts/cwe-top-10-most-dangerous-software-weaknesses-for-2023/) in the product to compromise user data or systems. While both enterprise security and product security aim to defend against cyber threats, the former focuses on the company's own assets, and the latter prioritizes the safety of the end-user experience.

## What is "Secure By Demand"?

[Secure By Demand](https://www.cisa.gov/resources-tools/resources/secure-demand-guide) is a proactive approach that customers can take by explicitly demanding secure design practices from software manufacturers during the [procurement process](https://www.cisa.gov/resources-tools/resources/software-acquisition-guide-government-enterprise-consumers-software-assurance-cyber-supply-chain). This concept emphasizes that [supply chain security](https://www.packetlabs.net/posts/third-party-risk/) should not be an afterthought but a fundamental requirement in the software development lifecycle. By playing an active role in setting security expectations, organizations ensure that the products they purchase are built with security as a core principle, aligning with best practices like those outlined by [CISA’s Secure by Design](https://www.cisa.gov/securebydesign) initiative.

Secure By Demand encourages transparency, accountability, and the prioritization of security features, such as secure authentication, elimination of vulnerabilities, and robust incident detection capabilities, thus creating a safer technology ecosystem for all users.

## CISA's Recommendation For Improving Software Product Security 

The Cybersecurity and Infrastructure Security Agency (CISA) recommends that organizations adopt a ["Secure By Demand" approach](https://www.cisa.gov/resources-tools/resources/secure-demand-guide) to enhance software product security. This involves prioritizing security at every stage of the [software development](https://www.packetlabs.net/posts/devsecops/) and [procurement process](https://www.packetlabs.net/roles/procurement/). CISA urges software manufacturers to [make security a foundational aspect](https://www.packetlabs.net/posts/cybersecurity-risk-management/) of their products, focusing on practices like secure coding, regular [application security assessments](https://www.packetlabs.net/posts/guide-to-application-security-testing/), and [timely patch management](https://www.packetlabs.net/posts/establishing-best-practices-for-effective-responsible-disclosure-channels/). 

By demanding secure-by-design principles, customers can reduce their risk of being [exploited by ransomware](https://www.packetlabs.net/posts/pentesting-helps-prevent-ransomware-attacks/), data breaches, and other malicious activities. CISA also encourages customers to ask their software providers about their commitment to secure-by-design practices, transparency in vulnerability reporting, and their support for secure authentication methods. Taking these proactive steps can significantly enhance the security posture of both individual organizations and the broader technology environment.

### Consider Security During the Entire Procurement Lifecycle

CISA emphasizes the importance of product security throughout the entire software procurement lifecycle. Before purchasing software, organizations should assess each vendor's security practices by asking targeted questions about their approach to product security and adherence to [secure-by-design](https://www.packetlabs.net/posts/global-governments-advise-a-security-by-design-cyber-strategy/) principles. 

During procurement, it's essential to include specific security requirements in a binding contract such as a service level agreement (SLA) ensuring that security is a non-negotiable aspect of the agreement. After procurement, organizations should [continuously monitor](https://www.packetlabs.net/posts/continuous-pentests/) and assess the security of the software products they use, keeping up with updates, patches, and any newly discovered vulnerabilities. By integrating security considerations into every stage of the procurement process, organizations can help ensure that the products they use are robust against cyber threats, thereby safeguarding their own infrastructure and operations.

## Questions to Consider For Software Product Security

To ensure the software products they purchase are secure, organizations should ask their software manufacturers critical questions that highlight their security practices:

1.  **Has the manufacturer committed to** [**CISA’s Secure by Design Pledge**](https://www.packetlabs.net/posts/cisa-helping-us-critical-infrastructure/)**?**
    
    *   This commitment indicates a public dedication to security principles.
        
2.  **How does the manufacturer handle security patches and updates?**
    
    *   Are updates and patches easy to install, widely supported, and are automatic update features supported?
        
3.  **Does the software support secure authentication methods, like multi-factor authentication (MFA)?**
    
    *   Verify that secure, [phishing-resistant MFA](https://www.packetlabs.net/posts/what-are-mfa-fatigue-attacks/) is available and that [default passwords](https://www.packetlabs.net/posts/are-you-guilty-of-these-password-sins/) are eliminated.
        
4.  **What steps has the manufacturer taken to address common vulnerabilities?**
    
    *   Look for efforts to eliminate entire [classes of vulnerabilities](https://www.packetlabs.net/posts/cwe-top-10-most-dangerous-software-weaknesses-for-2023/), such as using [memory-safe programming languages](https://www.packetlabs.net/posts/what-are-memory-safe-languages/) or preventing [SQL injections](https://www.packetlabs.net/posts/types-of-sql-injection/).
        
5.  **Does the manufacturer provide security features such as logs?**
    
    *   Security features should be available at no additional cost, especially for [cloud apps](https://www.packetlabs.net/posts/guide-to-cloud-penetration-testing/) and [SaaS products](https://www.packetlabs.net/posts/saas-cybersecurity/).
        
6.  **How does the manufacturer manage the security of third-party components?**
    
    *   Confirm that they maintain a software bill of materials (SBOM) and have processes to ensure the security of open-source and third-party [software dependencies](https://www.packetlabs.net/posts/policies-processes-and-tools-for-managing-software-dependency-security/).
        

## Conclusion

Adopting a Secure By Demand approach is crucial for enhancing software product security and building a safer technology ecosystem. By making security a key consideration from the earliest stages of the procurement lifecycle, organizations can significantly mitigate risks associated with cyber threats. CISA’s guidance encourages customers to ask probing questions about a manufacturer’s security practices and to integrate security requirements into contracts.

This proactive stance not only protects the organization but also drives broader industry standards for product security, ultimately contributing to the protection of critical infrastructure and digital assets. By demanding secure-by-design products, organizations play a vital role in promoting a resilient cybersecurity landscape.
