Dataset Viewer
Auto-converted to Parquet Duplicate
text
stringlengths
51
4.95k
embedding
listlengths
1.54k
1.54k
example_idx
int64
0
2.23k
According to Zero Trust Architecture: | | | 3.2.2.
[ 0.0068734917, 0.04320097, 0.040811356, 0.008028023, 0.031306606, -0.0069943145, -0.033212926, 0.013699996, -0.021050068, 0.028863294, -0.0016042622, -0.0029400287, 0.0007056404, 0.012981771, -0.0043630563, -0.009773246, 0.049188424, -0.016230568, -0.016807836, 0.036220077, 0....
0
According to IoT Device Cybersecurity Capability Core Baseline: | 1. The ability to use demonstrably secure cryptographic modules for standardized cryptographic algorithms (e.g., encryption with authentication, cryptographic hashes, digital signature validation) to prevent the confidentiality and integrity of the device's stored and transmitted data from being compromised 2. The ability for authorized entities to render all data on the device inaccessible by all entities, whether previously authorized or not (e.g., through a wipe of internal storage, destruction of cryptographic keys for encrypted data) 3. Configuration settings for use with the Device Configuration capability including, but not limited to, the ability for authorized entities to configure the cryptography use itself, such as choosing a key length | • This capability supports access management, data protection, and incident detection. • Authorized entities (e.g, customers, administrators, users) often want the confidentiality of their data protected so unauthorized entities cannot access their data and misuse it. • Authorized entities often want the integrity of their data protected so it is not inadvertently or intentionally changed, which could have a variety of adverse consequences (e.g., issuing the wrong command to a piece of equipment, concealing malicious activity). | • AGELIGHT : 5, 7, 18, 24, 25, 34 • BITAG : 7.2, 7.10 • CSDE : 5.1.3, 5.1.4, 5.1.5, 5.1.8, 5.1.10 • CTIA : 4.8, 5.14, 5.15 • ENISA : GP-OP-04, GP-TM- 02, GP-TM-04, GP-TM-14, GP-TM-24, GP-TM-32, GP- TM-34, GP-TM-35, GP-TM- 39, GP-TM-40 • ETSI : 4.4-1, 4.5-1, 4.5-2, 4.11-1, 4.11-2, 4.11-3 • GSMA: CLP13_6.4.1.1, 6.11, 6.12.1.1, 6.19, 7.6.1, 8.10.1.1, 8.11.1 • IEC : CR 3.1, CR 3.4, CR 4.1, CR 4.2, CR 4.3 • IIC : 7.3, 7.4, 7.6, 7.7, 8.8, 8.11, 8.13, 9.1, 10.4, 11.9 • IoTSF : 2.4.6.5, 2.4.7, 2.4.8.8, 2.4.8.16, 2.4.9, 2.4.12.2, 2.4.16.1, 2.4.16.2 • ISOC/OTA : 2, 17, 33 • OCF: 8.2, 11.2.1, 11.3, 14.2.2 • PSA: C1.1, C1.4, C2.4, D5.2, R2.2, R2.3, R6.1, R7.1 |
[ -0.0012311254, 0.041222844, 0.079109736, -0.00746618, 0.02986472, 0.010517517, -0.042308353, -0.004199726, 0.013661521, -0.0048417645, 0.032591727, -0.027058283, -0.03214164, -0.012099448, -0.01196045, -0.03420675, -0.016984235, 0.0292293, -0.014111609, 0.02859388, 0.03981962...
1
According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information: 3.2.3. 3.2.3.
[ 0.0021882725, 0.032307543, 0.053044476, 0.017318346, 0.02930219, -0.013286163, 0.02604639, -0.009116236, 0.012403341, 0.045981895, 0.019021379, 0.0016138118, -0.0015872018, 0.03501236, -0.018958766, -0.0024700242, 0.056300275, 0.0065929927, -0.02567072, -0.0030804866, -0.0395...
2
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171: ............................................ 5 | | 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 | | 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 | | 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 | | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | | 3.1 ACCESSCONTROL | .................................................................................................................. 12 | | 3.2 AWARENESSANDTRAINING | ...................................................................................................
[ 0.017715218, 0.028639602, 0.051454652, -0.015903434, 0.060768563, 0.0064553176, -0.010763337, 0.01538003, -0.0412013, 0.016789194, 0.024465788, -0.0016071191, 0.008179868, 0.030706376, 0.014802943, -0.017916527, 0.045388535, 0.004989115, -0.033095248, 0.032343693, 0.03808772,...
3
A111D3 DflTSbb NATL INST OF STANDARDS & TfCH R.I.C. A1 11 03089566 NBS Invitational Wor/Aud^ and evaluatio QC100 .U57 NO.500-19, 1977 C.2 NBS-PUB-O IMCE & TECHNOLOGY: UDIT AND EVALUATION OF COMPUTER SECURITY iO-19 NBS Special Publication 500-19 U.S. DEPARTMEMT OF COMMERCE National Bureau of Standards NATIONAL BUREAU OF STANDARDS The National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to pro- mote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute for Applied Technology, the Institute for Computer Sciences and Technology, the Office for Information Programs, and the Office of Experimental Technology Incentives Program. THE INSTITUTE FOR BASIC STANDARDS provides the central basis within the United States of a complete and consist- ent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essen- tial services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry, and commerce. The Institute consists of the Office of Measurement Services, and the following center and divisions: Applied Mathematics — Electricity — Mechanics — Heat — Optical Physics — Center for Radiation Research — Lab- oratory Astrophysics- — Cryogenics^ — Electromagnetics — Time and Frequency'.
[ 0.019853566, 0.01073995, 0.061678004, -0.012320258, -0.0054697036, 0.0013626312, -0.02686522, -0.036147606, -0.043788314, -0.015112645, 0.031514086, -0.013662752, -0.04716373, 0.019163141, 0.06269063, 0.040474273, 0.00026298495, 0.014629347, 0.006206157, 0.03458264, 0.0290132...
4
According to Ordered t-way Combinations for Testing State-based Systems: rd with combinatorial interaction testing. Computer. 2013 Dec 11;47(2):37-45. - [30] Garn B, Simos DE, Zauner S, Kuhn R, Kacker R. Browser fingerprinting using combinatorial sequence testing. In Proceedings of the 6th Annual Symposium on Hot Topics in the Science of Security 2019 Apr 1 (pp. 1-9). - [31] Ozcan M. An Industrial Study on Applications of Combinatorial Testing in Modern Web Development. In2019 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2019 Apr 22 (pp. 210-213). - [32] Ratliff, Z. B. (2018). Black-box Testing Mobile Applications Using Sequence Covering Arrays. undergraduate thesis, Texas A&M University. - [33] Ratliff ZB, Kuhn DR, Ragsdale DJ. Detecting Vulnerabilities in Android Applications using Event Sequences. In2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS) 2019 Jul 22 (pp. 159-166). IEEE. - [34] Elks DC, Deloglos C, Jayakumar A, Tantawy DA, Hite R, Gautham S. Realization Of An Automated T-Way Combinatorial Testing Approach For A Software Based Embedded Digital Device. Idaho National Lab.(INL), Idaho Falls, ID (United States); 2019 Jun 17. - [35] Becci G, Dhadyalla G, Mouzakitis A, Marco J, Moore AD. Robustness testing of real-time automotive systems using sequence covering arrays. SAE International Journal of
[ -0.00039313003, -0.013712871, 0.05502139, 0.0030176104, 0.0072564236, -0.030356629, 0.010003245, -0.011850979, -0.013698712, 0.058957558, 0.014611959, -0.023574527, 0.011022684, -0.010718268, 0.021351583, -0.033414945, 0.009875815, 0.004481284, -0.033273358, 0.041825317, 0.04...
5
According to Digital Identity Guidelines: • RPs and CSPs SHALL make human support personnel available to intervene and • RPs and CSPs SHALL educate support personnel on issue handling procedures for the digital identity management system, the avenues for redress, and the alternatives available to gain access to services. • RPs and CSPs SHALL implement a process for personnel and technologies that provides support functions to report and address major barriers that end users face and grievances they may have.
[ 0.0005419599, 0.034430392, 0.080422595, 0.08047927, 0.01589749, -0.001214982, 0.012008131, 0.05531533, 0.036640737, 0.055627044, 0.03547889, -0.02847946, 0.007296976, -0.028592812, 0.0040523014, 0.019524725, -0.00004358593, 0.041401483, -0.017356886, 0.025220618, 0.048372578,...
6
tegrity, and availability protection. The enhanced security requirements are implemented in addition to the basic and derived requirements since those requirements are not designed to address the APT. The enhanced security requirements apply to those components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. There is no expectation that all of the enhanced security requirements will be selected by federal agencies implementing this guidance. The decision to select a particular set of enhanced security requirements will be based on the mission and business needs of federal agencies and guided and informed by ongoing risk assessments. The enhanced security requirements for nonfederal systems processing, storing, or transmitting CUI associated with critical programs or high value assets will be conveyed to nonfederal organizations by federal agencies in a contract, grant, or other agreement. The application of the enhanced security requirements to subcontractors will also be addressed by federal agencies in consultation with nonfederal organizations. \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ ## THE APPLICABILITY OF ENHANCED SECURITY REQUIREMENTS The enhanced security requirements are only applicable to a nonfederal system or nonfederal organization as mandated by a federal agency in a contract, grant, or other agreement. The requirements apply to the components of nonfederal systems that process, store, or transmit CUI associated with a critical program or a high value asset or that provide protection for such components. The requirements also apply to services, including externally provided services, that process, store, or transmit CUI, or that provide security protections, for the system requiring enhanced protection.
[ -0.013136676, 0.019705012, 0.07176378, 0.04056105, 0.036807712, 0.011234986, 0.0022707682, 0.013336853, -0.035356425, 0.04081127, 0.0040035583, -0.022932881, -0.009314529, -0.00034425128, -0.0007299456, -0.008688972, 0.039860427, 0.0019830125, -0.033304602, 0.005695687, 0.036...
7
According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171: 3.4.3e Employ automated discovery and management tools to maintain an up-to-date, complete, accurate, and readily available inventory of system components. 3.4.3. 3.4.3e | Employ automated discovery and management tools to maintain an up-to-date, complete, accurate, and readily available inventory of system components.
[ -0.0119802905, 0.050263483, 0.02876923, -0.015404215, 0.022582743, -0.0025076629, -0.022486296, 0.0056904657, -0.052936487, 0.03596154, 0.02548998, 0.002531775, 0.00827391, 0.00053391175, 0.03813852, -0.03039508, -0.010492227, 0.02092934, -0.03739449, -0.00046071416, 0.024773...
8
"According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171(...TRUNCATED)
[-0.026579311,0.032411277,0.06373873,0.026992192,0.031611316,-0.016592715,0.0028159877,0.041262444,0(...TRUNCATED)
9
End of preview. Expand in Data Studio

CMMC Training Dataset - Balanced Variant

Dataset Description

This is the Balanced variant of the CMMC (Cybersecurity Maturity Model Certification) training dataset, containing 2,790 high-quality training examples with balanced coverage across all 17 CMMC domains.

Dataset Characteristics

  • Total Examples: 2,790 (2,232 train / 558 validation)
  • Source Documents: 71 NIST publications
  • CMMC Levels Covered: Level 1, Level 2, Level 3
  • CMMC Domains: All 17 domains (evenly distributed)
  • 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 "Balanced"?

The Balanced variant provides equal representation across all 17 CMMC domains, ensuring comprehensive coverage without bias toward any particular security area.

Domain Distribution (Perfectly Balanced)

Each of the 17 CMMC domains has approximately 840 examples:

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

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 exceeds the total number of examples (2,790).

This balanced distribution ensures your model learns all CMMC domains equally well.

CMMC Level Distribution

All Levels:         2,247 examples (80.5%)
Level 3 (Advanced): 301 examples (10.8%)
Level 2 (Advanced): 124 examples (4.4%)
Level 1 (Foundational): 118 examples (4.2%)

Source Documents (71 total)

The Balanced variant includes:

Core Foundation (14 documents):

  • NIST SP 800-171 R3 (CMMC Level 2)
  • NIST SP 800-172 R3 (CMMC Level 3)
  • NIST SP 800-53 R5 (Master controls)
  • Assessment procedures and supplementary guidance

Domain-Specific Publications (57 additional documents):

  • Selected from 596 NIST publications using domain keyword matching
  • Covers emerging topics: cloud security, IoT, supply chain, incident response
  • Includes practical implementation guides and case studies

Examples:

  • SP 800-61 (Incident Response)
  • SP 800-92 (Audit Log Management)
  • SP 800-115 (Security Testing)
  • SP 800-137 (Continuous Monitoring)
  • SP 800-161 (Supply Chain Risk Management)

Dataset Structure

JSONL Training Files

Each example follows the chat format:

{
  "messages": [
    {
      "role": "system",
      "content": "You are a cybersecurity expert specializing in CMMC..."
    },
    {
      "role": "user",
      "content": "How should incident response be implemented for CMMC Level 2?"
    },
    {
      "role": "assistant",
      "content": "According to NIST SP 800-61 R2, incident response for CMMC Level 2..."
    }
  ],
  "metadata": {
    "source": "NIST SP 800-61 R2",
    "cmmc_level": "2",
    "cmmc_domain": "Incident Response",
    "type": "domain_specific"
  }
}

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: 34.5 MB total (27.5 MB train + 7.0 MB validation)
  • Cost: $0.01 (674,102 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 (balanced sampling)
  5. Semantic chunking: General content with context preservation

Use Cases

The Balanced dataset is ideal for:

  • Comprehensive CMMC training: Equal coverage of all 17 domains
  • Domain-agnostic models: No bias toward specific security areas
  • Full compliance coverage: Suitable for general CMMC consulting
  • RAG systems: Balanced retrieval across all domains
  • Security assessment tools: Complete domain coverage
  • Training multiple specialists: Each domain well-represented

Dataset Statistics

Source Documents:         71
Total Examples:           2,790
Training Examples:        2,232 (80%)
Validation Examples:      558 (20%)
Avg Example Length:       ~242 tokens
Total Tokens Embedded:    674,102
Embedding Cost:           $0.01 USD
Domain Balance:           99.8% (within 2% variance)

Advantages Over Other Variants

vs. Core (14 docs, 1.2K examples):

  • 2.2x more examples
  • 5x more source documents
  • Better domain balance (Core is weighted toward SP 800-171/172)
  • More diverse use cases and scenarios

vs. Comprehensive (381 docs, 11.3K examples):

  • Faster training (75% fewer examples)
  • Better signal-to-noise ratio (curated selection)
  • Equal domain representation (Comprehensive may be imbalanced)
  • Lower computational cost

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: Check domain distribution
from collections import Counter
domains = [ex['metadata'].get('cmmc_domain', 'Unknown')
           for ex in train_data if 'metadata' in ex]
print(Counter(domains))

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}")  # (2232, 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: 14 docs, 1.2K examples - Essential CMMC foundation
  • Balanced (this dataset): 71 docs, 2.8K examples - Domain-balanced coverage
  • Comprehensive: 381 docs, 11.3K examples - Complete NIST CMMC library

When to Use Balanced vs. Others

Choose Balanced if:

  • You need equal representation across all 17 CMMC domains
  • You want comprehensive coverage without excessive examples
  • You're building a general-purpose CMMC assistant
  • You want faster training than Comprehensive
  • You need more diversity than Core

Choose Core if:

  • You only care about SP 800-171/172 fundamentals
  • You want the fastest training possible
  • You're focused on core CMMC requirements only

Choose Comprehensive if:

  • You need maximum context and coverage
  • You're building an exhaustive knowledge base
  • Training time/cost is not a constraint
  • You want every NIST CMMC-related publication

Citation

If you use this dataset, please cite:

@dataset{cmmc_balanced_2025,
  title={CMMC Training Dataset - Balanced 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
  • Balancing: Domain-based keyword matching with weighted sampling

Contact

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

Downloads last month
67

Collection including ethanolivertroy/cmmc-training-balanced