United States: The NIST Cybersecurity Framework - Version 1.0

Keywords: NIST, cybersecurity, cyber risks

On February 12, 2013, President Obama issued Executive Order (EO) 13636, directing the National Institute of Standards and Technology (NIST) to establish a "framework to reduce cyber risks to critical infrastructure," which was defined as "systems and assets, whether physical or virtual, so vital to the United States that the incapacity or destruction of such systems and assets would have a debilitating impact on security, national economic security, national public health or safety, or any combination of those matters."1 President Obama required the framework to include "a set of standards, methodologies, procedures, and processes that align policy, business, and technological approaches to address cyber risks."2 This framework was intended to provide a "prioritized, flexible, repeatable, performance-based, and cost-effective approach" to manage cybersecurity risk.3

NIST subsequently hosted a series of workshops with stakeholders and solicited comments on a preliminary version. At the end of this process, NIST released Version 1.0 of the "Framework for Improving Critical Infrastructure Cybersecurity" (the Framework) on February 12, 2014.

NIST describes the Framework as providing a "common taxonomy and mechanism for organizations to: 1) Describe their current cybersecurity posture; 2) Describe their target state for cybersecurity; 3) Identify and prioritize opportunities for improvement within the context of a continuous and repeatable process; 4) Assess progress toward the target state; 5) Communicate among internal and external stakeholders about cybersecurity risk."4 The Framework, which focuses on risk-management, is technologically neutral and is not industry-specific.5 It is designed to complement, rather than replace, a company's existing risk-management practices.6 NIST anticipates that the Framework "will continue to be updated and improved as industry provides feedback on implementation."7

The Framework consists of three parts. First, the Framework 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 implementation/operations level."8 Second, the Framework Implementation Tiers "describe the degree to which an organization's cybersecurity risk management practices exhibit the characteristics defined in the Framework," i.e., they describe general categories of overall cybersecurity sophistication.9 Third, the Framework Profiles "can be characterized as the alignment of standards, guidelines, and practices to the Framework Core in a particular implementation scenario," i.e., they state an entity's performance (or goals) across the various elements of the Framework Core.10

The Framework Core

The Framework Core "presents cybersecurity outcomes identified by industry as helpful in managing cybersecurity risk" and "is not a checklist of actions to perform."11 It is presented in the form of a table that effectively explains how, through meeting broadly accepted cybersecurity standards, a critical infrastructure operator can improve its performance of key security functions. The Framework Core is broken into four elements:

  • Functions "organize basic security activities at their highest level."12 These functions are: Identify ("Develop the organizational understanding to manage cybersecurity risk to systems, assets, data, and capabilities."); Protect ("Develop and implement the appropriate safeguards to ensure delivery of critical infrastructure services."); Detect ("Develop and implement the appropriate activities to identify the occurrence of a cybersecurity event."); Respond ("Develop and implement the appropriate activities to take action regarding a detected cybersecurity event."); and Recover ("Develop and implement the appropriate activities to contain the impact of a potential cybersecurity event.").13
  • Categories subdivide functions into "groups of cybersecurity outcomes closely tied to programmatic needs and particular activities." Examples include: "Asset Management," "Access Control," and "Detection Processes."14
  • Subcategories divide categories into "specific outcomes of technical and/or management activities." Examples include: "Data-at-rest is protected," "External information systems are catalogued," and "Notifications from detection systems are investigated."15
  • Informative References are a nonexhaustive list of "specific sections of standards, guidelines, and practices common among critical infrastructure sectors that illustrate a method to achieve the outcomes associated with each subcategory."16

The Framework Implementation Tiers

The Framework Implementation Tiers provide entities with a means to categorize their overall cybersecurity performance. However, NIST is careful to explain that "Tiers do not represent maturity levels," and that while "[p]rogression to higher Tiers is encouraged" when such a change is cost-effective and enhances cybersecurity, "[s]uccesful implementation of the Framework is based upon achievement of the outcomes described in the organization's Target Profile(s) and not upon Tier determination."17

The four Tiers, each of which is described in terms of "Risk Management Process," "Integrated Risk Management Program," and "External Participation," are:

  • Tier 1: PartialRisk management practices are ad hoc; there is limited awareness of cybersecurity risk; and participation in external entities (e.g., an Information Sharing and Analysis Center) is limited.
  • Tier 2: Risk InformedRisk management practices are approved by management, if not established entity-wide; organizational awareness of cybersecurity risk is not matched by an organization-wide approach for managing that risk; and the entity has not formalized its external interaction capabilities.
  • Tier 3: RepeatableRisk management practices are formally approved, expressed as policy, and regularly updated; there is an organization-wide approach to managing cybersecurity risk, including through knowledgeable personnel; and the entity engages in information sharing with external partners.
  • Tier 4: AdaptiveRisk management practices are updated through a process of continuous improvement; cybersecurity risk management is part of the organizational culture and is based on past activities and continuous system awareness; and the entity actively shares information with partners to facilitate improved cybersecurity before a cybersecurity event occurs.18

