Most software needs updating after its initial release to address bugs, newly identified vulnerabilities, and revisions to features and functionality.

But software patches and other changes can introduce new cybersecurity and privacy risks and can impair operations if not managed effectively.

In an effort to support successful, secure software updates and patches, the National Institute of Standards and Technology (NIST) finalized modifications to its catalog of security and privacy safeguards to assist developers who create patches and the organizations that receive and implement them in their own systems.

IT professionals will instantly recognize this catalog as one of NIST’s flagship risk management publications: “Security and Privacy Controls for Information Systems and Organizations.”

The catalog is a compilation of security and privacy safeguards, called controls, for strengthening the systems, products and services that underlie the nation’s businesses, government and critical infrastructure.

Schneider Bold
Fulfilling Executive Order

The modifications respond to Executive Order 14306, Sustaining Select Efforts to Strengthen the Nation’s Cybersecurity and Amending Executive Order 13694 and Executive Order 14144.

Completed with the help of a new commenting system in which stakeholders could provide feedback to proposed changes in real time and preview the proposed revisions prior to final publication, the update is available in several electronic formats.

“The changes emphasize secure software development practices, and to help organizations understand their role in ensuring the security of the software on their systems,” said NIST computer scientist Victoria Pillitteri, who led the project. “Ultimately, we want to help them achieve their goals while minimizing the risk of a patch creating unintended consequences.”

Most software has direct exposure to the Internet, which puts it at significant risk of compromise. Patching is a critical component of preventive maintenance that helps reduce the risk of data breaches and other adverse events.

Update management can be challenging because of the need to balance the trade-offs between deploying patches quickly to address critical vulnerabilities or bugs and thoroughly testing to ensure critical functions and services are not affected.

Once a vendor detects a vulnerability in its software, deploying a patch quickly reduces the window of opportunity for attackers, but it increases the risk the less thoroughly tested patch might disrupt an organization’s operations. Conversely, thorough testing decreases the risk of operational disruption but increases the window of opportunity for attackers.

“The updated controls emphasize the importance of monitoring the particular component being updated as well as the component’s relationship to the overall system,” Pillitteri said.

The changes to the catalog address multiple aspects of the software development and deployment process.

New Controls in Catalog

Among the changes are three entirely new controls:
Logging syntax: (SA-15) defines an electronic format for recording security-related events to support better incident response. Defining data formats facilitates automation and helps teams more quickly reconstruct security-related incidents.
Root cause analysis: (SI-02(07)) specifies conducting a review to find the cause of an issue or failure with the software update and coming up with an action plan and implementing it.
Design for cyber resiliency: (SA-24) recommends designing systems for survivability – the ability to anticipate, withstand, respond and recover from attack while maintaining critical functions.

The update also revises the technical content of some existing controls and provides additional examples of how to implement them.

“We are trying to keep this comprehensive set of security and privacy controls agile,” Pillitteri said. “NIST can now develop and rapidly issue updates to this guideline while coordinating with stakeholders in a transparent way that meets customer demand. It’s part of our effort to develop and issue standards at the pace of technology.”

Pin It on Pinterest

Share This