"Privacy & Cybersecurity Update: NIST Cybersecurity Framework: Preliminary Draft Issued"

by Skadden, Arps, Slate, Meagher & Flom LLP

On October 22, the National Institute of Standards and Technology (NIST) issued its Preliminary Cybersecurity Framework (the Preliminary Framework).1 The Preliminary Framework represents the first full draft of the Cybersecurity Framework (the Framework) that President Obama ordered NIST to develop in his February 12, 2013, executive order addressing the regulation of critical infrastructure network security.2

As its name suggests, this document provides a framework that companies can use to guide their evaluation of their cybersecurity practices, to develop a plan to reduce their risks and to respond to security breaches. While the Preliminary Framework does not propose new cybersecurity standards, the executive order mandates that agencies use the Framework (once it is finalized) as the basis for reviewing critical infrastructure cybersecurity within regulated sectors. The executive order also asks those agencies to consider whether they have the legislative authority to enact any regulations that might be required. As a result, companies in regulated critical infrastructure industries should understand the basic contours of the Preliminary Framework.

Preliminary Framework Basics

The Preliminary Framework — which hews closely to the discussion draft of the Framework released in late August (the Discussion Draft) — remains open-ended, with little specific guidance on steps companies should take to improve their security posture. Instead, the Preliminary Framework lists various existing standards companies might adopt. For example, when advising that companies use separate testing environments for system development, the Preliminary Framework lists sections of the COBIT, ISO 27000 series and NIST SP 800 series standards that offer more specific suggestions on implementing such environments.3

The Preliminary Framework, like the Discussion Draft on which it is based, is composed of three parts — a Framework Core, the Framework Implementation Tiers and the Framework Profile. The Framework Core lists the five security functions that a cybersecurity-conscious organization should consider, then breaks each one into categories and subcategories that should be addressed. The Framework Implementation Tiers provide companies with different tiers they might fall into depending, in part, on how proactive they are in assessing risk. Finally, the Framework Profile is a tool organizations can use to apply the Framework Implementation Tiers to the functions under the Framework Core and develop a comprehensive cybersecurity strategy.

For more information on the basic composition of the Preliminary Framework, please refer to our recent mailing on the Discussion Draft, available here.4

Notable Changes From the Discussion Draft

Although the Preliminary Framework closely tracks the Discussion Draft, there are a few important changes to note. Unlike the Discussion Draft, the Preliminary Framework is the first version to identify specific critical infrastructure industries. The draft indicates that “critical infrastructure” includes all 16 sectors designated as such by the presidential directive that accompanied the original executive order, including:

  • chemical
  • commercial facilities
  • communications
  • critical manufacturing
  • dams
  • defense industrial base
  • emergency services
  • energy
  • financial services
  • food and agriculture
  • government facilities
  • healthcare and public health
  • information technology
  • nuclear services
  • transportation systems
  • water systems

Specific identification of these sectors likely lays to rest the possibility that the Framework will adopt a narrower definition of critical infrastructure.

In addition, the Preliminary Framework clarifies that critical infrastructure operators should employ the Framework not only to address information technology security, but also industrial control system (ICS) security. Companies in critical infrastructure sectors that use ICSs, including energy, nuclear services and transportation, should be aware of the potential for new regulation of those systems.

While the Preliminary Framework offers more specificity regarding covered entities and systems, it is more general than the Discussion Draft in defining the functions in the Framework Core. For example, where the Discussion Draft suggested that operators prepare to detect anomalies by “[i]dentify[ing] and determin[ing] normal organizational behaviors and expected data flow of personnel, operational technology, and information systems,” the Preliminary Framework merely recommends that “[a] baseline of normal operations and procedures is identified and managed.” Relaxed guidelines such as this one may broaden the applicability of the Framework, but also increase the vagueness of the list of categories and subcategories to implement.

The Preliminary Framework also adds new language explicitly recommending that critical infrastructure operators consider the associated appendix addressing protections for privacy and civil liberties. That appendix offers a set of privacy and civil liberties issues corresponding to the categories and subcategories of the Framework Core. The Preliminary Framework suggests that potential privacy issues should be considered when preparing to address each corresponding category when designing a cybersecurity strategy.

Going Forward

The Framework is not yet complete, although NIST appears increasingly unlikely to make major modifications. While the release of the Preliminary Framework was delayed by the government shutdown, NIST has indicated that it intends to continue to adhere to the schedule laid out in the executive order and will release the first official edition of the Framework in February 2014.

The official release of the Preliminary Framework commences the next step of the process set forth in the executive order. Ninety days after the release, the executive order requires applicable agencies to report on their ability to mitigate risks to critical infrastructure industries by adopting regulations based on the Preliminary Framework. Some critical infrastructure regulators are already considering how best to implement appropriate aspects of the executive order under their existing authorities.5

In addition to the creation of the Framework itself, NIST and the Department of Homeland Security continue to revise and develop incentives to encourage companies voluntarily to adopt the Framework. One much-discussed incentive is liability protection for those who adopt the Framework. Such protection could prove important since creative class action plaintiffs may try to assert in a data breach case that the Framework is a de facto standard, and that the entity suffering the breach failed to adhere to it.

Skadden continues to follow the cybersecurity regulatory process within NIST and other agencies as it unfolds and can assist clients in understanding the applicability of the Framework and subsequent sector-specific regulations to their companies and the implications within various industries.


1 National Institute of Standards and Technology, Improving Critical Infrastructure Cybersecurity Executive Order 13636: Preliminary Cybersecurity Framework, Oct. 22, 2013, at http://www.nist.gov/itl/upload/preliminary-cybersecurity-framework.pdf.

2 The White House – Office of the Press Secretary, Executive Order: Improving Critical Infrastructure Cybersecurity, Feb. 12, 2013. The Executive Order, which touched on a variety of cybersecurity topics, directed NIST to develop a Framework — in effect, a voluntary standard — that includes a set of “standards, methodologies, procedures, and processes” to help owners and operators of critical infrastructure identify, assess and manage cyber risk. This includes identifying cross-sector security standards and guidelines applicable to critical infrastructure as well as areas for improvement that should be addressed through future collaboration.

3 COBIT is the Control Objectives for Information and Related Technology, and ISO 27001 is a product of the International Organization for Standardization. Both are commonly applied private sector cybersecurity standards. The NIST standards are required for certain government information technology systems but also widely referenced in the private sector.

4 Stuart D. Levi, Ivan A. Schlager and Joshua F. Gruenspecht, “NIST Cybersecurity Framework: Discussion Draft Update,” Privacy & Cybersecurity Update, Sept. 18, 2013.

5 Remarks by Thomas J. Curry, Comptroller of the Currency, Before the Exchequer Club, Washington, D.C., Sept. 18, 2013.

Download PDF

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Skadden, Arps, Slate, Meagher & Flom LLP | Attorney Advertising

Written by:

Skadden, Arps, Slate, Meagher & Flom LLP

Skadden, Arps, Slate, Meagher & Flom LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
Privacy Policy (Updated: October 8, 2015):

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.


JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at info@jdsupra.com. In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at: info@jdsupra.com.

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.