The Framework Profile

NIST describes a Framework Profile as "the alignment of the Functions, Categories, and Subcategories with the business requirements, risk tolerance, and resources of the organization," and explains that a "Profile enables organizations to establish a roadmap for reducing cybersecurity risk that is well aligned with organizational and sector goals."19 An entity may generate a "Current Profile" and a "Target Profile."20 In other words, then, a Framework Profile is the assessment that a company generates when it uses the Framework Core to evaluate its cybersecurity posture—e.g., strong in certain categories, weak in others—and to determine which areas it should strengthen in order to manage its cybersecurity risk.

How to Use the Framework

NIST identifies four ways to use the Framework:

  • Basic review of cybersecurity practices, by comparing an organization's current cybersecurity activities with those outlined in the Framework Core.21
  • Establishing or improving a Cybersecurity Program.
  • Communicating cybersecurity requirements to stakeholders, including service providers and partners.22
  • Identifying opportunities for new or revised informative references, such as through collaboration with technology leaders and standards bodies.23

NIST also includes a subsection entitled "Methodology to protect privacy and civil liberties" in the "How to Use the Framework" section. It responds to the EO's requirement that the Framework include a methodology "to protect individual privacy and civil liberties,"24 and provides "a general set of considerations and processes" to "address individual privacy and civil liberties implications that may result from cybersecurity operations."25 The Framework does not identify specific "Informative References" (i.e. existing standards) that an entity might use to protect individual privacy.26 Instead, it describes general categories of activities for managing risk to individual privacy.27 Within those categories, it identifies steps the entity might take to protect individual privacy. For example, within the "Awareness and training measures" category, it identifies one steps as: "Applicable information from organization privacy policies is included in cybersecurity workforce training and awareness activities."28

Next Steps

Implementation: EO 13636 directs the Secretary of the Department of Homeland Security (DHS) to establish, in coordination with sector-specific agencies, "a voluntary program to support the adoption of the Cybersecurity Framework by owners and operators of critical infrastructure and any other interested entities," including through the establishment of incentives for participation in that program. To that end, DHS launched the "C Cubed" (or "C3") voluntary program29 to coincide with the release of the Framework. The stated purposes of that program are to: "1) support industry in increasing its cyber resilience; 2) increase awareness and use of the Framework; and 3) encourage organizations to manage cybersecurity as part of an all hazards approach to enterprise risk management."30 DHS further states that "The C³ Voluntary Program's focus during the first year will be engagement with Sector-Specific Agencies (SSAs) and organizations using the Framework to develop guidance on how to implement the Framework.31 Later phases of the C³ Voluntary Program will broaden the program's reach to all critical infrastructure and businesses of all sizes that are interested in using the Framework."32

Regulation: EO 13636 requires "agencies with responsibility for regulating the security of critical infrastructure" to evaluate "current cybersecurity regulatory requirements" and, "if they are deemed to be insufficient," to propose, within 90 days of publication of the Framework, "prioritized, risk-based, efficient, and coordinated actions ... to mitigate cyber risk."33 EO 13636 similarly recommends that independent regulatory agencies with relevant responsibilities engage in a consultative process "to consider prioritized actions to mitigate cyber risks for critical infrastructure."34

Regulatory agencies have not yet indicated what "prioritized actions" they might take in response to the Framework, but at least three categories of action are possible.

First, an agency could attempt to mandate or encourage, either by rule or through guidance, adoption of a portion of the Framework Core.35

Second, an agency could impose disclosure requirements based on the Framework. The SEC, for example, recently has pressed registrants for disclosure of cyber risk. It may find the Framework Tiers to provide an appealing template for relevant disclosure requirements.

Third, a regulator could attempt to use the Framework in the exercise of otherwise unrelated enforcement authority. The Consumer Financial Protection Bureau, for example, has authority to bring actions for "abusive acts or practices" against covered financial institutions, and conceivably could seek to prove that, by failing to pursue an appropriate target profile, a company took "unreasonable advantage" of "the reasonable reliance by the consumer on a covered person to act in the interests of the consumer."36

