Software is the way of the manufacturing world, but the idea of a safe and secure delivery of new software or updates is becoming more murky with the constantly evolving and complex deployment process.

Updates may enhance features and/or address security vulnerabilities to provide benefits and security to customers. But it is critical for all software manufacturers to implement a safe software deployment program supported by verified processes, including robust testing and measurements.

That is why the Cybersecurity and Infrastructure Security Agency (CISA), Federal Bureau of Investigation (FBI) and the Australian Signals Directorate’s (ASD’s) Australian Cyber Security Centre (ACSC) issued a joint guidance entitled, “Safe Software Deployment: How Software Manufacturers Can Ensure Reliability for Customers.”

This guide encourages software manufacturers to establish a safe software deployment program as part of their software development lifecycle (SDLC).

Security Starts Early
Software manufacturers should incorporate safe deployment practices early in the SDLC. Safe deployment processes do not begin with the first push of code; they start much earlier. To maintain product quality and reliability, technology leaders should ensure all code and configuration changes pass through a series of well-defined phases supported by a robust testing strategy, according to the guidance.

Schneider Bold

The basis for these phases is to catch any new issues and regressions, reducing the risk of flawed software.

This guidance is part of CISA’s Secure by Design campaign. The guide is primarily for software or service manufacturers deploying software to many types of customer systems, including mobile devices and laptops, as well as for cloud-based services.

A safe software deployment process aims to achieve several key objectives. These objectives help ensure software is not only reliable, safe, and secure for customers, but deployed in a controlled, efficient manner.

By incorporating mechanisms for timely issue detection, continuous improvement, and support for agile development, the safe software deployment process empowers teams to deliver high-quality software while adapting to changing requirements and technologies.

The mechanisms include:
Quality processes: Robust quality assurance processes help ensure software products function consistently and meet customer expectations without causing disruptions. This focus on reliability enhances customer safety by reducing the risk of failures that could compromise critical systems or data, resulting in increased customer trust.

Cost and impact management: For software manufacturers, technical and process defects cost less to remediate when they catch defects early in the process and cause less damage to customer systems. Customers suffering an impact by these defects can suffer downtime and data loss, adversely affecting their financial and reputational positions.

Controlled and measured deployments: A well-defined deployment strategy includes phased rollouts, such as canary releases, allowing manufacturers to monitor performance in real-world environments without impacting all customers at once. This reduces the risk of widespread failures and provides valuable data to refine subsequent deployments.

Comprehensive testing: Early detection through comprehensive testing strategies, including automated testing and monitoring tools, allows teams to identify and address defects before they escalate into larger problems. Proactively catching issues early improves the quality of a product and reduces the likelihood of expensive fixes later.

Continuous improvement: Feedback loops integrated into the development and deployment processes enable teams to learn from each iteration and apply those lessons to future releases. Using feedback loops helps evolve the safe software deployment process and improves maintenance practices of security standards, as well as improves performance, and better meets the needs of users. It is important to include “near misses” in the feedback loop. “Near misses” provide an opportunity to enhance the program without the software manufacturer or their customers experiencing the full negative impact of an actual incident.

Optimize for agility: Teams should be able to adapt quickly to changes in requirements, emerging technologies, and security threats. Shorter development cycles, collaboration, and iterative improvements help deliver high-quality software that meets evolving customer expectations.

Secure development ecosystem: A secure development ecosystem can support developers while reducing the likelihood of defects entering the code base. Software manufacturers have a greater chance of detecting and blocking issues earlier by implementing automated technical controls throughout the development ecosystem.

Click here for more on the Safe Software Deployment: How Software Manufacturers Can Ensure Reliability for Customers joint guidance.

Pin It on Pinterest

Share This