Request Demo

NIST Cybersecurity Framework

Breaking Down the NIST Cybersecurity Framework: Detect

down-arrow

In the past two blog posts, we've been diving into the framework functions. So far, we've covered Identify and Protect. Now, we move onto the third function of the framwork core: Detect.

[Webinar with Cybersecurity Influencers: The Benefits of Frameworks and Standards HERE]

NIST defines the framework core as "a set of cybersecurity activities , desired outcomes, and applicable references that are common across critical infrastructure sectors . The Core presents industry standards , guidelines, and practices in a manner that allows for communication of cybersecurity activities and outcomes across the organization from the executive level to the implem entation/operations level".

The detect function requires that you develop and implement the appropriate activities to identify the occurrence of a cybersecurity event.

"The detect function enables timely discovery of cybersecurity events. Examples of outcome Categories within this Function include : Anomalies and Events; Security Continuous Monitoring; and Detection Processes".

  • Anomalies & Events: Your program will detect unusual activity as soon as possinle, and the impact of events is understood by everyone on your team and beyond.
  • Security & Continuous Monitoring: You're monitoring your information system and environments at specified intervals to identify cyber events in your organization.
  • Detection Processes: Procedures and processes for detection are put in place and tested in order to ensure timely and broad awareness of cyber events.

The detect function is a critical step to a robust cyber program - the faster you can detect a cybersecurity event, the faster you can mitigate the effects of it. Examples of how to accomplish steps towards a thorough detect function is as follows:

  • Anomalies & Events: Prepare your team to have the knowledge to collect and analyze data from multiple points to detect an event.
  • Security & Continuous Monitoring: Make your team able to monitor your assets 27/7 or consider involving a MSS to supplement.
  • Detection Processes: Attempt to know about a breach as soon as possible and follow disclosure requirements as needed. Your program should be able to detect inappropriate access to your data as soon as possible.

Clearly, the detect function is one of the most important, as detecting a breach or event can be life or death for your business. There is no doubt that following these best practices and implementing these solutions will help you scale your program and mitigate cybersecurity risk. In our next blog post, we will explore the respond function.

Learn How CyberStrong Streamlines the NIST Cybersecurity Framework Adoption

    

You may also like

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 ...

Digital Risk Management Frameworks
on January 24, 2019

As organizations continue to embrace digitization, security teams are faced with the challenge of keeping the enterprise secure while empowering growth and innovation. Many CISO’s ...

The Cybersecurity Impact Of The ...
on January 23, 2019

There has been a great deal of speculation around the cybersecurity posture of the nation in light of the most recent (and longest documented) government shutdown. I’ve seen two ...

George Wrenn