Litigation and Insurance: The three elements of the Framework also are likely to play a role in future litigation, as well as in the insurance markets. First, the Framework Core provides a vocabulary for identifying a cybersecurity failure (e.g., a failure of detection, identification, etc.), and it specifies particular industry standards that are intended to reduce the risk of such a failure. Though these risk-management tools should properly be expected to reduce, rather than eliminate, risk, and although the framework imposes no mandatory legal obligations, the plaintiffs may attempt to use the failure to meet identified "Informative References" as a basis for liability, whether for a data breach or another form of harm. Second, insurance companies may find the Framework Tiers, as well as the more granular elements of the Framework Core, to be useful as they look to build actuarial analyses of cyber risk. Third, information relating to a company's work toward a goal Framework Profile may prove to be fertile ground for civil discovery with respect to a company's awareness of cybersecurity risk, as well as its decisions how to prioritize and address those risks.

Originally published February 28, 2014

Footnotes

1 Executive Order (EO) 13636, Improving Critical Infrastructure Cybersecurity § 2, 7 (Feb. 12, 2013).

2 Id. § 7.

3 Id.

4 NIST, Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0 (Framework) at 4 (Feb. 12, 2014), available at http://www.nist.gov/cyberframework/upload/cybersecurity-framework-021214-final.pdf.

5 Framework 4-5. The Framework describes "risk management" as the "ongoing process of identifying, assessing, and responding to risk." It explains: "To manage risk, organizations should understand the likelihood that an event will occur and the resulting impact. With this information, organizations can determine the acceptable level of risk for delivery of services and can express this as their risk tolerance."

6 Framework 4.

7 Framework 2.

8 Framework 4.

9 Framework 5.

10 Framework 5.

11 Framework 7.

12 Framework 7.

13 Framework7.

14 Framework 8.

15 Framework 8.

16 Framework 8.

17 Framework 9.

18 Framework 10-11.

19 Framework 11.

20 Framework 11.

21 Framework 13.

22 Framework 15.

23 Framework 15.

24 EO 13636 § 7(b).

25 Framework 15.

26 Cf. Preliminary Framework App. B, available at http://www.nist.gov/itl/upload/preliminary-cybersecurity-framework.pdf.

27 Framework 16-17. The categories are governance of cybersecurity risk, approaches to identifying and authorizing individuals to access organizational assets and systems, awareness and training measures, anomalous activity detection and system and assets monitoring, and response activities, including information sharing or other mitigation efforts.

28 Framework 16.

29 The full name of the program is the Critical Infrastructure Cyber Community (C3) Voluntary Program.

30 http://www.dhs.gov/about-critical-infrastructure-cyber-community-c%C2%B3-voluntary-program

31 EO 13636 § 8(b) requires SSAs to "coordinate with the Sector Coordinating Councils to review the Cybersecurity Framework and, if necessary, develop implementation guidance or supplemental materials to address sector-specific risks and operating environments."

32 http://www.dhs.gov/about-critical-infrastructure-cyber-community-c%C2%B3-voluntary-program

33 EO 13636 § 10 (a)-(b).

34 EO 13696 § 10(e).

35 The Administration has repeatedly emphasized the voluntary nature of the Framework and the accompanying DHS program. However, the Administration does not control the actions of independent agencies. The Administration's posture also may change if an executive branch agency finds existing regulations insufficient as part of the assessment required by the Executive Order.

36 See 12 U.S.C. § 5531(d).

Learn more about our Privacy & Security and Government Relations practices.

Visit us at mayerbrown.com

Mayer Brown is a global legal services provider comprising legal practices that are separate entities (the "Mayer Brown Practices"). The Mayer Brown Practices are: Mayer Brown LLP and Mayer Brown Europe – Brussels LLP, both limited liability partnerships established in Illinois USA; Mayer Brown International LLP, a limited liability partnership incorporated in England and Wales (authorized and regulated by the Solicitors Regulation Authority and registered in England and Wales number OC 303359); Mayer Brown, a SELAS established in France; Mayer Brown JSM, a Hong Kong partnership and its associated entities in Asia; and Tauil & Chequer Advogados, a Brazilian law partnership with which Mayer Brown is associated. "Mayer Brown" and the Mayer Brown logo are the trademarks of the Mayer Brown Practices in their respective jurisdictions.

© Copyright 2014. The Mayer Brown Practices. All rights reserved.

This Mayer Brown article provides information and comments on legal issues and developments of interest. The foregoing is not a comprehensive treatment of the subject matter covered and is not intended to provide legal advice. Readers should seek specific legal advice before taking any action with respect to the matters discussed herein.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Emails

From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.