Dataset Viewer
Auto-converted to Parquet Duplicate
text
stringlengths
51
3.17k
embedding
listlengths
1.54k
1.54k
example_idx
int64
0
994
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer: NIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information. | Access Control | Maintenance | Security Assessment and Monitoring | |-----------------------------------|---------------------|--------------------------------------| | Awareness and Training | Media Protection | System and Communications Protection | | Audit and Accountability | Personnel Security | System and Information Integrity | | Configuration Management | Physical Protection | Planning | | Identification and Authentication | Risk Assessment | System and Services Acquisition | | Incident Response | | Supply Chain Risk Management | - An understanding of the need for security (why is cybersecurity important to our business mission?). - Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.). - How to respond to confirmed or suspected incidents. - How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI). - How to recognize and report insider threats, social engineering, and social mining.
[ -0.027711315, 0.021571606, 0.060914047, 0.027075734, 0.038516186, -0.007379091, 0.0059903474, 0.040473774, -0.0056534894, 0.02641473, 0.046397384, 0.0041503413, -0.016575942, -0.013016691, 0.029973982, -0.02405037, -0.011662904, 0.021724146, -0.035058625, 0.011770953, 0.04627...
0
According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations: | Table 1. Security Requirement Families .......................................................................................................4 | |----------------------------------------------------------------------------------------------------------------------------------------------------------| | Table 2. Security Control Tailoring Criteria.................................................................................................93 | | Table 3. Access Control (AC) .......................................................................................................................93 | | Table 4. Awareness and Training (AT).........................................................................................................94 | | Table 5. Audit and Accountability (AU).......................................................................................................95 | | Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 | | Table 7. Configuration Management (CM).................................................................................................96 | | Table 8. Contingency Planning (CP) ............................................................................................................96 | | Table 9. Identification and Authentication (IA) ..........................................................................................97 | | Table 10. Incident Response (IR).................................................................................................................98 | | Table 11. Maintenance (MA) ......................................................................................................................98 | | Table 12.
[ -0.00629847, 0.05169411, 0.06691708, -0.010437464, 0.0360979, 0.017622385, -0.007844761, -0.0008131358, -0.022927763, 0.024287434, 0.03500483, -0.019875173, 0.026007015, 0.025327181, 0.014823066, -0.056892846, 0.046921935, 0.024727326, -0.020368386, 0.034258343, 0.02940619, ...
1
## Summary of NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations Kelley Dempsey Computer Security Division Information Technology Laboratory Greg Witte Doug Rike G2, Inc. Annapolis Junction, MD February 19, 2014 <!-- image --> ## Abstract This white paper provides an overview of NIST Special Publication (SP) 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations , which was published April 30, 2013. ## Keywords assurance; computer security; FIPS Publication 199; FIPS Publication 200, FISMA; Privacy Act; Risk Management Framework; security controls; security requirements ## Disclaimer Any mention of commercial products or reference to commercial organizations is for information only; it does not imply recommendation or endorsement by NIST, nor does it imply that the products mentioned are necessarily the best available for the purpose. ## Additional Information For additional information on NIST's Computer Security Division programs, projects and publications, visit the Computer Security Resource Center, csrc.nist.gov. Information on other efforts at NIST and in the Information Technology Laboratory (ITL) is available at www.nist.gov and www.nist.gov/itl.
[ 0.0025568528, -0.0031894115, 0.030262616, 0.017924586, -0.011273325, -0.02269696, -0.0050949166, 0.0127012795, -0.0067076283, -0.009876685, 0.018550882, -0.015807707, -0.024826366, -0.015181411, 0.021281533, -0.0037922212, 0.019001815, 0.013214842, 0.00548322, 0.051030584, -0...
2
According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations: The NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate.
[ -0.018804658, 0.044273976, 0.04562037, 0.0071751666, 0.0104962755, -0.010081137, 0.026546434, 0.03287449, -0.017671442, 0.054394383, -0.009918448, 0.014484973, -0.015775269, 0.01864758, 0.037115637, -0.032133974, 0.00605878, 0.008869381, -0.0018470865, 0.03689124, 0.032986693...
3
team oversees incident response, allocates funding, and may have decision-making authority on high-impact response actions, such as shutting down or rebuilding critical services. - Incident handlers. Incident handlers verify that an incident has occurred, collect and analyze data and evidence, prioritize incident response activities, and act appropriately to limit damage, find root causes, and restore operations. Incident handlers also often provide input to others on mitigating cybersecurity issues and improving resiliency. An organization's incident handlers might be: - o On staff (e.g., an incident response team), - o On contract (e.g., outsourcing a security operations center [SOC] to a managed security services provider [MSSP] or leveraging a cloud service provider's incident response team when an incident occurs within that provider's cloud), and/or - o Available when needed (e.g., from a parent organization, a cybersecurity services provider, a business partner, or a law enforcement agency). Many organizations may use more than one of these approaches, such as internally performing basic incident response and engaging third-party resources for assistance with certain incidents. Larger organizations may have multiple incident response teams, with each team responsible for a particular logical or physical segment of the organization. When this model is employed, the teams should be part of a single coordinated entity (e.g., a federation) to ensure that incident response processes, procedures, and training are consistent across the organization and that information is shared among teams. - Technology professionals. Cybersecurity, privacy, system, network, cloud, and other technology architects, engineers, and administrators, as well as software developers, may be involved in incident response and recovery efforts. - Legal.
[ -0.015856141, 0.0027793464, 0.06019305, 0.0034334876, 0.019449396, -0.020679303, -0.015217073, 0.049775023, -0.008120997, 0.041310374, 0.06048244, -0.015530578, 0.0104300855, -0.011485152, 0.0034063575, 0.009652351, -0.02442931, -0.0064871516, -0.054067634, 0.017073989, 0.001...
4
According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer: | Access Control | Maintenance | Security Assessment and Monitoring | |-----------------------------------|---------------------|--------------------------------------| | Awareness and Training | Media Protection | System and Communications Protection | | Audit and Accountability | Personnel Security | System and Information Integrity | | Configuration Management | Physical Protection | Planning | | Identification and Authentication | Risk Assessment | System and Services Acquisition | | Incident Response | | Supply Chain Risk Management | ## Family: Access Control ## Getting Started with Access Control
[ 0.0024122677, 0.039233364, 0.06147799, 0.006042283, 0.029624108, 0.0016134322, -0.019112328, 0.02795178, -0.010989589, -0.0002886758, 0.033924382, -0.0013703805, -0.004452907, 0.021050107, 0.01056487, -0.03846356, -0.016856011, 0.01868761, -0.008998721, 0.05038222, 0.04448925...
5
itado que los titulares de registros de patentes cuyo uso pueda ser necesario para el cumplimiento de las orientaciones o requisitos de esta publicación comuniquen dichos registros de patentes al ITL. Sin embargo, los titulares de patentes no están obligados a responder a las solicitudes de patentes del ITL y el ITL no ha realizado una búsqueda de patentes para identificar cuáles, si las hubiera, pueden aplicarse a esta publicación. Tras la convocatoria del ITL para la identificación de reclamaciones de patentes cuyo uso pueda ser necesario para el cumplimiento de las orientaciones o requisitos de esta publicación, se ha recibido notificaciones de una o más de dichas reclamaciones. Mediante la publicación, el ITL no adopta posición alguna con respecto a la validez o el alcance de cualquier reivindicación de patente o de cualquier derecho relacionado con ella. No obstante, el o los titulares conocidos de patentes han facilitado a NIST una carta de garantía en la que declaran o bien (1) una renuncia general en el sentido de que no poseen y no tienen actualmente la intención de poseer ninguna reivindicación esencial de patente, o bien (2) que negociarán licencias libres de cánones o que devenguen cánones con otras partes sobre una base no discriminatoria demostrable con términos y condiciones razonables. Para más detalles se puede consultar en zerotrust-arch@nist.gov . No se declara ni se da a entender que esta sea la única licencia necesaria para evitar la infracción de patentes en el uso de esta publicación.
[ 0.032497592, 0.046622686, 0.025064632, -0.021595094, -0.00792067, -0.013779374, -0.05748814, 0.010396266, -0.05030212, -0.034917627, 0.05146275, 0.010050547, -0.005701278, -0.010599993, -0.0040097237, 0.03575723, 0.014384382, -0.052302353, -0.04190609, 0.040424436, 0.02943550...
6
According to Assessing Enhanced Security Requirements for Controlled Unclassified Information: | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 | |-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----| | 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 | | 1.2 | TARGET AUDIENCE.............................................................................................................................. | | | 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 | | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 | | 2.1 | ASSESSMENT PROCEDURES................................................................................................................
[ 0.03428543, 0.038844522, 0.05217921, -0.014217516, 0.035945676, 0.011424084, -0.009348775, -0.00733276, -0.028461387, 0.021438276, 0.03344213, -0.0151267, -0.0030009632, 0.028197855, 0.03136023, -0.028224207, 0.016655182, 0.024179002, -0.013222686, 0.018526254, 0.023889117, ...
7
parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance. Parameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems.
[ 0.010864979, 0.0039596953, 0.061008636, 0.0008292269, -0.0076073576, 0.0021140217, -0.0013596825, 0.0131802615, -0.0013050769, 0.038841832, 0.010852498, -0.01965806, -0.004689852, 0.02040694, -0.009292334, -0.022678537, 0.043260217, 0.0070956238, -0.0022981209, 0.013417407, 0...
8
"...103 |\n| Appendix D. Organization-Defined Parameters....................(...TRUNCATED)
[0.02891047,0.033823695,0.06413056,-0.0065940693,-0.0015046761,-0.010990116,-0.0020105448,0.00248732(...TRUNCATED)
9
End of preview. Expand in Data Studio

CMMC Training Dataset - Core Variant

Dataset Description

This is the Core variant of the CMMC (Cybersecurity Maturity Model Certification) training dataset, containing 1,244 high-quality training examples derived from the most essential NIST cybersecurity publications for CMMC compliance.

Dataset Characteristics

  • Total Examples: 1,244 (995 train / 249 validation)
  • Source Documents: 14 foundational NIST publications
  • CMMC Levels Covered: Level 1, Level 2, Level 3
  • CMMC Domains: All 17 domains
  • Format: JSONL with chat-formatted messages
  • Embeddings: 1536-dimensional vectors (OpenAI text-embedding-3-small)
  • License: Public Domain (NIST documents are US Government works)

What Makes This "Core"?

The Core variant focuses on the essential foundation documents that form the basis of CMMC:

Foundation Documents (14 total)

Primary CMMC Requirements:

  • NIST SP 800-171 Rev 3: Protecting Controlled Unclassified Information (CMMC Level 2)
  • NIST SP 800-171A Rev 3: Assessment Procedures for SP 800-171
  • NIST SP 800-171B: Protecting CUI in Nonfederal Systems and Organizations
  • NIST SP 800-172 Rev 3: Enhanced Security for CUI (CMMC Level 3)
  • NIST SP 800-172A: Assessment Procedures for SP 800-172

Master Control Catalog:

  • NIST SP 800-53 Rev 5: Security and Privacy Controls

Supplementary Guidance:

  • NIST SP 800-37 Rev 2: Risk Management Framework

This core set provides comprehensive coverage of CMMC requirements across all 17 domains and 3 maturity levels.

CMMC Level Distribution

Level 3 (Advanced): 579 examples (46.5%)
All Levels:         561 examples (45.1%)
Level 2 (Advanced): 104 examples (8.4%)

CMMC Domain Coverage

All 17 CMMC domains are represented (567 examples each):

  • Access Control (AC)
  • Awareness and Training (AT)
  • Audit and Accountability (AU)
  • Configuration Management (CM)
  • Identification and Authentication (IA)
  • Incident Response (IR)
  • Maintenance (MA)
  • Media Protection (MP)
  • Personnel Security (PS)
  • Physical Protection (PE)
  • Risk Assessment (RA)
  • Security Assessment (CA)
  • System and Communications Protection (SC)
  • System and Information Integrity (SI)
  • System and Services Acquisition (SA)
  • Planning (PL)
  • Supply Chain Risk Management (SR)

Note: Domain counts represent the number of examples tagged with each domain. Since examples can be tagged with multiple domains, the sum of domain counts (9,639) exceeds the total number of examples (1,244).

Dataset Structure

JSONL Training Files

Each example follows the chat format:

{
  "messages": [
    {
      "role": "system",
      "content": "You are a cybersecurity expert specializing in CMMC (Cybersecurity Maturity Model Certification) and NIST frameworks..."
    },
    {
      "role": "user",
      "content": "What is the purpose of CMMC Level 2 requirement 3.1.1?"
    },
    {
      "role": "assistant",
      "content": "According to NIST SP 800-171 R3, control 3.1.1 (Access Control) requires..."
    }
  ],
  "metadata": {
    "source": "NIST SP 800-171 R3",
    "cmmc_level": "2",
    "cmmc_domain": "Access Control",
    "cmmc_practice_id": "AC.L2-3.1.1",
    "nist_control": "3.1.1",
    "type": "cmmc_requirement"
  }
}

Vector Embeddings

Pre-computed embeddings using OpenAI's text-embedding-3-small model:

  • Format: Parquet files with 1536-dimensional vectors
  • Files: embeddings_train.parquet, embeddings_valid.parquet
  • Size: 15.3 MB total (12.1 MB train + 3.2 MB validation)
  • Cost: $0.01 (330,784 tokens processed)

FAISS Indexes

Ready-to-use vector similarity search indexes:

  • L2 distance indexes: faiss_train_l2.index, faiss_valid_l2.index
  • Cosine similarity indexes: faiss_train_cosine.index, faiss_valid_cosine.index

Q&A Generation Strategies

Examples were generated using 5 complementary strategies:

  1. Section-based Q&A: Questions from document sections
  2. Control-based Q&A: NIST control requirements (3.1.1 format)
  3. CMMC-specific Q&A: Level-focused questions (L1/L2/L3)
  4. Domain-specific Q&A: Questions per CMMC domain
  5. Semantic chunking: General content with context preservation

Use Cases

This Core dataset is ideal for:

  • Fine-tuning LLMs on CMMC compliance requirements
  • Building CMMC chatbots for compliance guidance
  • RAG systems for CMMC documentation
  • Semantic search across CMMC controls
  • Training materials for CMMC assessors
  • Compliance automation tools

Dataset Statistics

Source Documents:         14
Total Examples:           1,244
Training Examples:        995 (80%)
Validation Examples:      249 (20%)
Avg Example Length:       ~266 tokens
Total Tokens Embedded:    330,784
Embedding Cost:           $0.01 USD

Quick Start

Load JSONL Data

import json

# Load training data
with open('train.jsonl', 'r') as f:
    train_data = [json.loads(line) for line in f]

# Example: Access first training example
print(train_data[0]['messages'])
print(train_data[0]['metadata'])

Load Embeddings

import pandas as pd
import numpy as np

# Load embeddings
df = pd.read_parquet('embeddings_train.parquet')

# Access embeddings as numpy array
embeddings = np.vstack(df['embedding'].values)
texts = df['text'].tolist()

print(f"Embeddings shape: {embeddings.shape}")  # (995, 1536)

Use FAISS Index

import faiss

# Load FAISS index
index = faiss.read_index('faiss_train_cosine.index')

# Search for similar content
query_embedding = ... # your query vector (1536-dim)
k = 5  # number of results
distances, indices = index.search(query_embedding.reshape(1, -1), k)

# Get similar texts
for i, idx in enumerate(indices[0]):
    print(f"{i+1}. {texts[idx][:100]}...")

Related Datasets

This is part of a family of 3 CMMC datasets:

  • Core (this dataset): 14 docs, 1.2K examples - Essential CMMC foundation
  • Balanced: 71 docs, 2.8K examples - Domain-balanced coverage
  • Comprehensive: 381 docs, 11.3K examples - Complete NIST CMMC library

Citation

If you use this dataset, please cite:

@dataset{cmmc_core_2025,
  title={CMMC Training Dataset - Core Variant},
  author={Troy, Ethan Oliver},
  year={2025},
  publisher={HuggingFace},
  note={Derived from NIST Special Publications (Public Domain)}
}

License

Public Domain - This dataset is derived from NIST Special Publications, which are works of the US Government and not subject to copyright protection in the United States.

Acknowledgments

This dataset is built from publications by the National Institute of Standards and Technology (NIST), Computer Security Resource Center.

Dataset Version

  • Version: 1.0
  • Created: 2025
  • Source: NIST CSRC Publications
  • Processing: Docling + custom CMMC-aware data preparation

Contact

For questions or issues, please open an issue on the GitHub repository.

Downloads last month
42

Collection including ethanolivertroy/cmmc-training-core