Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

10/23/2013
01:20 PM
50%
50%

NIST Releases Preliminary Cybersecurity Framework

Proposal offers private and public-sector organizations a common language for understanding and managing cybersecurity risk.

The National Institute of Standards and Technology (NIST) has published a preliminary cybersecurity framework for owners and operators of critical infrastructure.

The voluntary framework, developed in response to a presidential executive order, provides both private and public-sector organizations with a common language for understanding and managing cybersecurity risk internally and externally. It can be used as a tool to prioritize actions and to align policy, business and technology to manage risk.

The document lists five core functions -- identify, protect, detect, respond and recover -- all of which offer a high-level, strategic view of how an organization deals with cybersecurity risk. NIST said the framework was created to complement, and not replace, an organization's existing business or cybersecurity risk management process. The agency also said its approach focuses on outcomes, rather than any particular technology.

The framework is being watched closely as a vehicle for bringing closer cooperation between the public and private sectors on cybersecurity practices, in part because of the continued difficulty in Congress of crafting legislation that would allow the government and industry to share cyber intelligence. The preliminary framework released by NIST incorporates recommendations from a series of meetings with industry groups to address concerns over cybersecurity monitoring and reporting, as well as privacy protection practices. However, because the framework is voluntary, its adoption remains uncertain.

[ Learn more about why a cybersecurity framework is important. See Dept. Of Energy Breach: Bigger Than We Realized. ]

The final framework is due to be released in February 2014, following a 45-day public comment period on the preliminary framework. "We encourage organizations to begin reviewing and testing the preliminary framework to better inform the version we plan to release in February," NIST director Patrick Gallagher said in a written statement. "The framework will be a living document that allows for continuous improvement as technologies and threats evolve. Industry now has the opportunity to create a more secure world by taking ownership of the framework and including cyber risks in overall risk management strategies."

The cybersecurity framework was prompted by President Obama's executive order, issued in February of this year. The executive order -- and a related presidential policy directive -- called for a number of improvements in public-private information sharing, and created a process for building a framework of voluntary cybersecurity standards for critical infrastructure companies. The order instructed NIST to work with other agencies and private industry in creating a risk framework and best practices.

The need for industry-wide guidance on managing cybersecurity risk is growing, as cyber threats become more dangerous and sophisticated. Examples include emerging threats that want to damage systems, and new groups of attackers that are driven by a wide range of motives, according to industry experts.

Although the framework is voluntary, organizations are encouraged to adopt it when finalized because it's an opportunity to agree on basic security principles and practices, said Tom Conway, director of McAfee Federal, a participant in the development process. Conway added: "The framework will be a very important tool in raising the cyber resiliency of individual companies, each of the critical infrastructure industry segments, and thus the nation as a whole."

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
WKash
50%
50%
WKash,
User Rank: Apprentice
10/24/2013 | 2:46:13 PM
re: NIST Releases Preliminary Cybersecurity Framework
There's already the usual grumbling about NIST's approach.

Critics complain that instead of creating a sense of urgency around certain issues, the recommendations in the framework are given the same weight. The fact that it creates additional reporting obligations that takes away from actually protecting networks isn't encouraging, and somewhat typical of NIST's got-to-document mentality.

In NIST's defense, one of their policy advisers, Adam Sedgewick, has said the agency considered prioritizing certain recommendations, but the large range of companies covered by the guidelines make a single list of priorities impractical.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15564
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing Arm guest OS users to cause a hypervisor crash because of a missing alignment check in VCPUOP_register_vcpu_info. The hypercall VCPUOP_register_vcpu_info is used by a guest to register a shared region with the hypervisor. The region will be map...
CVE-2020-15565
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing x86 Intel HVM guest OS users to cause a host OS denial of service or possibly gain privileges because of insufficient cache write-back under VT-d. When page tables are shared between IOMMU and CPU, changes to them require flushing of both TLBs....
CVE-2020-15566
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a host OS crash because of incorrect error handling in event-channel port allocation. The allocation of an event-channel port may fail for multiple reasons: (1) port is already in use, (2) the memory allocation failed, o...
CVE-2020-15567
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes...
CVE-2020-15563
PUBLISHED: 2020-07-07
An issue was discovered in Xen through 4.13.x, allowing x86 HVM guest OS users to cause a hypervisor crash. An inverted conditional in x86 HVM guests' dirty video RAM tracking code allows such guests to make Xen de-reference a pointer guaranteed to point at unmapped space. A malicious or buggy HVM g...