Request Demo

NIST Cybersecurity Framework

Breaking Down the NIST Cybersecurity Framework: Recover


In the past few blog posts, we've been going over the five NIST Framework functions. In the last blog post, we covered the Respond function. In this post, we'll be going over the last Framework function, Recover.

"The Framework Core then identifies underlying key Categories and Subcategories for each Function, and matches them with example Informative References such as existing standards, guidelines, and practices for each Sub category" - NIST CSF

According to NIST, Recover is defined as the need to "develop and implement the appropriate activities to maintain plans for resilience and to restore any capabilities or services that were impaired due to a cyber security event.

The Recover Function support s timely recovery to normal operations to reduce the impact from a cybersecurity event. Examples of outcomes for this function include : Recovery Planning, Improvements, and Communications."

Recover includes these areas:

  • Recovery Planning: Recovery procedures are tested, executed, and maintained so that your program can mitigate the effects of an event sooner rather than later
  • Improvement: Recovery planning and processes are improved when events happen and areas for imporvement are identified and solutions put together
  • Communication: Coordinate internally and externally for greater organization, thorough planning and execution

The recover function is important not only in the eyes of your business or organization in recovering from an attack, but also in the eyes of your customers or market. Swift recovery handled with grace and tactfullness will allow you to end up in a much stronger position internally and externally than you would otherwise. Prioritizing these focus areas within recover will enure that your organization has a recovery plan that is up to date and matches your organiztion's goals and objectives.

CyberStrong streamlines all your compliance regs while giving visibility into NIST CSF best practices..


You may also like

Why GRC Needs IRM
on February 15, 2019

Today, every organization strives to optimize the speed with which they access information. Data is being stored, processed, transmitted and utilized in almost every day-to-day ...

Alison Furneaux
Government Shutdown Cybersecurity ...
on February 12, 2019

In January, CyberSaint CEO George Wrenn penned his thoughts on the impact of the government shutdown. In his post, George foresaw the outcome of the shutdown not being a future ...

The Cybersecurity Skills Gap: The ...
on February 7, 2019

The cybersecurity skills gap is nothing new to the seasoned cyber professional. It has been widely discussed in cyber and information security circles for some time. The main flag ...

George Wrenn
The Post-Digitization CISO
on February 5, 2019

Information leaders in digital businesses, whether focusing on optimization or a full transformation, are inherently altering their position among the executive leadership. As ...

Integrated Risk Management and ...
on January 31, 2019

With technology permeating every aspect of a business, one begins to wonder what technology is reserved for digital risk management rather than the other facets of integrated risk ...

Department of Defense Launches ...
on January 29, 2019

The Defense Federal Acquisition Regulation Supplement (DFARS) mandate, specifically Clause 252.204-7012 requiring all members of the Department of Defense’s supply chain to comply ...