With that in mind, some vendors have taken this seriously and made great strides driving the industry forward in software assurance, while others continue to lag behind leaving their customers facing attacks on products they don’t know are vulnerable.
That is where “Shifting the Balance of Cybersecurity Risk: Security-by-Design and Default Principles” comes in. This is a document released Thursday and created by Cybersecurity and Infrastructure Security Agency (CISA), Federal Bureau of Investigation, National Security Agency, Australian Cyber Security Centre, Canadian Centre for Cyber Security, New Zealand’s Computer Emergency Response Team, United Kingdom’s National Cyber Security Centre, Germany’s Federal Office for Information Security (BSI), and the Netherlands’ National Cyber Security Centre.
The document encourages every technology manufacturer to build their products in a way that prevents customers from having to constantly perform monitoring, routine updates, and damage control on their systems to mitigate cyber intrusions. This way, manufacturers are encouraged to take ownership of improving the security outcomes of their customers.
Fixes After the Fact
Historically, technology manufacturers have relied on fixing vulnerabilities found after the customers have deployed the products, requiring the customers to apply those patches at their own expense. Incorporating Secure-by-Design practices will break the vicious cycle of creating and applying fixes.
To create a future where technology and associated products are safer, the authoring agencies urge manufacturers to revamp their design and development programs to permit only Secure-by-Design and -Default products to be shipped to customers. Products Secure-by-Design are those where the security of the customers is a core business goal, not just a technical feature. Secure-by-Design products start with that goal before development starts. Secure-by-Default products are those that are secure to use “out of the box” with little to no configuration changes necessary and security features available without additional cost.
“Secure-by-Design” means technology products are built in a way that reasonably protects against malicious cyber actors successfully gaining access to devices, data, and connected infrastructure. Software manufacturers should perform a risk assessment to identify and enumerate prevalent cyber threats to critical systems, and then include protections in product blueprints that account for the evolving cyber threat landscape.
Secure information technology (IT) development practices and multiple layers of defense are also recommended to prevent adversary activity from compromising systems or obtaining unauthorized access to sensitive data. Manufacturers should use a tailored threat model during the product development stage to address all potential threats to a system and account for each system’s deployment process, according to the guidance.
Manufacturers to take a holistic security approach for their products and platforms. Secure-by-Design development requires the investment of significant resources by software manufacturers at each layer of the product design and development process that cannot be “bolted on” later, according to the guidance.
Security a Strong Priority
It requires strong leadership by the manufacturer’s top business executives to make security a business priority, not just a technical feature. This collaboration between business leaders and technical teams extends from the early stages of design and development, through customer deployment and maintenance. Manufacturers are encouraged make hard tradeoffs and investments, including those that will be “invisible” to the customers, such as migrating to programming languages that eliminate widespread vulnerabilities. They should prioritize features, mechanisms, and implementation of tools that protect customers rather than product features that seem appealing but enlarge the attack surface, according to the guidance.
“Secure-by-Default” means products are resilient against prevalent exploitation techniques out of the box without additional charge. These products protect against the most prevalent threats and vulnerabilities without end-users having to take additional steps to secure them. Secure-by-Default products make customers acutely aware when they deviate from safe defaults, they are increasing the likelihood of compromise unless they implement additional compensating controls.
A secure configuration should be the default baseline. Secure-by-Default products automatically enable the most important security controls needed to protect enterprises from malicious cyber actors, as well as provide the ability to use and further configure security controls at no additional cost.
The complexity of security configuration should not be a customer problem. Organizational IT staff are frequently overloaded with security and operational responsibilities, thus resulting in limited time to understand and implement the security implications and mitigations required for a robust cybersecurity posture. Through optimizing secure product configuration – securing the “default path” – manufacturers can aid their customers by ensuring their products are manufactured, distributed, and used securely in accordance with “Secure-by-Default” standards.
Security Not a Luxury Item
Manufacturers of products that are “Secure-by-Default” do not charge extra for implementing additional security configurations. Instead, they include them in the base product like seatbelts are included in all new cars. Security is not a luxury option but is closer to the standard every customer should expect.
To that end, there are recommendations to manufacturers for developing a written roadmap to implement and ensure IT security, according to the guidance. Software manufacturers should implement strategies to take ownership of the security outcomes of their customers through Secure-by-Design and -Default principles.
Technology manufacturers should adopt a strategic focus that prioritizes software security. There are three core principles to guide software manufacturers in building software security into their design processes prior to developing, configuring, and shipping their products:
1. The burden of security should not fall solely on the customer. Software manufacturers should take ownership of the security outcomes of their customer’s purchase and evolve their products accordingly.
2. Embrace radical transparency and accountability. Software manufacturers should pride themselves in delivering safe and secure products, as well as differentiating themselves among the rest of the manufacturer community based on their ability to do so. This may include sharing information they learn from their customer deployments, such as the uptake of strong authentication mechanisms by default. It also includes a strong commitment to ensure vulnerability advisories and associated common vulnerability and exposure (CVE) records are complete and accurate. However, beware of the temptation to count CVEs as a negative metric, since such numbers are also a sign of a healthy code analysis and testing community.
3. Build organizational structure and leadership to achieve these goals. While technical subject matter expertise is critical to product security, senior executives are the primary decision makers for implementing change in an organization. Executive-level commitment for software manufacturers to prioritize security as a critical element of product development requires the development of partnerships with an organization’s customers to understand:
— The product deployment scenario guidance along with tailored threat model.
— Proposed implementation for security controls to align to Secure-by-Default principles.
— Resource allocation strategies tailored to company size and the ability to replace legacy development practices with Secure-by-Design practices.
— The need to maintain an open line of communication for feedback internally and externally (e.g., employee and customer feedback) regarding product security issues. Software security should be emphasized in internal forums (e.g., all-hands or brown bags), as well as external product marketing and customer engagement.
— Measurements of effectiveness within customer deployments. Senior executive leaders will want to know where investments in security by design and default are helping customers by slowing the pace of security patches, reducing configuration errors, and minimizing attack surface.
Operational Tactics
To enable these three principles, manufacturers should consider several operational tactics to evolve their development processes.
Convene routine meetings with company executive leadership to drive the importance of Secure-by-Design and Secure-by-Default within the organization. Policies and procedures should be established to reward production teams that develop products adhering to these principles, which could include awards for implementing outstanding software security practices or incentives for job ladders and promotion criteria.
Operate around the importance of software security to business success. For example, consider assigning a “software security leader” or a “software security team” that upholds business and IT practices to directly link software security standards and manufacturer accountability. Manufacturers should ensure they have robust, independent product security assessment and evaluation programs for their products.
Use a tailored threat model during development to prioritize the most critical and high-impact products. Threat models consider a product’s specific use-case and enables development teams to fortify products. Finally, senior leadership should hold teams accountable for delivering secure products as a key element of product excellence and quality.
Click here for more on the Shifting the Balance of Cybersecurity Risk: Security-by-Design and Default Principles.

