BLOG

NIST SP 800-53 Rev 5: New Supply Chain Control Requirements

Blog Post by Rob Taylor, Vice President of Solution Delivery at CORL Technologies

The National Institute of Standards and Technology (NIST) has announced an updated version of their flagship security controls framework NIST Special Publication (SP) 800-53. The new version, Revision 5 or “Rev 5”, update is the first overhaul of the NIST SP 800-53 framework in over seven years and represents critical updates that reflect the modern cyber threat landscape. A major addition in this revision includes an entire security controls “family” dedicated to Supply Chain Risk Management (SR).

This blog post will help provide some insight into the new controls framework version, its differences from prior iterations and other related standards, and its applicability for third-party risk management programs.

NIST SP 800-53: The Granddaddy of Security Controls Frameworks

NIST SP 800-53 has historically served as the foundation of US government security controls and has found widespread adoption in critical infrastructure entities and private sector organizations. NIST SP 800-53 Rev 4 was released in April 2013 and was followed up by the creation of the NIST Cybersecurity Framework (CsF) in February of 2014. The NIST CsF was designed to be a more “approachable” security framework that employed more business-friendly language and structure to support adoption both inside and outside of federal entities. As one might expect, NIST has designed the new SP 800-53 Rev 5 controls to integrate and align with the NIST CsF framework.

The new NIST updates have varying implications for specific industry sectors. The federal sector and government entities will need to overhaul their programs in the coming months and years to align with the new control requirements including supply chain and vendor risk management. Healthcare has also depended on NIST for control requirements either directly or via its incorporation into the HITRUST Common Security Framework (HITRUST CSF). The HITRUST Alliance released the HITRUST CSF in 2007 and relied heavily upon NIST SP 800-53 and ISO controls as the foundation of the framework. Note: CORL’s CEO Cliff Baker served as the chief architect of the HITRUST CSF and designed the model that remains in use today to normalize security controls for healthcare entities including NIST SP 800-53, ISO, HIPAA, NIST CsF, state and global regulations, and more.

What’s New: Comparing Rev 4 to Rev 5

According to NIST, Rev 5 is not just a minor update but is a “complete renovation”[1] of the standard. Rev 5 adds more than 45 new base controls, 150 new control extensions, and approximately 100 new parameters to existing controls.

The most significant updates include the addition of controls around third-party risk and supply chain, privacy, and new “state of the practice” areas like cyber resiliency, secure systems design, and governance models. The framework updates have also been designed to scale and apply to a variety of systems and applications from largescale IT and cloud infrastructures down to individual mobile and IoT devices.

Here is a quick view of the control family changes from Rev 4 to Rev 5.

NIST SP 800-53 Rev 4 Control Families

NIST SP 800-53 Rev 5 Control Families

NIST lists the following areas as the most significant changes to the standard.[2] I have included commentary for each are as to how these changes may impact CORL’s clients and the industry more broadly.

  • Integrating supply chain risk management: Rev 5 establishes a new Supply Chain Risk Management (SCRM) control family and integrates supply chain risk management aspects throughout the other control families to help protect system components, products, and services that are part of critical systems and infrastructures. The SCRM controls help ensure that security and privacy requirements, threats, and other concerns are addressed throughout the system development life cycle and the national and international supply chains.

Third-party and vendor risk management has become a dominant theme for security programs in 2020. The volume of third-party applications and systems deployed in our industry is rising daily, with typical organizations leveraging hundreds to thousands of vendors to support critical business functions. The breach trends for these same third-party entities are causing organizations to ramp up investment in vendor risk management programs, teams, and processes.

The addition of supply chain risk management controls to the NIST SP 800-53 catalog is a much needed and long overdue adjustment to reflect the industry’s dependence on third-party vendors.

CORL is in the process of updating our assessment processes to reflect the new NIST Rev 5 controls for organizations that choose to align with this standard. The supply chain controls will also be helpful to drive compliance with third-party vendors and organizations that have built their security programs around NIST models.

  • Making controls outcome-based: Rev 5 accomplishes this by removing the entity responsible for satisfying the control (i.e., information system, organization) from the control statement—thus focusing on the protection outcome to be achieved by the application of the control.Note that for historical continuity, Appendix C, Control Summaries now includes an “implemented by [system/organization]” column.

The movement to outcomes-based controls represents a fundamental mindset shift that will help organizations to move away from a focus on tactical “busy work” and towards strategic outcomes that can measurably reduce risk.

