Data Class Nist SP 1800 39a Preliminary Draft
Data Class Nist SP 1800 39a Preliminary Draft
Implementing Data
Classification Practices
Volume A:
Executive Summary
William Newhouse
Murugiah Souppaya
National Institute of Standards and Technology
Gaithersburg, Maryland
John Kent
Ken Sandlin
The MITRE Corporation
McLean, Virginia
Karen Scarfone
Scarfone Cybersecurity
Clifton, Virginia
April 2023
PRELIMINARY DRAFT
13 This 1800-series National Institute of Standards and Technology (NIST) publication documents how the
14 National Cybersecurity Center of Excellence (NCCoE) and its collaborators are using commercially
15 available technology to build interoperable data classification solutions for use cases. As the project
16 progresses, this preliminary draft will be updated with supporting guidance, and additional use cases
17 and volumes will also be released to solicit public comment.
18 CHALLENGE
19 Significant challenges that have hindered effective use of data classification for protecting data include:
20 ▪ The limited nature of actionable and interoperable standards for data classification across
21 different regulated industry sectors means that many organizations do not use classifications
22 that are consistent with those of their partners and suppliers to support various policies.
23 ▪ The lack of shared data classification schemes can result in data being classified and labeled
24 inconsistently.
25 ▪ Data being widely distributed across data centers, clouds, and endpoint devices complicates the
26 process of establishing and maintaining data inventories.
27 ▪ Data classifications and data handling requirements often change during the data lifecycle,
28 requiring the capability to adjust to those changing requirements.
29 ▪ Organizational culture may not connect its data owners and business process owners with its
30 data classification technology operators.
31 SOLUTION
32 The NCCoE is collaborating with technology providers to build several example data classification
33 solutions and demonstrate their ability to meet organizational data classification needs. The project’s
34 objective is to define product-agnostic recommended practices for defining data classification schemes
35 and communicating them to others. Organizations will also be able to use the recommended practices
36 to inventory and characterize data for other security management purposes, such as prioritization of
37 data in preparing the migration of systems, applications, and services to support post-quantum
38 cryptographic algorithms.
39 For the first example solution, the use case involves the creation, transmission, storage, and retrieval of
40 email. The solution focuses on the classification and exchange of email messages and attachments
41 within and among multiple organizations. Additional volumes of this publication will be released in the
42 future. Volumes will document how organizations can apply zero-trust-aligned approaches to solve the
43 challenge of exchanging data via email using data classification techniques. Future volumes will include
44 data classification guidance, example solution architectures, demonstrations of the technology, and
45 mapping relationships to support various government and industry-recommended practices.
46 Our solution strategy follows an agile implementation methodology to build iteratively and
47 incrementally while adapting or adding capabilities. Additional data classification use cases will be
48 examined to address an increasing number of requirements and resource types.
Collaborators
ActiveNav Janusnet Thales Trusted Cyber Technologies
Adobe JPMorgan Chase & Co. Trellix
GitLab Quick Heal Virtru
Google
50 While the NCCoE is using a suite of commercial products to address this challenge, this guide does not
51 endorse these particular products, nor does it guarantee compliance with any regulatory initiatives. Your
52 organization's information security experts should identify the products that will best integrate with
53 your existing tools and IT system infrastructure. Your organization can adopt this solution or one that
54 adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring and
55 implementing parts of a solution.
62 Future releases of this publication will include guidance to assist people in the following roles:
63 Technology, security, and privacy program managers who are concerned with how to identify,
64 understand, assess, and mitigate risk will be able to use NIST SP 1800-39b: Approach, Architecture, and
65 Security Characteristics, which will describe what we built and why, including the risk analysis performed
66 and the security/privacy control mappings once it is published.
67 IT professionals who want to implement an approach like this will be able to make use of NIST SP 1800-
68 39c: How-To Guides, which will provide specific product installation, configuration, and integration
69 instructions for building the example implementations, allowing you to replicate all or parts of this
70 project once it is published.
78
79 COLLABORATORS
80 Collaborators participating in this project submitted their capabilities in response to an open call in the
81 Federal Register for all sources of relevant security capabilities from academia and industry (vendors
82 and integrators). Those respondents with relevant capabilities or product components signed a
83 Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to
84 build this example solution.
85 Certain commercial entities, equipment, products, or materials may be identified by name or company
86 logo or other insignia in order to acknowledge their participation in this collaboration or to describe an
87 experimental procedure or concept adequately. Such identification is not intended to imply special
88 status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it
89 intended to imply that the entities, equipment, products, or materials are necessarily the best available
90 for the purpose.