At CORL, this line of outcomes-based thinking has been at the core of our enterprise risk management and reporting services and related industry guidance. Learn more about our recommendations in our blog post, Enterprise Risk Reporting | The Achilles Heel of Vendor Risk Management Programs.

  • Consolidating the control catalog: Information security and privacy controls are now integrated into a seamless, consolidated control catalog for systems and organizations. The privacy controls in Appendix J of Revision 4 have been incorporated into a new privacy family and the existing Program Management family. Some of the privacy controls were also incorporated into current security controls—allowing the controls to serve both the security and privacy communities as well as achieving more efficient control implementation.

Let’s face it, there is an overwhelming volume of security controls to consider when adopting comprehensive standards like NIST 800-53. Adding privacy controls into the mix is a welcome and necessary evolution, but it also contributes to the number and complexity of the overall control catalog. The consolidation of controls and logical restructuring of the framework is a necessary form of “hygiene” for any control framework that strives to keep up with complex and evolving business and threat landscapes. For example in the healthcare industry, the HITRUST Alliance is continually reviewing, revising, and releasing new versions of the HITRUST CSF for this very reason. We suspect another major overhaul to HITRUST will be coming soon to align with NIST SP 800-53 Rev 5.

There are some drawbacks, however, to shuffling the deck with security control standards like NIST 800-53. Historic trending of compliance and maturity of the security program can become challenging to compare apples to apples over time. There is also an educational component wherein security, compliance, and business leaders need to become familiar with the new terminology, structure, and nuances of update control requirements in order to assess, communicate, and apply the new standards effectively.

  • Separating the control selection process from the controls: Having a consolidated, stand-alone control catalog allows the controls to be used by different communities of interest, including systems engineers, security architects, software developers, enterprise architects, systems security and privacy engineers, and mission or business owners. These communities of interest can now better collaborate on points of intersection or use an individualized process as needed for selecting controls to manage risk consistent with their mission and business needs as well as internal organizational policies and procedures.

For many organizations, this change may be a helpful way to open up the dialog around security controls and standards to stakeholders and audiences outside of the security, risk, IT, and compliance teams. NIST SP 800-53 has traditionally been known to use some fairly antiquated “tech speak” that can be challenging to use when communicating with non-technical audiences.

In practical terms, we interpret this to mean that the guidelines and control baselines may evolve over time. Having a separate document and forum for communicating those changes and guidelines makes sense so that we don’t need to wait another seven years to have the NIST catalog update to reflect our rapidly changing businesses and threat landscape.

  • Improving descriptions of content relationships: Rev 5 clarifies the relationship between requirements and controls as well as the relationship between security and privacy controls. These relationships are important to understand whether you are selecting and implementing controls at the enterprise level or as part of a life cycle-based systems engineering process.

There are significant dependencies between security and privacy functions for most organizations. Understanding the inter-relationship and overlap between those controls is essential to effective privacy and security risk management for the enterprise.

  • Adding new state-of-the-practice controls: As cyber threats evolve rapidly, new safeguards and countermeasures are needed to protect the critical and high value assets of organizations including individual’s privacy and personally identifiable information. The new controls in Rev 5 are based on the latest threat intelligence and cyber-attack data (e.g., controls to support cyber resiliency, secure systems design, security and privacy governance, and accountability).

Agility to adapt to evolving threats will be critical for the successful deployment of the new NIST controls. These latest controls provide a useful mechanism to get a handle on threats that face our organizations in the near term. These threats evolve quickly, however, so don’t wait too long to check out these updates before they have the potential to become stale.

Closing Thoughts: What’s Next?

NIST SP 800-53 Rev 5 is a welcome addition and update to the security controls catalog for the cybersecurity and risk management industry.

For organizations that are currently using NIST SP 800-53 Rev 4 as the foundation for their programs, this update will require some near-term strategic planning and tactical updates heading into 2021 to calibrate the program to the new requirements. This includes updating policy and procedure documentation, risk analysis models, and reporting at a minimum. Given the large-scale overhaul of the controls, it will also require some substantive implementation work to rollout new and updated controls. These initiatives will need to be balanced against the organization’s overall security, privacy, and risk strategic plans and prioritized accordingly alongside other remediation efforts.

The strong emphasis on supply chain controls in Rev 5 demonstrates that third-party risk is fast becoming a requirement for enterprises via standards like NIST alongside the evolving regulatory space which often points to NIST for compliance mandates and leading practices.

Contact our team here at CORL to learn more about the NIST SP 800-53 Rev 5 changes and to discuss implications for your organization.


Most Recent Posts
Selecting the Right Technology for Your Third-Party Risk Management Program Read More
Healthcare’s Gamble with Business Associate Breach Risks Read More
Explaining CORL's Processes to Vendors Read More