{"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| | | 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| 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 |"}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.2.3. 3.2.3."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Audit and Evaluation of Computer Security provide?"}, {"role": "assistant", "content": "A111D3 DflTSbb\n\nNATL INST OF STANDARDS & TfCH R.I.C. A1 11 03089566\nNBS Invitational Wor/Aud^ and evaluatio\nQC100 .U57 NO.500-19, 1977 C.2 NBS-PUB-O\n\nIMCE & TECHNOLOGY:\n\nUDIT AND EVALUATION\nOF COMPUTER SECURITY\n\niO-19\n\nNBS Special Publication 500-19\nU.S. DEPARTMEMT OF COMMERCE\nNational Bureau of Standards\n\n\fNATIONAL BUREAU OF STANDARDS\n\nThe National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to\nstrengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this\nend, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and\ntechnological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to pro-\nmote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute\nfor Applied Technology, the Institute for Computer Sciences and Technology, the Office for Information Programs, and the\nOffice of Experimental Technology Incentives Program. THE INSTITUTE FOR BASIC STANDARDS provides the central basis within the United States of a complete and consist-\nent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essen-\ntial services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry,\nand commerce. The Institute consists of the Office of Measurement Services, and the following center and divisions:\n\nApplied Mathematics — Electricity — Mechanics — Heat — Optical Physics — Center for Radiation Research — Lab-\noratory Astrophysics- — Cryogenics^ — Electromagnetics — Time and Frequency'."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\nrd 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.\nIn 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"}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n• RPs and CSPs SHALL make human support personnel available to intervene and\n\n• RPs and CSPs SHALL educate support personnel on issue handling procedures\nfor the digital identity management system, the avenues for redress, and the\nalternatives available to gain access to services.\n\n• RPs and CSPs SHALL implement a process for personnel and technologies that\nprovides support functions to report and address major barriers that end users\nface and grievances they may have."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 7)"}, {"role": "assistant", "content": "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.\nThe 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. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## THE APPLICABILITY OF ENHANCED SECURITY REQUIREMENTS\n\nThe 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n3.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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.9.\n\n4.3.9. Notification of Proofing . . . . . . . . . . . . . . . . . . . . . .\n\n• Visual and tactile inspection by trained personnel for on-site identity proofing"}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide?"}, {"role": "assistant", "content": "## Assessing Enhanced Security Requirements for Controlled Unclassified Information\n\nRON ROSS VICTORIA PILLITTERI KELLEY DEMPSEY\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\n\n\n## NIST Special Publication 800-172A\n\n## Assessing Enhanced Security Requirements for Controlled Unclassified Information\n\nRON ROSS VICTORIA PILLITTERI KELLEY DEMPSEY\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172A\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by the National Institute of Standards and Technology (NIST) to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 7)"}, {"role": "assistant", "content": "ving inputs from a variety of software producers will be particularly helpful to us in refining and revising the SSDF. The publication will be updated periodically to reflect your inputs and feedback.\nIf you are from a standards-developing organization or another organization that has produced a set of secure practices and you would like to map your secure software development standard or guidance to the SSDF, please contact us at ssdf@nist.gov. We would like to introduce you to the National Online Informative References Program (OLIR) so that you can submit your mapping there to augment the existing set of informative references. ## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Executive Summary\n\nThis document describes a set of fundamental, sound practices for secure software development called the Secure Software Development Framework (SSDF). Organizations should integrate the SSDF throughout their existing software development practices, express their secure software development requirements to third-party suppliers using SSDF conventions, and acquire software that meets the practices described in the SSDF."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.1 (NIST 3.6.1)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.6.1 | Potential Deficiencies | Potential Deficiencies | 88 |\n| 4. 3.6.1 Potential Deficiencies - The objective of the review is to determine whether the Initiation Phase contains deficiencies."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.6.1", "cmmc_practice_id": "IR.L2-3.6.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.5. 3.2.5) option. 3.2.5) with a non-exportable authentication\nkey (see Sec."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n| | 5.4 Specific Details ........................................................................................................... | 5.4 Specific Details ........................................................................................................... | 5.4 Specific Details ..........................................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 5)"}, {"role": "assistant", "content": ". . . . 2.2. 2.3. Evaluation Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.\nCost and Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5. Algorithm and Implementation Characteristics . . . . . . . . . . . . . . . . . 2.6. Selection of the Candidates to Advance to the Second Round . . . . . . . . . 3. Summary of the Second-Round Candidates . . . . . . . . . . . . . . . . . . . . . . . 3.1. CROSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2. LESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3. HAWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4. Mirath (MIRA/MiRitH)\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5. MQOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6. PERK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7. RYDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8. SDitH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9. UOV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10. MAYO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11. QR-UOV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12. SNOVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13. FAEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.14. SQIsign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 6)"}, {"role": "assistant", "content": "|\n| Federal Vulnerability Disclosure Coordination Body ....................................................\n| 6 | |\n| Preparation................................................................................................................. | 7 | |\n| 2.1.1. Create Source Vulnerability | Report Receipt Capability............................................. 7 | |\n| 2.1.2. Determine Scope and Obtain Contacts .................................................................... | 8 | |\n| 2.1.3. Develop Technical Analysis Capability ....................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-03-30 Supersedes NIST Special Publication (SP) 800-140Cr1 (May 2022) https://doi.org/10.6028/NIST.SP.800-140Cr1\n\n## How to Cite this NIST Technical Series Publication:\n\nCalis A (2023) Cryptographic Module Validation Program (CMVP)-Approved Security Functions: CMVP Validation Authority Updates to ISO/IEC 24759. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-140Cr2. https://doi.org/10.6028/NIST.SP.800-140Cr2\n\n## Author ORCID iDs\n\nAlexander Calis: 0000-0003-1937-8129\n\n## Contact Information\n\nsp800-140-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe approved security functions listed in this publication replace the ones listed in International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 19790 Annex C and ISO/IEC 24759 6.15, within the context of the Cryptographic Module Validation Program (CMVP). As a validation authority, the CMVP may supersede Annex C in its entirety. This document also supersedes SP 800-140Cr1. ## Keywords\n\nCryptographic Module Validation Program; CMVP; FIPS 140 testing; FIPS 140; ISO/IEC 19790; ISO/IEC 24759; testing requirement; vendor evidence; vendor documentation; security policy."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.7 (NIST 3.3.7)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.3.7 Encryption\n\nEnciphering may be indicated for very sensitive data\n\nthat must be passed outside the control of its owner."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.3.7", "cmmc_practice_id": "AU.L2-3.3.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\nIn addition to functionalities like revocation, accountability, attribute privacy protection, policy updating, decentralization (multi-authorities), and key hierarchy for practical access control system deployments [ZDXSLZ], the applicable access policy structure for fundamental ABE is restricted to supporting non-monotone and stated policy rules [TKN]. For example, CP-ABE allows data owners to define their own access policies by attributes and, thus, support complex access control policy structure. However, by only associating attributes, decryption keys are organized logically as a static set. Users can only use all possible combinations of attributes in the set of keys issued to compose their policies, and it has restrictions for specifying policies, attribute managements (e.g., applying environment conditions and dynamic attributes), and the application of deny rules. This may fail to satisfy the enterprise requirements of access control in terms of flexibility and dynamic properties [BS]. However, research has introduced methods to handle the non-monotone restriction [AG, AN, AT, TKN] to address the deny rule issue. The policy issue can be addressed by combining various technologies, such as refreshing user secret keys more frequently, shortening the expiration time interval, or allowing dynamic attributes to be updated closer to real-time. In KP-ABE, the secret key and ciphertext relate to a set of attributes to offer fine-grained access control [BCSES] for which permission evaluation depends only on the resources' attributes. The resource provider (i.e., data owner or encrypted) cannot specify the access policy except by choosing descriptive attributes for permissions. This means that there is no choice but to trust the key issuer. Such accountability for user secret keys provides fine-grained access without flexibility or scalability [BS]."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\ninstallations require administrator privileges, such as installing firmware patches for a system basic input/output system (BIOS). 3 Some patch installations require user participation or cooperation.\n- Change software configuration and state. In some cases, making a patch take effect necessitates implementing changes. Examples include restarting patched software, rebooting the operating system or platform on which the patched software runs, redeploying the applications, or altering software configuration settings. In other cases, no such changes are needed. - Resolve any issues. Installing a patch may cause side effects to occur, like inadvertently altering existing security configuration settings or adding new settings, and these side effects can inadvertently create a new security problem while fixing the original one. Patch installation can also cause operational issues that may necessitate uninstalling the patch, reverting to the previous version of the software, or restoring the software or asset from backups."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 4)"}, {"role": "assistant", "content": "oners in these fields, but since the report contains initial findings from a small group exercise, it is not intended as a specific recommendation or guideline for practice. ## Table of Contents\n\n| 1.\nIntroduction.....................................................................................................................................1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Background......................................................................................................................................2 |\n| 3. Report from the Design-A-Thon .......................................................................................................4 |\n| 4. Designs ............................................................................................................................................6 |\n| 5. Discussion......................................................................................................................................14 |\n| References.........................................................................................................................................16 |\n| Appendix A."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\nAdditional information about this publication is available at https://csrc.nist.gov/publications/cswp, including related content, potential updates, and document history."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nource code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications.\n| CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.4.3 SP800161 : SA-1, SA-8, SA-15, SR-3 SP800181 : T0414; K0003, K0039, K0044, K0157, K0168, K0177, K0211, K0260, K0261, K0262, K0524; S0010, S0357, S0368; A0033, A0123, A0151 |\n| Define Security Requirements for Software Development (PO."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n..........................................6 |\n| 3. | Threat Environment.............................................................................................................\n7 |\n| 3.1 | Identifier Collisions .......................................................................................................7 |\n| 3.2 | Revoked PIV Cards .......................................................................................................8 |\n| 3.3 | Visual Counterfeiting ....................................................................................................8 |\n| 3.4 | Skimming.......................................................................................................................9 |\n| 3.5 | Sniffing ..........................................................................................................................9 |\n| 3.6 | Social Engineering.......................................................................................................10 |\n| 3.7 | Electronic Cloning.......................................................................................................10 |\n| 3.8 | Electronic Counterfeiting ............................................................................................10 |\n| 3.9 | Other Threats ...............................................................................................................11 |\n| 4. | PIV Authentication Mechanisms in PACS Applications ................................................"}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nPresident's Council on Integrity and Efficiency | ^ | 3.2.2 | Size of Review Task | Size of Review Task | 49 | |-----------|------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------|-----------| | 3.3 | BACKGROUND ON THE METHODOLOGY | BACKGROUND ON THE METHODOLOGY | BACKGROUND ON THE METHODOLOGY | 49 | | | 3.3.1 | The Invitational Workshop | The Invitational Workshop | 49 | | | 3.3.2 | Workshop Points of Agreement | Workshop Points of Agreement | 49 | | 3.4 | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | 50 | | | 3.4.1 | Assumptions and Caveats | Assumptions and Caveats | 50 | | | 3.4.2 | Audit Planning/Prioritization Process | Audit Planning/Prioritization Process | 51 | | | 3.4.3 | Non-Discretionary Audits | Non-Discretionary Audits | 51 | | | 3.4.4 | Risk Evaluation Levels and Dimensions | Risk Evaluation Levels and Dimensions | 53 | | | 3.4.5 | Two Level Work Priority Dimensions/Characteristics | Two Level Work Priority Dimensions/Characteristics | 54 | | | 3.4.5.1 Level I: | 3.4.5.1 Level I: | 3.4.5.1 Level I: | .....55 | | | 3.4.5.1.1 Mission Impact/Strategic"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nAlthough the integration of IT and OT networks is helping manufacturers boost productivity and gain efficiencies, it has also provided malicious actors, including nation states, common criminals, and insider threats a fertile landscape where they can exploit cybersecurity vulnerabilities to compromise the integrity of ICS and ICS data to reach their end goal. The motivations behind these attacks can range from degrading manufacturing capabilities to financial gain, and causing reputational harm.\n\nThe NCCoE, in conjunction with the NIST EL, collaborated with cybersecurity technology providers to develop and implement example solutions that demonstrate how manufacturing organizations can protect the integrity of their data from destructive malware, insider threats, and unauthorized software within manufacturing environments that rely on ICS.\n\nAn organization that is interested in protecting the integrity of a manufacturing system and information from destructive malware, insider threats, and unauthorized software should first conduct a risk assessment and determine the appropriate security capabilities required to mitigate those risks. Once the security capabilities are identified, the sample architecture and solution presented in this document may be used."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.2.1, 3. 3.2.1, 3. 3.2.1, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n6. Threats and Security Considerations . . . . . . . . . . . . . . . . . . . . . . .\n\n6.1. Authenticator Threats . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\nThreat Mitigation Strategies . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 10)"}, {"role": "assistant", "content": "1. Scope the Target Profile. Decide which of your supplier criticality levels it will apply to, and determine any other restrictions to be placed on the Profile's scope, such as suppliers of a particular type of product or service only. You can create as many Target Profiles as you need to specify the requirements for all of your suppliers. 2. Select the CSF Categories to include. Identify which CSF Categories and Subcategories correspond to your requirements, and only include those Categories and Subcategories in the Target Profile. 3. Determine what types of information to include in your Target Profile. Target Profiles are flexible and can contain whatever types of information you want to communicate to your suppliers. The notional Profile excerpt below captures each selected Category's and Subcategory's relative priority, the internal practices that the supplier must follow, and references to additional sources of information on achieving the Category and Subcategory. 4. Fill in the columns, and share the Target Profile. Once the contents of the Target Profile have been internally reviewed and finalized, it can be shared with your suppliers as your set of C-SCRM requirements for them."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nrs. ' Zombie devices ' are those that no longer receive software support and security updates. Higginbotham noted that unsupportive owners can neglect cybersecurity issues, leading to vulnerabilities.\nHerd immunity in cybersecurity requires collective action from manufacturers and consumers. Most consumers are unaware or indifferent to the end of life status of their products, resulting in ' zombie hordes ' . Communicating end of life status and dates is crucial, including proactive notification to consumers, retailers, and third parties. Companies should track devices to address critical vulnerabilities and create structured options for off-ramping zombie devices. Higginbotham emphasized that company priorities often overlook device security. Manufacturers should implement vulnerability disclosure programs, track issues, conduct comprehensive security audits, and allocate budgets for security maintenance. Buyers must keep products updated or segmented, and legislation should clarify responsibility to ensure herd immunity. Companies should have a dedicated point of contact for security researchers and consider recalls for insecure devices. Stacey also addressed secure repairs, both before and after end of life. Good hardware should not end up in landfills, but unpatched zombie devices pose risks. Consumer Reports advocates for designing products for longevity, including features like hardware upgrades, crypto agility, and increased memory."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nSome of the threats to wireless IMDs include device reprogramming, data extraction, data tampering, repeated access attempts and data flooding. Vulnerabilities include unsecured communication channels, inadequate authentication and access control, weak audit mechanisms and meager storage. The resulting risks include patient safety compromise resulting from firmware malfunction or therapy misconfiguration, device unavailability due to battery power depletion, patient privacy loss due to data leakage to unauthorized parties, and inappropriate medical follow-up due to tampering of patient readings. While some cyber threats may be unintentional, various motivations exist for deliberate cyber attacks, such as patient information gathering, negative impact to patient health status, ego satisfaction of the attacker, as well as gaining competitive advantage over another vendor through negative press. ## C. Authentication and Access Control Mechanisms\n\nFor each type of data identified, the authentication and access control mechanisms applicable for extracting or updating the data type need to be reviewed to determine adequacy of the protection mechanisms while balancing the needs of patient safety in emergency situations and the utility of the IMD within a patient's environment. This is a non-trivial exercise since the security and privacy requirements for IMDs frequently conflict with the requirements stemming from emergency access to patient data and device utility in hospital and home settings. Creative approaches may be devised to decouple data essential for patient safety in emergency conditions from patient personally identifiable information/data to allow different authentication and access control mechanisms to apply to each group of data."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nSeptember 2020\nINCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XVII\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 7)"}, {"role": "assistant", "content": "ation Processing Guidelines. latter effort will be carried out by a working group convened for this\npurpose and will result in a FIPS publication by NBS. These Proceedings are the result of phase one.\nTask Group 15\n\nThis\n\nThe General Chairman and organizer of the Workshop was Robert G. General Accounting Office. McKenzie of the U.S. project on computer security auditing, he initiated and planned the\nWorkshop and co-edited these Proceedings. Mr. McKenzie is an audit\nmanager at GAG and has conducted a number of reviews of computer securi-\nty of proposed and on-going systems in the Federal Government. As leader of the TG-15\n\nThe General Vice-Chairman of the Workshop was Zella G. Ruthberg of\n\nthe National Bureau of Standards. rity audit project, Mrs. Ruthberg worked closely with Mr. McKenzie on\nthe planning, acted as the Workshop arrangements chairman, and is co-\neditor of these Proceedings. in computer science at NBS and most recently has become active in the\nmanagerial procedures required for computer security. She has conducted a wide range of projects\n\nAs NBS coordinator of the TG-15 secu-\n\nMr. S. Jeffery, Chief of the Systems and Software Division of the\n\nInstitute for Computer Sciences and Technology of NBS, headed the NBS\nMr. Jeffery has been active in the formulation\nstaff at the Workshop. of policy concerning the effective utilization of computers within the\nFederal Government and is manager of the computer program at NBS. program provided the needed technical and administrative support for\nthis Workshop. This\n\nI would like to thank all of the particitpants in this Workshop,\nthe Chairmen and Recorders of the sessions, and the three individuals\nnamed above for the success of the Workshop. from the Workshop and subsequent efforts in this area will have far-\nreaching, beneficial effects on the use of computers throughout the\ncountry\n\nThe products to be derived\n\nDennis K."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 6)"}, {"role": "assistant", "content": "IoT Product Capabilities..............................................................................................5 | 2.2.1. IoT Product Capabilities..............................................................................................5 | |\n| 2.2.2. IoT Product | 2.2.2."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines provide? (Part 5)"}, {"role": "assistant", "content": "blication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations.\ni\n\n\fNIST SP 800-63-4\nJuly 2025\n\nPatent Disclosure Notice\n\nDigital Identity Guidelines\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for\ncompliance with the guidance or requirements of this publication disclose such patent\nclaims to ITL. However, holders of patents are not obligated to respond to ITL calls for\npatents and ITL has not undertaken a patent search in order to identify which, if any,\npatents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims\nwhose use may be required for compliance with the guidance or requirements of this\npublication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid\npatent infringement in the use of this publication. ii\n\n\fNIST SP 800-63-4\nJuly 2025\n\nTable of Contents\n\nDigital Identity Guidelines\n\n1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1. Scope and Applicability\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. How to Use This Suite of SPs . . . . . . . . . . . . . . . . . . . . . . . . 1.3. Enterprise Risk Management Requirements and Considerations . . . . . 1.3.1. Security, Fraud, and Threat Prevention . . . . . . . . . . . . . . 1.3.2. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.3. Customer Experience . . . . . . . . . . . . . . . . . . . . . . . 1.4. Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5. Document Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. Digital Identity Model\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.1.1 | ZTA basada en una gobernanza de la identidad mejorada... 3.1.1 ZTA basada en una gobernanza de la identidad mejorada\n\nPara desarrollar una ZTA, el enfoque de la gobernanza de la identidad mejorada utiliza la identidad de los actores como el componente clave de la creación de las políticas."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n.............................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1.\nBaseline Security ........................................................................................................................11 |\n| 3.2.2. Controls for Interacting With SCM Systems...............................................................................12 |\n| 4. CI/CD Pipelines -Background, Security Goals, and Entities to be Trusted .....................................13 |\n| 5. Integrating SSC Security Into CI/CD Pipelines.................................................................................15 |\n| 5.1.1. Secure Build................................................................................................................................16 |\n| 5.1.2. Secure Pull-Push Operations on Repositories............................................................................17 |\n| 5.1.3. Integrity of Evidence Generation During Software Updates......................................................18 |\n| 5.1.4. Secure Code Commits ................................................................................................................19 |"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n## Family: Incident Response"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Media Protection?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| 1. The ability for the manufacturer and/or supporting entity to receive maintenance and vulnerability information (e.g., bug reporting capabilities and bug bounty programs) from their customers and others in the IoT device ecosystem 2. The ability for the manufacturer and/or supporting entity to respond to customer and third-party queries about cybersecurity of the IoT device (e.g., customer support). | • This capability provides input from customers and others in the IoT device ecosystem for the manufacturer to use in the Information Dissemination and Education and Awareness non- technical supporting capabilities. • Customers and others in the IoT device ecosystem may want, or be required, to report vulnerabilities they identify in an IoT device. • Manufacturers can use reports of common queries and vulnerabilities to identify ways to improve the cybersecurity of the IoT device. • Some customers may need additional support to securely provision and use an IoT device. • Supports the customers' responsibilities related to cybersecurity, such as enabling them to obtain specialized cybersecurity information that may be used proactively for cybersecurity (e.g., threat intelligence and mitigation, digital forensics investigations, and secure reprovisioning and disposal). | • CTA : VUL-002, VUL-003 • AGELIGHT : 9 • ETSI : Provision 5.2-1 • IoTSF : 2.4.3.11, 2.4.3.12 • CSDE : 5.2.1, 5.2.2 |"}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\naft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nCommission (2016) ISO/IEC 27035-1:2016 - Information technology - Security Techniques - Information security incident management - Part 1: Principles of incident management (ISO, Geneva, Switzerland).\nAvailable at https://www.iso.org/standard/60803.html |\n| [ISOIEC_27036] | International Organization for Standardization/International Electrotechnical Commission (2013) ISO/IEC 27036-3:2013 - Information technology - Security Techniques - Information security for supplier relationships - Part 3: Guidelines for information and communication technology supply chain security (ISO, Geneva, |\n| [ISOIEC_29147] | Switzerland). Available at https://www.iso.org/standard/59688.html International Organization for Standardization/International Electrotechnical Commission (2018) ISO/IEC 29147:2018 - Information technology - Security techniques - Vulnerability disclosure (ISO, Geneva, Switzerland). Available at https://www.iso.org/standard/72311.html |\n| [ISOIEC_30111] | International Organization for Standardization/International Electrotechnical Commission (2019) ISO/IEC 30111:2019 - Information technology - Security techniques - Vulnerability handling processes (ISO, Geneva, Switzerland). Available at https://www.iso.org/standard/69725.html |\n| [NIST_TBF] | National Institute of Standards and Technology (2021) The Bugs Framework (BF) . Available at https://samate.nist.gov/BF/Home/Approach.html |\n| [NIST_VULN] | National Institute of Standards and Technology (2021) Vulnerability Data Ontology ."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Maintenance?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nts related to the IoT product (e.g., price of maintenance) and length and terms of support. - b. All IoT components, including but not limited to the IoT device, that are part of the IoT product. - c.\nHow the baseline product criteria are met by the IoT product across its product components, including which baseline product criteria are not met by IoT product components and why (e.g., the capability is not needed based on risk assessment). - d. Product design and support considerations related to the IoT product, for example :\n- i. All hardware and software components, from all sources (e.g., open source, propriety third-party, internally developed) used to"}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 6)"}, {"role": "assistant", "content": ".....................................11 | |\n| 4.\n| Attribute-Based Encryption............................................................................................13 | |\n| 4.1. | Ciphertext-Policy Attribute-Based Encryption | ............................................................13 |\n| 4.2. | Key-Policy Attribute-Based Encryption ......................................................................18 | |\n| 5. | ABE System Considerations ..........................................................................................22 | |\n| 5.1. | Security .....................................................................................................................22 | |\n| 5.1.1. | Key Management....................................................................................................22 | |\n| 5.1.2."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nCMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B\n\nCMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B\n\nHawes D, Calis A, Crombie R (2023) Cryptographic Module Validation Program (CMVP) Security Policy Requirements: CMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-140Br1. https://doi.org/10.6028/NIST.SP.800-140Br1"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The National Institute of Standards and Technology (NIST) initiated the Post-Quantum Cryptography (PQC) Standardization Process in December 2016 to select quantum-resistant public-key cryptographic algorithms for standardization in response to the substantial development and advancement of quantum computing. After three rounds of evaluation and analysis, NIST announced the selection of the first algorithms to be standardized [2]. The key encapsulation mechanism (KEM) selected for standardization was CRYSTALS-Kyber (ML-KEM [3]). The digital signatures selected were CRYSTALS-Dilithium (ML-DSA [4]), Falcon (FN-DSA), and SPHINCS + (SLH-DSA [5])."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nIn order for the plans to adequately reflect the protection of the resources, a senior management official must authorize a system to operate. The authorization of a system to process information, granted by a management official, provides an important quality control. By authorizing processing in a system, the manager accepts its associated risk.\n\nManagement authorization should be based on an assessment of management, operational, and technical controls. Since the system security plan establishes and documents the security controls, it should form the basis for the authorization, supplemented by the assessment report and the plan of actions and milestones. In addition, a periodic review of controls should also contribute to future authorizations. Re-authorization should occur whenever there is a significant change in processing, but at least every three years.\n\n- Approves system security plans,\n- Authorizes operation of an information system,\n- Issues an interim authorization to operate the information system under specific terms and conditions, or\n- Denies authorization to operate the information system (or if the system is already operational, halts operations) if unacceptable security risks exist."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.2.1. 3.2.1."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide?"}, {"role": "assistant", "content": "## Summary of NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations\n\nKelley Dempsey Computer Security Division Information Technology Laboratory\n\nGreg Witte Doug Rike G2, Inc. Annapolis Junction, MD\n\nFebruary 19, 2014\n\n\n\n## Abstract\n\nThis 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\n\nassurance; computer security; FIPS Publication 199; FIPS Publication 200, FISMA; Privacy Act; Risk Management Framework; security controls; security requirements\n\n## Disclaimer\n\nAny 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\n\nFor 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nlow the audit logs through certain types of attacks on the IMD. Creative techniques for selective overwriting of audit records based on significance of each type of audit record may be useful.\nAlert mechanisms when audit log storage space nears depletion may also be useful for alerting the patient or the remote monitoring facility so that appropriate steps can be taken in a timely manner prior to audit space exhaustion."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 5)"}, {"role": "assistant", "content": "osure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Software Supply Chain (SSC) -Definition and Model .....................................................................4 |\n| 2.4.1. Software Supply Chain Defects ....................................................................................................6 |\n| 2.4.2. Software Supply Chain Attacks.....................................................................................................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - Prioritize the patch. A patch may be a higher priority to deploy than others because its deployment would reduce cybersecurity risk more than other patches would. Another patch may be a lower priority because it addresses a low-risk vulnerability on a small number of low-importance assets. - Schedule patch deployment. Many organizations schedule patch deployments as part of their enterprise change management activities. - Acquire the patch."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "Murugiah Souppaya, Gary Stoneburner, Keith\nStouffer, Marianne Swanson, Pat Toth, Glenda Turner, Patrick Viscuso, Joe Weiss, Richard\nWilsher, Mark Wilson, John Woodward, and Carol Woody.\niv\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\nI\n\n. NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nPatent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent\nclaims whose use may be required for compliance with the guidance or requirements of this\npublication disclose such patent claims to ITL. However, holders of patents are not obligated to\nrespond to ITL calls for patents and ITL has not undertaken a patent search in order to identify\nwhich, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose\nuse may be required for compliance with the guidance or requirements of this publication, no\nsuch patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent\ninfringement in the use of this publication. v\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\npublic. Sometimes, the media learns of incidents through alternate sources (i.e., not through public affairs personnel). Having a media engagement strategy in place can greatly aid in this situation.\n| CSF Element | CSF Element Description regarding cybersecurity- | Priority | Recommendations, Considerations, Notes notifications, data breach reporting, and |\n|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| GV.OC-04 | understood and managed Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated | Medium | N1: Understanding critical external dependencies on the organization's operations can aid in prioritizing response and recovery efforts. |\n| GV.OC-05 | Outcomes, capabilities, and services that the organization depends on are understood and communicated | Medium | N1: Understanding critical dependencies on external resources (e.g., cloud-based hosting providers and managed service providers) can aid in prioritizing response and recovery efforts."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MP.L2-3.8.1 (NIST 3.8.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.8.1 of [SP800-63C] describes the association of an\nRP subscriber account with multiple CSP/IdP accounts."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.8.1", "cmmc_practice_id": "MP.L2-3.8.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nother than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- applications, supply chain applications) and allocate routing priorities and WAN resources accordingly.\n- Integration of security and networking functions: Use of appliances that contain a combination of networking and security functions (e.g., the presence of a firewall and secure web gateway [SWG] functions in a WAN router) [36]\n- Centralized visibility and management capabilities: Includes the ability to recognize and authenticate newly connected appliances and bring them under the defined management workflows as nodes so as to configure a uniform set of policies that cover all components\n- Integration with remote LAN locations: An additional preferred but non-essential feature is the integration of WAN and LAN functions in a single appliance (the latter going by the name SD-Branch), which can be managed using a single management console, thus providing better visibility into both components. This feature enables the connectivity of SD-WAN into the local LAN at the remote branch offices."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 10)"}, {"role": "assistant", "content": "Profile..........................................................................................................17 Table 2. Highlighted Insights and Key Takeaways from the Consumer Profiling Process.\n........20 |\n| List of Figures | List of Figures | List of Figures |\n\n## Acknowledgments\n\nThe authors wish to thank all contributors to this publication, including the participants in workshops and other interactive sessions; the individuals and organizations from the private and public sectors, including manufacturers from various sectors as well as several manufacturer trade organizations, who provided feedback during NIST's Executive Order 14028 response period. Special thanks to Cybersecurity for IoT team members Rebecca Herold, Brad Hoehn, and David Lemire. ## Introduction\n\nOn May 12, 2021, the President issued Executive Order (EO) 14028, which, among other directives, called for NIST to recommend requirements for a consumer IoT product cybersecurity labeling program. As part of NIST's response to this directive 1 , a profile of the IoT core baseline 2 for consumer IoT products was created."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "ft publications during the designated public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThis publication provides security and privacy control baselines for the Federal Government. There are three security control baselines (one for each system impact level-low-impact, moderate-impact, and high-impact), as well as a privacy baseline that is applied to systems irrespective of impact level."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nPersonnel within the following Workforce Categories and Specialty Areas from the National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework [SP800181] are most likely to find this publication of interest: - Securely Provision (SP): Risk Management (RSK), Software Development (DEV), Systems Requirements Planning (SRP), Test and Evaluation (TST), Systems Development (SYS) - Operate and Maintain (OM): Systems Analysis (ANA) - Oversee and Govern (OV): Training, Education, and Awareness (TEA); Cybersecurity Management (MGT); Executive Cyber Leadership (EXL); Program/Project Management (PMA) and Acquisition - Protect and Defend (PR): Incident Response (CIR), Vulnerability Assessment and Management (VAM) - Analyze (AN): Threat Analysis (TWA), Exploitation Analysis (EXP) | Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.2.5. 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.2.3 Other Considerations\n\nUSB attacks do not always come in the form of disguised file-based malware."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 6)"}, {"role": "assistant", "content": "th authentication and authorization support. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities.\n|\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n| | Offers secure data storage on-prem. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n\n\n\n\n\n\n\n| Collaborator | Component |\n|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Real-time data management software that enables detection of behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n| | Access control platform that secures connections and provides control mechanisms to enterprise systems for authorized users and devices; monitors activity down to the keystroke |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n| | Provides host-based application allowlisting (the blocking of unauthorized activities that have the potential to pose a harmful attack) and file integrity monitoring. |\n\nWhile the NCCoE used a suite of commercial products to address this challenge, this guide does not endorse these particular products, nor does it guarantee compliance with any regulatory initiatives."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Maintenance?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| 1. The ability to update the device's software through remote (e.g., network download) and/or local means (e.g., removable media) 2. The ability to verify and authenticate any update before installing it 3. The ability for authorized entities to roll back updated software to a previous version 4. The ability to restrict updating actions to authorized entities only 5. The ability to enable or disable updating 6. Configuration settings for use with the Device Configuration capability including, but not limited to: a. The ability to configure any remote update mechanisms to be either automatically or manually initiated for update downloads and installations b. The ability to enable or disable notification when an update is available and specify who or what is to be notified | • This capability supports vulnerability management. • Updates can remove vulnerabilities from an IoT device, which lowers the likelihood of an attacker compromising the device. • Updates can correct IoT device operational problems, which can improve device availability, reliability, performance, and other aspects of device operation. • Some authorized entities will need automatic update capabilities to meet their cybersecurity goals and needs, while others would prefer or need more direct control over updates and their application. • Some organizations may want a rollback capability in the event that an update inadvertently impacts critical applications or integration with other systems, while other organizations may prefer to eliminate the risk of someone intentionally or inadvertently rolling software back to a vulnerable version."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n.............................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1.\nBaseline Security ........................................................................................................................11 |\n| 3.2.2. Controls for Interacting With SCM Systems...............................................................................12 |\n| 4. CI/CD Pipelines -Background, Security Goals, and Entities to be Trusted .....................................13 |\n| 5. Integrating SSC Security Into CI/CD Pipelines.................................................................................15 |\n| 5.1.1. Secure Build................................................................................................................................16 |\n| 5.1.2. Secure Pull-Push Operations on Repositories............................................................................17 |\n| 5.1.3. Integrity of Evidence Generation During Software Updates......................................................18 |\n| 5.1.4. Secure Code Commits ................................................................................................................19 |"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 2)"}, {"role": "assistant", "content": "ly the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities.\nThe information in this publication, including\nconcepts and methodologies, may be used by federal agencies even before the completion of such\ncompanion publications. Thus, until each publication is completed, current requirements, guidelines, and\nprocedures, where they exist, remain operative. For planning and transition purposes, federal agencies\nmay wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide\nfeedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\nhttps://csrc.nist.gov/publications. NIST Technical Series Policies\nCopyright, Use, and Licensing Statements\nNIST Technical Series Publication Identifier Syntax\n\nPublication History\nApproved by the NIST Editorial Review Board on 2024-10-16\n\nHow to cite this NIST Technical Series Publication:\nAlagic G, Bros M, Ciadoux P, Cooper D, Dang Q, Dang T, Kelsey J, Lichtinger J, Liu YK, Miller C, Moody D,\nPeralta R, Perlner R, Robinson A, Silberg H, Smith-Tone D, Waller N (2024) Status Report on the First Round\nof the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization\nProcess. (National Institute of Standards and Technology, Gaithersburg, MD), NIST IR 8528."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n| Technology Partner/Collaborator | Build Involvement | |-----------------------------------|--------------------------------------------------------------------------------------------------------| | Symantec Corporation | Symantec Information Centric Analytics v6.5.2 Symantec Security Analytics v8.0.1 | | Cisco Systems | Cisco Identity Services Engine v2.4, Cisco Advanced Malware Protection v5.4, Cisco Stealthwatch v7.0.0 | | Glasswall Government Solutions | Glasswall FileTrust Advanced Threat Protection (ATP) for Email v6.90.2.5 | | Tripwire | Tripwire Log Center v7.3.1, Tripwire Enterprise v8.7 | | Micro Focus | Micro Focus ArcSight Enterprise Security Manager v7.0 Patch 2 | | Semperis | Semperis Directory Services Protector v2.7 | | Component | Product | Function | Cybersecurity Frame- work Subcategories | |----------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| | Mitigation and Containment | Cisco Identity Services Engine (ISE) v2.4 Glasswall FileTrust ATP for Email v6.90.2.5 Semperis DSP v2.7 | • Provides ability to sandbox files locally."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nBalancing exposure to cybersecurity risks throughout the supply chain with the costs and benefits of implementing C-SCRM practices and controls should be a key component of the acquirer's overall approach to C-SCRM. Enterprises should be aware that implementing C-SCRM practices and controls necessitates additional financial and human resources. Requiring a greater level of testing, documentation, or security features from suppliers, developers, system integrators, external system service providers, and other ICT/OT-related service providers may increase the price of a product or service, which may result in increased cost to the acquirer. This is especially true for those products and services developed for general-purpose applications and not tailored to the specific enterprise security or C-SCRM requirements. When deciding whether to require and implement C-SCRM practices and controls, acquirers should consider both the costs of implementing these controls and the risks of not implementing them."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.2.2. 3.2.2. 3.2.2)\n\nDigital Identity Guidelines\n\nThe impact analysis SHALL consider the level of impact for each impact category for each\ntype of impacted entity if an intruder obtains unauthorized access as a member of each\nuser group."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.1.1, A. 3.1.1 Scenario\n\nThe following scenario was simulated to test the architecture's defense against ransomware."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n3.3.2 | C(0e, 2s) Scheme with Unilateral Key Confirmation Provided by Party V to Party U... 3.3.2 C(0e, 2s) Scheme with Unilateral Key Confirmation Provided by Party V to Party U\n\nFigure\\_16 depicts a typical flow for a C(0e, 2s) scheme with unilateral key confirmation from party V to party U."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n- Federal agencies responsible for managing and protecting CUI\n- Nonfederal organizations responsible for protecting CUI\n- Individuals with system development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Individuals with acquisition or procurement responsibilities (e.g., contracting officers)\n- Individuals with system, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Individuals with security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, analysts, independent verifiers and validators)\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 6)"}, {"role": "assistant", "content": "## Table of Contents | Executive Summary....................................................................................................................1 | Executive Summary....................................................................................................................1 | Executive Summary....................................................................................................................1 | |------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| | Introduction .........................................................................................................................2 | Introduction .........................................................................................................................2 | | | Structural Implications of Drivers on the Enterprise Network Landscape .....................2 | Structural Implications of Drivers on the Enterprise Network Landscape .....................2 | | | Security Implications of Drivers on the Enterprise Network Landscape........................3 | Security Implications of Drivers on the Enterprise Network Landscape........................3 | | | The Need for a Security Guide......................................................................................3 | The Need for a Security Guide......................................................................................3 | | | Scope............................................................................................................................4 | Scope............................................................................................................................4 | | | Target Audience............................................................................................................4 | Target Audience............................................................................................................4 | | | Organization of This Document.....................................................................................4 | Organization of This Document.....................................................................................4 | | | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | | Limitations of Network Perimeter-based Protections ....................................................5 | Limitations of Network Perimeter-based Protections ....................................................5 | | | Limitations of VPN-based Access .................................................................................5 | Limitations of VPN-based Access .................................................................................5 | | | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 |"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 9)"}, {"role": "assistant", "content": "| Enterprise Infrastructure Layer ...................................................................................\n| 6 |\n| | Designing a Policy Framework for ZTA for Cloud-Native Application Environments. 7 | Designing a Policy Framework for ZTA for Cloud-Native Application Environments. 7 |\n| | Functional Components of Identity-Based Segmentation Policies for ZTA.................. | 8 |\n| | Shortcomings of Identity-Based Segmentation Policies for Enterprise ZTA ................"}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Data Structure for Integrity Protection with Erasure Capability provide? (Part 2)"}, {"role": "assistant", "content": "f each application. When a license application is received, TPO will contact you regarding the licensing process and to obtain additional information that may be necessary for the application process.\nA license application should include the prospective licensee's intentions for research and development of the invention(s) and a description of the resources and technical capabilities of the prospective licensee to bring the invention to practical application. ## Disclaimer\n\nAny 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\n\nFor additional information on NIST's Cybersecurity programs, projects and publications, visit the Computer Security Resource Center. Information on other efforts at NIST and in the Information Technology Laboratory (ITL) is also available. Submit comments on this publication to:\n\nblock-matrix@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## I. BACKGROUND\n\nThis document describes a data structure, referred to as a data block matrix, that supports the ongoing addition of hash-linked records while also allowing for the deletion of arbitrary records, thereby preserving hash-based integrity assurance that other blocks are unchanged. (This publication is a final version of [1].)\n\n## II. DATA STRUCTURE\n\nFig. 1 shows a matrix with numbered data blocks, where a block may contain a single record or multiple transactions. Every row or column is terminated with a block containing a hash of that row or column (e.g., H 0 , -is the hash of row 0)."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 5)"}, {"role": "assistant", "content": "| 41 |\n\n## NIST USABLE CYBERSECURITY\n\nWe are the Usable Cybersecurity team within the National Institute of Standards and Technology (NIST) Visualization and Usability Group.\nOur multi-disciplinary team conducts research at the intersection of cybersecurity, human factors, cognitive science, and psychology to 'champion the human in cybersecurity.' Through research and other human-centered projects, we seek to better understand and improve people's interactions with cybersecurity systems, products, and services. We provide data and guidance to policymakers, system engineers, and cybersecurity professionals so that they can make better decisions that consider the human element, thereby advancing cybersecurity adoption and empowering people to be active, informed participants in cybersecurity. ## Why Usable Cybersecurity Is Important\n\n\n\nSecurity must be usable by people ranging from non-technical users to experts and system administrators. Furthermore, systems must be usable while maintaining security. In the absence of usable security, there is ultimately no effective security. -A Roadmap for Cybersecurity Research [DHS2009]\n\nUsable cybersecurity considers the relationships and interactions between people and cybersecurity, including people's perceptions, the challenges they encounter, and the design of usable systems, products, and services that also result in improved cybersecurity outcomes. When organizations, policy makers, and cybersecurity professionals fail to consider the human element, there can be real consequences, for example: more calls to the help desk, people resorting to less-secure workarounds, user frustration, and the perception that cybersecurity is inconvenient and burdensome. ## EXECUTIVE SUMMARY\n\nCybersecurity role-based training (RBT) includes specialized training on policies, procedures, and tools for individuals who are assigned roles having security and privacy responsibilities [SP800-53]."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.4.1. 3.4.1. 3.4.1), guidance (Section 3."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 8)"}, {"role": "assistant", "content": "gement is encouraged. For more information on IoT device security and privacy considerations, see NISTIR 8228, Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks [4].\n## 2 IoT Device Cybersecurity Capability Core Baseline Definition\n\nTable 1 defines the IoT device cybersecurity capability core baseline. The core baseline's role is as a default for minimally securable devices. However, device cybersecurity capabilities will often need to be added or removed from an IoT device's design, integration, or acquisition to best address an organization's common cybersecurity risks. The core baseline does not specify how the device cybersecurity capabilities are to be achieved, so organizations who choose to adopt the core baseline for any of the IoT devices they produce, integrate, or acquire have considerable flexibility in implementing it to effectively address needs. Each row in Table 1 covers one of the device cybersecurity capabilities in the core baseline:\n\n- The first column defines the capability. Note that Figure 1, which is located in Appendix A, indicates how the capability relates to the risk mitigation areas and challenges defined in NISTIR 8228, Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks [3]. - The second column provides a numbered list of common elements of that capability-elements an organization seeking to implement the core baseline often (but not always) would use in order to achieve the capability. (Note: the elements are not intended to be comprehensive, nor are they in any particular order.)\n- The third column explains the rationale for needing the capability and its common elements to be included in the core baseline. - The last column lists IoT reference examples that indicate existing sources of IoT device cybersecurity guidance specifying a similar or related capability."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\naft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 9)"}, {"role": "assistant", "content": "ework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53].\nThe security control mappings can be useful to organizations that wish to demonstrate compliance to the security requirements in the context of their established information security programs when such programs have been built using the NIST security controls. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nThe software development and use of AI models and AI systems inherit much of the same risk as any other digital system. A unique challenge for this community is the blurring of traditional boundaries between system code and system data, as well as the use of plain human language as the means of interaction with the systems. AI models and systems, their configuration parameters (e.g., model weights), and the data they interact with (e.g., training data, user queries, etc.) can form closed loops that can be manipulated for unintended functionality.\n\nAI model and system development is still much more of an art than an exact science, requiring developers to interact with model code, training data, and other parameters over multiple iterations. Training datasets may be acquired from unknown, untrusted sources. Model weights and other training parameters can be susceptible to malicious tampering. Some models may be complex to the point that they cannot easily be thoroughly inspected, potentially allowing for undetectable execution of arbitrary code. User queries can be crafted to produce undesirable or objectionable output and - if not sanitized properly - can be leveraged for injection-style attacks. The goal of this document is to identify the practices and tasks needed to address these novel risks.\n\nThis Profile's scope is AI model development , which includes data sourcing for, designing, training, fine-tuning, and evaluating AI models, as well as incorporating and integrating AI models into other software. Consistent with SSDF version 1.1 and EO 14110, practices for the deployment and operation of AI systems with AI models are out of scope . Similarly, while cybersecurity practices for training data and other forms of data being used for AI model development are in scope, the rest of the data governance and management life cycle is out of scope."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 6)"}, {"role": "assistant", "content": "................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1.\nDeveloper Environment ...............................................................................................................8 |\n| 3.1.2. Threat Actors................................................................................................................................8 |\n| 3.1.3. Attack Vectors ..............................................................................................................................9 |\n| 3.1.4. Attack Targets (Assets).................................................................................................................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1. Baseline Security ........................................................................................................................11 |\n| 3.2.2. Controls for Interacting With SCM Systems...............................................................................12 |\n| 4. CI/CD Pipelines -Background, Security Goals, and Entities to be Trusted .....................................13 |\n| 5. Integrating SSC Security Into CI/CD Pipelines.................................................................................15 |\n| 5.1.1. Secure Build................................................................................................................................16 |\n| 5.1.2. Secure Pull-Push Operations on Repositories............................................................................17 |\n| 5.1.3."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.9. UOV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.9. UOV"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. | Symmetric key | Acryptographic key that is shared between two or more entities and used with a cryptographic application to process information. |\n|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Symmetric-key algorithm | A cryptographic algorithm that uses secret keying material that is shared between authorized parties."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 4)"}, {"role": "assistant", "content": "lishment to be studied: BIKE, Classic McEliece, HQC, and SIKE. This report describes the evaluation and selection process of these fourth-round candidates based on public feedback and internal review.\nThe report summarizes each of the candidate algorithms and identifies those selected for standardization. The only key-establishment algorithm that will be standardized is HQC, and NIST will develop a standard based on HQC to augment its key-establishment portfolio. ## Keywords\n\ncryptography; key-encapsulation mechanism (KEM); key establishment; post-quantum cryptography; quantum-resistant; quantum-safe. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Contents\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . | . . . | 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|\n| 1.1. | Purpose and Organization of This Document . . . . | 3 |\n| 2. Evaluation Criteria and Selection Process . . | . . . . . . . . | 4 |\n| 2.1. | Acceptance of the Fourth-Round Candidates . ."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nApplication whitelisting technologies, also known as application control programs, are used to specify which applications are authorized for use on a host. Most application whitelisting technologies can be run in two modes: audit and enforcement. In enforcement mode, the technology generally prohibits all applications that are not in the whitelist from being executed. In audit mode, the technology logs all instances of non-whitelisted applications being run on the host, but does not act to stop them. The tradeoff between enforcement mode and audit mode is simple; using enforcement mode will stop malware from executing, but it may also prevent benign applications not included on the whitelist from being run. Organizations deploying application whitelisting technologies should consider first deploying them in audit mode, so as to identify any necessary applications missing from the whitelist, before reconfiguring them for enforcement mode. Running application whitelisting technologies in audit mode is analogous to intrusion detection software without intrusion prevention capabilities; it can be useful after an infection occurs to determine which hosts were affected, but it has no ability to prevent infections."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 4)"}, {"role": "assistant", "content": "ify, add, or delete Vendor Evidence (VE) and/or Test Evidence (TE) specified under paragraph 6.14 of the ISO/IEC 24759 and specify the order of the security policy as stated in ISO/IEC 19790:2012 B.1.\n## Keywords\n\nCMVP; Cryptographic Module Validation Program; FIPS 140; FIPS 140 testing; ISO/IEC 19790; ISO/IEC 24759; security policy; testing requirement; vendor documentation; vendor evidence. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Supplemental Content\n\nSee https://csrc.nist.gov/projects/cmvp/sp800-140-series-info for details about the NIST Special Publication (SP) 800-140x series publications and their relationships to ISO/IEC 19790 and ISO/IEC 24759. ## Audience\n\nThis document is intended for vendors, testing labs, and CMVP to address issues in ISO/IEC 19790, Information technology - Security techniques - Security requirements for cryptographic modules , and ISO/IEC 24759, Information technology - Security techniques - Test requirements for cryptographic modules ."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nhemes may use the blockchain as a database for storing only the policies but not use the blockchain for access enforcement, such that PDP and PEP functions are performed off-the-chain.\nHowever, the main problems of the traditional mechanism, like single point of failure, will be inherited [GBHC]. In addition, considerations should include governance frameworks for legal processes, applicable smart contracts, and the responsibilities of participating AC nodes even though the AC system is based on permissioned blockchains."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.2.2 rsakpg2-prime-factor ... 3.2.2 rsakpg2-prime-factor\n\nrsakpg2-prime-factor is the generator in the RSAKPG2 family such that the private key is in the prime-factor format ( p , q , d ). 3.2.2)."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide?"}, {"role": "assistant", "content": "NIST Special Publication\nNIST SP 800-63B-4\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nDavid Temoshok\nJames L. Fenton\nYee-Yin Choong\nNaomi Lefkovitz\nAndrew Regenscheid\nRyan Galluzzo\nJustin P. Richer\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-63B-4\n\n\fNIST Special Publication\nNIST SP 800-63B-4\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nDavid Temoshok\nNaomi Lefkovitz *\nRyan Galluzzo\nApplied Cybersecurity Division\nInformation Technology Laboratory\n\nYee-Yin Choong\nInformation Access Division\nInformation Technology Laboratory\n\nAndrew Regenscheid\nComputer Security Division\nInformation Technology Laboratory\n\nJames L. Fenton\nAltmode Networks\n\nJustin P. Richer\nBespoke Engineering\n\n* Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-63B-4\n\nJuly 2025\n\nNational Institute of Standards and Technology\nCraig Burkhardt, Acting Under Secretary for Standards and Technology and Acting NIST Director\n\nU.S. Department of Commerce\nHoward Lutnick, Secretary\n\n\fCertain equipment, instruments, software, or materials, commercial or non-commercial,\nare identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product\nor service by NIST, nor does it imply that the materials or equipment identified are\nnecessarily the best available for the purpose. There may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice PL.L2-3.15.6 (NIST 3.15.6)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.15.6. 3.15.6."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.15.6", "cmmc_practice_id": "PL.L2-3.15.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 2)"}, {"role": "assistant", "content": "y and Privacy\n\n## JOINT TASK FORCE\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-37r2\n\n## December 2018\n\n\n\nU.S. Department of Commerce Wilbur L.\nRoss, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-37, Revision 2 Natl. Inst. Stand. Technol. Spec. Publ. 800-37, Rev."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\nrunning up against is, how do you automate a test when the spec is so woolly? Then you have many degrees of freedom to implement to the spec and the test language can't accommodate all those degrees of freedom. There's too many millions of possible configurations. So, yeah. Take making standards seriously and include all people in it so that they can bring their expertise to how to do it right.' (C05)\n\n'So if the crypto primitives were already validated, for example, the FIPS 140-2 certification, we already have a baseline that we are comfortable with…The government can validate it. Then after we may build on top of that.' (C11)"}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nrocesses. Although information systems typically support mission/business processes, the processes also depend on a variety of other resources and capabilities not associated with information systems.\nRecovery of mission essential functions is addressed by COOP plans or business continuity plans. These plans are part of a suite of security and emergency management-related plans further described in Section 2.2. The ISCP may be prepared in coordination with disaster recovery planning, COOP planning, or business continuity planning to the degree that a particular system is necessary to provide a capability that is required during any of these events/efforts."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.15 (NIST 3.1.15)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.15. 3.1.15."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.15", "cmmc_practice_id": "AC.L2-3.1.15", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.1.3. 3.1.3. 3.1.3."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nOne of the basic tenets of zero trust is to remove the implicit trust in users, services, and devices based only on their network location, affiliation, and ownership. NIST Special Publication 800207 has laid out a comprehensive set of zero trust principles and referenced zero trust architectures (ZTA) for turning those concepts into reality. A key paradigm shift in ZTAs is the change in focus from security controls based on segmentation and isolation using network parameters (e.g., Internet Protocol (IP) addresses, subnets, perimeter) to identities. From an application security point of view, this requires authentication and authorization policies based on application and service identities in addition to the underlying network parameters and user identities. This in turn requires a platform that consists of Application Programming Interface (API) gateways, sidecar proxies, and application identity infrastructures (e.g., Secure Production Identity Framework for Everyone [SPIFFE]) that can enforce those policies irrespective of the location of the services or applications, whether on-premises or on multiple clouds. The objective of this publication is to provide guidance for realizing an architecture that can enforce granular application-level policies while meeting the runtime requirements of ZTA for multicloud and hybrid environments. egress gateway; identity-tier policies; ingress gateway; microservices; multi-cloud; network-tier policies; service mesh; sidecar proxy; SPIFFE; transit gateway; zero trust; zero trust architecture. | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide?"}, {"role": "assistant", "content": "## NIST SPECIAL PUBLICATION 1800-26\n\n## Data Integrity:\n\n## Detecting and Responding to Ransomware and Other Destructive Events\n\nIncludes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C)\n\nJennifer Cawthra Michael Ekstrom Lauren Lusty Julian Sexton John Sweetnam\n\nFINAL\n\nThis publications is available free of charge from https://doi.org/10.6028/NIST.SP.1800-26. This publication is available free of charge from https://www.nccoe.nist.gov/projects/building-blocks/data-integrity/detect-respond. \n\nNIST SPECIAL PUBLICATION 1800-26\n\n## Data Integrity: Detecting and Responding to Ransomware and Other Destructive Events\n\nIncludes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C)\n\nJennifer Cawthra National Cybersecurity Center of Excellence NIST\n\nMichael Ekstrom Lauren Lusty Julian Sexton John Sweetnam The MITRE Corporation McLean, Virginia\n\nFINAL\n\nDECEMBER 2020\n\n\n\nU.S. Department of Commerce Wilbur Ross, Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Undersecretary of Commerce for Standards and Technology\n\n## NIST SPECIAL PUBLICATION 1800-26A\n\n## Detecting and Responding to Ransomware and Other\n\n## Data Integrity: Destructive Events\n\n## Volume A:\n\nExecutive Summary\n\n## Jennifer Cawthra\n\nNational Cybersecurity Center of Excellence NIST\n\nMichael Ekstrom Lauren Lusty Julian Sexton John Sweetnam Anne Townsend\n\nThe MITRE Corporation McLean, Virginia\n\n## December 2020\n\nFINAL\n\nThis publications is available free of charge from https://doi.org/10.6028/NIST.SP.1800-26. This publication is available free of charge from https://www.nccoe.nist.gov/projects/building-blocks/data-integrity/detect-respond. \n\n## Executive Summary\n\nThe CIA triad represents the three pillars of information security: confidentiality, integrity, and availability, as follows."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n| EXECUTIVE SUMMARY......................................................................................................... iii | EXECUTIVE SUMMARY......................................................................................................... iii | EXECUTIVE SUMMARY......................................................................................................... iii |\n|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|\n| 1 INTRODUCTION................................................................................................................. | 1 INTRODUCTION................................................................................................................. | 1 |\n| 2 REPORTING CONVENTIONS.......................................................................................... | 2 REPORTING CONVENTIONS.......................................................................................... | 2 |\n| 3 SECURITY AWARENESS APPROACHES..................................................................... | 3 SECURITY AWARENESS APPROACHES....................................................................."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n................................................................... | Executive Summary.................................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body .................................................... | 6 | |\n| Preparation................................................................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nNFC (communications protocol)\nNear-Field Communication\n\napproved cryptography\nAn encryption algorithm, hash function, random bit generator, or similar technique that\nis Federal Information Processing Standards (FIPS)-approved or NIST-recommended.\nApproved algorithms and techniques are either specified or adopted in a FIPS or NIST\nrecommendation.\n\nasymmetric keys\nTwo related cryptographic keys comprised of a public key and a private key that are used\nto perform complementary operations, such as encryption and decryption or signature\nverification and generation."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Blockchain for Access Control Systems provide? (Part 10)"}, {"role": "assistant", "content": "nodes. The main purpose of smart contracts is to satisfy common contractual conditions, as well as minimize exceptions (both malicious and accidental) and the need for trusted intermediaries [IR8202].\nEvery blockchain node that executes the smart contract should arrive at the same result given the same input. Blockchain can be utilized for AC systems as a trustable alternative for a single entity/organization or a member of a large-scale system to enforce AC policies. The robust, distributed nature of blockchain technology can overcome the limitations of traditional AC systems in a decentralized and efficient way. It is supported by the following infrastructural properties that are not included in traditional AC mechanisms unless specifically implemented:\n\n- Tamper-evident and tamper-resistant design prevents the alteration AC data (i.e., attributes, policy rules, environment conditions, and access requests) and AC logs (i.e., request permissions and previous AC data) and reduces the probability of frauds. - The control of authorization processing is decentralized, and the storage of AC data/logs has no single point of failure, thus providing more system tolerance and availability. - The traceability of blocks allows AC data/logs and system states to be seen and tracked. - The execution of arbitrary programs in smart contracts allows for controls on distributed AC data and authorization processes. - Consensus mechanisms and protocols jointly regulate the participating AC entities/organizations in determining policy rules through blocks or smart contracts. Blockchain properties improve the security, flexibility, scalability, integrity, and confidentiality of AC data/logs and processes (compared to traditional AC systems) by allowing organizations to verify and audit AC data transactions and processes to track the states of their AC systems hosted on distributed sites [SP162]."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. The authors, Peter Mell of the National Institute of Standards and Technology (NIST) and Karen Kent and Joseph Nusbaum of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. The authors would particularly like to acknowledge Tim Grance and Murugiah Souppaya of NIST and Lucinda Gagliano, Thomas Goff, and Pius Uzamere of Booz Allen Hamilton for their keen and insightful assistance throughout the development of the document."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.1.2 rsakpg1-prime-factor ... 3.1.2 rsakpg1-prime-factor\n\nrsakpg1-prime-factor is the generator in the RSAKPG1 family such that the private key is in the prime factor format ( p , q , d ). 3.1.2)."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CONTROL NUMBER | CONTROL NAME CONTROL ENHANCEMENT NAME | PRIVACY CONTROL BASELINE | SECURITY CONTROL BASELINES | SECURITY CONTROL BASELINES | SECURITY CONTROL BASELINES | |------------------|-------------------------------------------------------|----------------------------|------------------------------|------------------------------|------------------------------| | CONTROL NUMBER | CONTROL NAME CONTROL ENHANCEMENT NAME | PRIVACY CONTROL BASELINE | LOW | MOD | HIGH | | AC-4(2) | PROCESSING DOMAINS | | | | | | AC-4(3) | DYNAMIC INFORMATION FLOW CONTROL | | | | | | AC-4(4) | FLOW CONTROL OF ENCRYPTED INFORMATION | | | | x | | AC-4(5) | EMBEDDED DATA TYPES | | | | | | AC-4(6) | METADATA | | | | | | AC-4(7) | ONE-WAY FLOW MECHANISMS | | | | | | AC-4(8) | SECURITY AND PRIVACY POLICY FILTERS | | | | | | AC-4(9) | HUMAN REVIEWS | | | | | | AC-4(10) | ENABLE AND DISABLE SECURITY OR PRIVACY POLICY FILTERS | | | | | | AC-4(11) | CONFIGURATION OF SECURITY OR PRIVACY POLICY FILTERS | | | | | | AC-4(12) | DATA TYPE IDENTIFIERS | | | | | | AC-4(13) | DECOMPOSITION INTO POLICY - RELEVANT SUBCOMPONENTS | | | | | | AC-4(14) | SECURITY OR PRIVACY POLICY"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Contingency Planning Guide for Federal Information Systems provide? (Part 5)"}, {"role": "assistant", "content": "Technology (NIST), Amy Wohl Phillips, Dean Gallup, and David Lynes of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content.\nThe authors would like to acknowledge Kelley Dempsey, Esther Katzman, Peter Mell, Murugiah Souppaya, Lee Badger, and Elizabeth Lennon of NIST, and David Linthicum of Booz Allen Hamilton for their keen and insightful assistance with technical issues throughout the development of the document. ## Table of Contents\n\n| Chapter 1."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The rapid development and wide application of distributed network systems have made network security - especially access control and data privacy - ever more important. Blockchain technology offers features such as decentralization, high confidence, and tamper-resistance, which are advantages to solving auditability, resource consumption, scalability, central authority, and trust issues - all of which are challenges for network access control by traditional mechanisms."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nHPC file systems in the data storage zone provide superior data access speed and much larger storage capacity compared to average enterprise file systems. Hard disk failure is a threat due to the large number of disks deployed in the data storage zone. Incident response and contingency planning controls may not be easy to implement, and file backup, recovery, and forensic imaging may become infeasible. The security measures that can be implemented on the enterprise file systems may take an unacceptably long time and degrade HPC file system performance in an unacceptable way. system that can remotely mount a file system will have complete control over all file system data. This access could be used to gain privileges elsewhere within other zones of the HPC security enclave. Hashing is another technique for monitoring data integrity. Data files can be hashed at the beginning to acquire hashing keys. A file is not modified if its hashing key remains the same. Parallel file systems maintain many types of metadata (e.g., user ID, group ID, modification time, checksum, etc.). Hashing metadata is another way to check whether a file has been modified. Periodically scanning file systems for malware is a proven technique for monitoring data integrity. However, scanning an HPC system for malware is challenging. HPC data storage can easily contain a petabyte or more of data. Existing malware scanning tools are mainly designed for a single machine or laptop. They are not efficient or fast enough to scan large HPC data storage systems. Furthermore, the scanning operation can adversely affect the performance of running jobs. HPC systems may consider alternate implementation options for malware scanning to alleviate some of the stated impacts. For example, conduct scanning at write, and conduct subsequent batch scanning at read. Protection against ransomware attacks on HPC data is especially important."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- A business champion: Someone who is responsible for developing and maintaining the incident response plan.\n- Who to call: List all the individuals who may be part of the incident response efforts. Include their contact information, roles, and responsibilities.\n- What/when/how to report: List the business' communications/reporting responsibilities as required by laws, regulations, contracts, agreements, or policies.\n- Also, most federal contracts will include specific reporting and notification requirements that should be included in the Incident Response Plan\n\nDescription: Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of the systems; and employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n| 1 | Summary..............................................................................................1 | Summary..............................................................................................1 | |-----|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | 1.2 | Solution..........................................................................................................................2 | | | 1.3 | Benefits..........................................................................................................................3 | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | 2.1 | Typographic Conventions..............................................................................................5 | | 3 | Approach .............................................................................................6 | Approach .............................................................................................6 | | | 3.1 | Audience........................................................................................................................6 | | | 3.2 | Scope .............................................................................................................................6 | | | 3.3 | Assumptions..................................................................................................................7 | | | 3.4 | Risk Assessment ............................................................................................................7 | | | 3.4.1 | Risk................................................................................................................................8 | | | | 3.4.2 Security Control Map....................................................................................................9 | | | 3.5 Technologies................................................................................................................13 | 3.5 Technologies................................................................................................................13 | | 4 | Architecture .......................................................................................16 | Architecture .......................................................................................16 | | | 4.1 Architecture Description .............................................................................................16 | 4.1 Architecture Description .............................................................................................16 | | | 4.1.1 | High-Level Architecture ..............................................................................................16 | | | 4.1.2 | Architecture Components...........................................................................................17 | | 5 | Security Characteristic Analysis..........................................................20 | Security Characteristic Analysis..........................................................20 | | | 5.1 Assumptions and Limitations | ......................................................................................20 | | | 5.2 Build | Testing................................................................................................................20 | | | 5.3 | Scenarios and Findings................................................................................................21 | | | 5.3.1 | Ransomware via Web Vector and Self-Propagation...................................................21 | | | 5.3.2 | Destructive Malware via USB Vector..........................................................................22 | | |"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software... 3.1.3 ZTA y el uso de una infraestructura de red y perímetros definidos a través de software\n\nEl último modelo utiliza la infraestructura de red para implementar una ZTA."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 10)"}, {"role": "assistant", "content": "..................11 | |\n| 3.4.4.\n| SCAP Generation Script ........................................................................................11 | |\n| 3.4.5."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Risk Assessment?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n1 One resource supporting both Information Reception and Information Dissemination to others in the ecosystem about vulnerabilities is found in Draft NIST SP 800-216: Federal Vulnerability Disclosure Guidelines [17] . This document recommends guidance for establishing a federal vulnerability disclosure framework and highlights the importance of proper handling of vulnerability reports and communicating the minimization or elimination of vulnerabilities."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 8)"}, {"role": "assistant", "content": "10, ACPT], data structure [MARG], system simulation [VK13, ACRLCS], and test oracle [ACTS] to verify the expected functional logic implied in policy rules [AS15]. The model proof method converts policy to a finite state machine (FSM) and verifies test access cases against it to detect policy faults, such as rule conflict, access blocking, or privilege leakage [SP192]. For instance, [ACPT] applies the symbolic model verification [NuSMV] tool to build an FSM model in terms of policy rule attributes. Thus, a test case is represented by a deterministic finite state transducer that corresponds to the FSM, which should satisfy the two requirements below after it takes actions in compliance with the test case:\n\n- 1) Safety - There is no violation of the FSM model to the test case, and it is assured that the FSM will eventually be in a desired state. - 2) Liveness - Where the FSM will have neither a deadlock in which the system waits forever for system events nor a livelock in which the model repeatedly executes the same operations forever [NuSMV]. An access control policy verification method uses structured data that represents underlying policy rule logics. The data structure, such as a binary decision diagram [CFMY93], is given assignments of binary values to the policy attributes that traverse from the root to a terminal of the rule's permission [Fisler et al. 05]. This method is used by software tool suite Margrave [MARG] for verifying safety requirements (test cases) against policies written in eXtensible Access Control Markup Language (XACML) [XACML]. Margrave's API verifies safety requirements in the form of queries, which should hold by the binary tree. Otherwise, counterexamples are produced indicating violations of the tree structure [SND13]. Model proof and data structure methods initially accept the policy under verification as faultless until tested against specified cases or requirements."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 4)"}, {"role": "assistant", "content": "h incorporating cybersecurity incident response recommendations and considerations throughout their cybersecurity risk management activities as described by the NIST Cybersecurity Framework (CSF) 2.0.\nDoing so can help organizations prepare for incident responses, reduce the number and impact of incidents that occur, and improve the efficiency and effectiveness of their incident detection, response, and recovery activities. Readers are encouraged to utilize online resources in conjunction with this document to access additional information on implementing these recommendations and considerations. ## Keywords\n\ncyber threat information sharing; Cybersecurity Framework; cybersecurity incident; cybersecurity risk management; incident handling; incident management; incident response. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Supplemental Content\n\nNIST has established an Incident Response project page that hosts links to resources with additional information on incident response activities."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n...................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6.\nAssessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "CONTRIBUTIONS TO NIST SPECIAL PUBLICATION 800-53\n\nThe authors wanted to acknowledge the many individuals who contributed to previous versions of Special Publication 800-53 since its inception in 2005.\nThey include Marshall Abrams, Dennis Bailey, Lee Badger, Curt Barker, Matthew Barrett, Nadya Bartol, Frank Belz, Paul Bicknell, Deb Bodeau, Paul Brusil, Brett Burley, Bill Burr, Dawn Cappelli, Roger Caslow, Corinne Castanza, Mike Cooper, Matt Coose, Dominic Cussatt, George Dinolt, Randy Easter, Kurt Eleam, Denise Farrar, Dave Ferraiolo, Cita Furlani, Harriett Goldman, Peter Gouldmann, Tim Grance, Jennifer Guild, Gary Guissanie, Sarbari Gupta, Priscilla Guthrie, Richard Hale, Peggy Himes, Bennett Hodge, William Hunteman, Cynthia Irvine, Arnold Johnson, Roger Johnson, Donald Jones, Lisa Kaiser, Stuart Katzke, Sharon Keller, Tom Kellermann, Cass Kelly, Eustace King, Daniel Klemm, Steve LaFountain, Annabelle Lee, Robert Lentz, Steven Lipner, William MacGregor, Thomas Macklin, Thomas Madden, Robert Martin, Erika McCallister, Tim McChesney, Michael McEvilley, Rosalie McQuaid, Peter Mell, John Mildner, Pam Miller, Sandra Miravalle, Joji Montelibano, Douglas Montgomery, George Moore, Rama Moorthy, Mark Morrison, Harvey Newstrom, Sherrill Nicely, Robert Niemeyer, LouAnna Notargiacomo, Pat O'Reilly, Tim Polk, Karen Quigg, Steve Quinn, Mark Riddle, Ed Roback, Cheryl Roby, George Rogers, Scott Rose, Mike Rubin, Karen Scarfone, Roger Schell, Jackie Snouffer, Ray Snouffer, Murugiah Souppaya, Gary Stoneburner, Keith Stouffer, Marianne Swanson, Pat Toth, Glenda Turner, Patrick Viscuso, Joe Weiss, Richard Wilsher, Mark Wilson, John Woodward, and Carol Woody."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. | 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n## Protecting Information and System Integrity in Industrial Control System Environments: Cybersecurity for the Manufacturing Sector\n\nThe first draft of this publication is available free of charge from https://www.nccoe.nist.gov/publications/practice-guide/protecting-information-and-systemintegrity-industrial-control-system-draft\n\n## Protecting Information and System Integrity in Industrial Control System Environments: Cybersecurity for the Manufacturing Sector"}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control.\n\nThe Defense Science Board Report, Resilient Military Systems and the Advanced Cyber Threat [DSB 2013], provides a sobering assessment of the vulnerabilities in the United States Government, the U.S. critical infrastructure, and the systems supporting the mission-essential operations and assets in the public and private sectors.\n\n'…The Task Force notes that the cyber threat to U.S. critical infrastructure is outpacing efforts to reduce pervasive vulnerabilities, so that for the next decade at least the United States must lean significantly on deterrence to address the cyber threat posed by the most capable U.S. adversaries. It is clear that a more proactive and systematic approach to U.S. cyber deterrence is urgently needed…'"}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "ft publications during the designated public comment periods\nand provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at\nhttps://csrc.nist.gov/publications.\nSubmit comments on this publication to: sec-cert@nist.gov\n\nNational Institute of Standards and Technology\nAttn: Computer Security Division, Information Technology Laboratory\n100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. T\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\nI\n\n. NIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nReports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory\n(ITL) promotes the U.S. economy and public welfare by providing technical leadership for the\nNation’s measurement and standards infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT). ITL’s responsibilities include the development\nof management, administrative, technical, and physical standards and guidelines for the cost-\neffective security of other than national security-related information in federal information\nsystems. The Special Publication 800-series reports on ITL’s research, guidelines, and outreach\nefforts in information systems security and privacy and its collaborative activities with industry,\ngovernment, and academic organizations."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.4. 3.1.4."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 8)"}, {"role": "assistant", "content": ".................61 |\n| List of Tables |\n| Table 1.\nExample of a phased MFA deployment................................................................................16 |\n| List of Figures |\n| Fig. 1. Callout box formats..................................................................................................................4 |\n| Fig. 2. The identity provider (IdP) can be at hosted at the state or county, or both...............................7 |\n| Fig. 3. Single sign-on eliminates repeated MFA challenges to users......................................................9 |\n| Fig. 4. An example of a phishing attack. ............................................................................................10 |\n| Fig. 5. MFA implementation points...................................................................................................11 |\n| Fig. 6. Potential authentication points for local agencies. ..................................................................17 |\n| Fig. 7. MFA at the CAD/RMS application. ..........................................................................................18 |\n| Fig. 8. Local agency identity service Integrated with CAD/RMS using identity federation....................19 |\n| Fig. 9. State-provided identity service for use by a local agency.........................................................20 |\n| Fig. 11. Common architecture for implementing MFA directly with state portal.................................22 |\n| Fig. 12."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide?"}, {"role": "assistant", "content": "## Transitioning to the Security Content Automation Protocol (SCAP) Version 2\n\nDavid Waltermire Computer Security Division Information Technology Laboratory\n\nJessica Fitzgerald-McKay Cybersecurity Solutions National Security Agency Fort Meade, MD\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.CSWP.09102018\n\nSeptember 10, 2018\n\n\n\n## Abstract\n\nThe Security Content Automation Protocol (SCAP) version 2 (v2) automates endpoint posture information collection and the incorporation of that information into network defense capabilities using standardized protocols. SCAP v2 expands the endpoint types supported by SCAP v1 through the explicit inclusion of network equipment, Internet of Things (IoT), and mobile devices in its scope. To automate self-reporting of posture information from endpoint machines, SCAP v2 will integrate with existing network management protocols that include the Internet Engineering Task Force (IETF) Network Endpoint Assessment (NEA) protocols. SCAP v2 will streamline SCAP content acquisition and reuse through its use of the IETF Resource Oriented Lightweight Information Exchange (ROLIE) protocol. Improvements to software version identification and the incorporation of patch information will be made by transitioning from the Common Platform Enumeration (CPE) to Software Identification (SWID) Tags. SCAP v2 provides component-level interoperability via a modular and extensible architecture. This white paper provides a gap analysis of SCAP v1 and an overview of how SCAP v2 will address these gaps; describes the SCAP 2.0 architecture; and provides a plan for completing the work necessary to finalize SCAP v2."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nMany U.S. Government Information Technology (IT) systems need to employ strong cryptographic schemes to protect the integrity and confidentiality of the data that they process. Algorithms such as the Advanced Encryption Standard (AES), as defined in Federal Information Processing Standard (FIPS) 197, 1 and HMAC, as defined in FIPS 198, 2 make attractive choices for the provision of these services. These algorithms have been standardized to facilitate interoperability between systems. However, the use of these algorithms requires the establishment of secret keying material that is shared in advance. Trusted couriers may manually distribute this secret keying material, but as the number of entities using a system grows, the work involved in the distribution of the secret keying material grows rapidly. Therefore, it is essential to support the cryptographic algorithms used in modern U.S. Government applications with automated keyestablishment schemes. | Additional input | Information known by two parties that is cryptographically bound to the secret keying material being protected using the encryption operation."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\ncycle. The last panel member was Matthew Areno, Senior Principal Engineer for Intel Corporation. Matthew admitted that there is no industry standard to describe the phases of the supply chain for ICs.\nHowever, his expertise and history with the industry have enabled him to develop his own conceptual model that is divided into seven stages: concept, development, integration, manufacturing, testing, provisioning, and deployment. During his time at Intel, Matthew has worked to develop a threat model for Intel's supply chain. Intel discovered that each of their teams approached the exercise of threat modeling in different ways, which made it difficult and time-consuming for them to exchange information. As a result, Intel has been developing and deploying a unified Threat Modeling Tool that utilizes vulnerability resources like MITRE Common Weakness Enumeration (CWE) to automatically make design-based suggestions on potential vulnerabilities and mitigations. The tool also forms a closed loop that incorporates knowledge learned from Intel's own design processes."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| VULNERABILITIES | VULNERABILITIES | 6-5 | | 3.1 | Targets | Targets | 6-5 | | | 3.1.1 | Vul nerabl llties of Data and Prog ranis •••••••••••«••«•••••••«••••••••• | 6~5 | | | | Vulnerabilities of Terminals | 6-7 | | | 3.1.2 3.1.3 | Vulnerabilities of Media | 6-7 | | | 3.1.4 | Vulnerability of Services | 6-9 | | 3.2 | Hazards | | 6-10 | | | 3.2.1 | Natural Hazards | 6-10 | | | 3.2.2 Man-made Hazards | 3.2.2 Man-made Hazards | 6-10 | | 4.1 | CONTROLS Control Principles | CONTROLS Control Principles | 6-11 | | | | | 6-11 | | | 4.1.1 | Separation of Duties | | | | 4.1.2 | Restrict Access | 6-12 | | | 4.1.3 | Independent Authorization | 6-12 | | | 4.1.4 | Individual Accountability | 6-12 | | | 4.1.5 | Test of Concealment | 6-12 6-12 | | | 4.1.6 Test of Sensitive Combinations | 4.1.6 Test of Sensitive Combinations | 6-12 | | 4.2 | Control Measures | Control Measures | 6-12 | | | 4.2.1 | Explicit Assignment of Responsibility 4.2.2 Physical and Environmental Controls | 6-13 |"}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\nIn addition to functionalities like revocation, accountability, attribute privacy protection, policy updating, decentralization (multi-authorities), and key hierarchy for practical access control system deployments [ZDXSLZ], the applicable access policy structure for fundamental ABE is restricted to supporting non-monotone and stated policy rules [TKN]. For example, CP-ABE allows data owners to define their own access policies by attributes and, thus, support complex access control policy structure. However, by only associating attributes, decryption keys are organized logically as a static set. Users can only use all possible combinations of attributes in the set of keys issued to compose their policies, and it has restrictions for specifying policies, attribute managements (e.g., applying environment conditions and dynamic attributes), and the application of deny rules. This may fail to satisfy the enterprise requirements of access control in terms of flexibility and dynamic properties [BS]. However, research has introduced methods to handle the non-monotone restriction [AG, AN, AT, TKN] to address the deny rule issue. The policy issue can be addressed by combining various technologies, such as refreshing user secret keys more frequently, shortening the expiration time interval, or allowing dynamic attributes to be updated closer to real-time. In KP-ABE, the secret key and ciphertext relate to a set of attributes to offer fine-grained access control [BCSES] for which permission evaluation depends only on the resources' attributes. The resource provider (i.e., data owner or encrypted) cannot specify the access policy except by choosing descriptive attributes for permissions. This means that there is no choice but to trust the key issuer. Such accountability for user secret keys provides fine-grained access without flexibility or scalability [BS]."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.5.2 | Sandboxing... 3.5.2 Sandboxing\n\nSandboxing refers to a security model where applications are run within a sandbox-a controlled environment that restricts what operations the applications can perform and that isolates them from other applications running on the same host."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 3. | POLICY | AND CONTROL STANDARDS | 3-6 |\n|------|----------------|-------------------------------------------------------------------------------------------------------|-----------|\n| | 3.1 | General | 3-6 |\n| | 3.2 | Assessing Security Safeguards | 3-6 |\n| | 3.3 | Establishing Control Standards | 3-6 |\n| | 3.4 | Require a Plan to Implement Controls | 3-7 |\n| | 3.5 | Establish Personnel Security Policies | 3-7 |\n| 4. | ALLOCATE | RESOURCES | 3-7 |\n| | 4.1 | General | 3-7 3-8 |\n| 5. | REPORT | ON SECURITY | |\n| | 5.1 | General | 3-8 |\n| Fig. | 1 | Responsibilities and Duties to Provide Security for Data Processing System .."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-83 Revision 1\n\n## Guide to Malware Incident Prevention and Handling for Desktops and Laptops\n\nMurugiah Souppaya Karen Scarfone\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-83 Revision 1\n\n## Guide to Malware Incident Prevention and Handling for Desktops and Laptops\n\nMurugiah Souppaya Computer Security Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nJuly 2013\n\n\n\nU.S. Department of Commerce\n\n## Cameron F. Kerry, Acting Secretary\n\nNational Institute of Standards and Technology Patrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Management Act (FISMA), Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 7)"}, {"role": "assistant", "content": "171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements.\n|\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |\n\n\n\nView more FAQs here. If you still have a question after reviewing all our FAQs , send your question to: sec-cert@nist.gov. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n\n\n## Additional Resources\n\n## Online Introductory Courses Available for the NIST SP 800-53 Series\n\n\n\nSP 800-171 requirements are focused on protecting confidentiality and are based on a subset of controls found in SP 800-53, which is a catalog of security and privacy controls for systems and organizations. With that in mind, it is important to have a basic understanding of the SP 800-53 series. To assist, NIST has released three self-guided online introductory courses to provide a high-level overview of foundational security and privacy risk management concepts. The online introductory courses are between 45-60 minutes, are available at no cost, and registration is not required. Access the courses. ## Roles of Different Federal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nIn working with the Office of Management and Budget to develop standards and guidelines required by FISMA, NIST consults with federal agencies; state, local, and tribal governments; and private sector organizations to improve information security and privacy, avoid unnecessary and costly duplication of effort, and help ensure that its publications are complementary with the standards and guidelines used for the protection of national security systems. In addition to a comprehensive and transparent public review and comment process, NIST is engaged in a collaborative partnership with the Office of Management and Budget, Office of the Director of National Intelligence, Department of Defense, Committee on National Security Systems, Federal CIO Council, and Federal Privacy Council to establish a Risk Management Framework (RMF) for information security and privacy for the Federal Government. This common foundation provides the Federal Government and their contractors with cost-effective, flexible, and consistent ways to manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. The framework provides a basis for the reciprocal acceptance of security and privacy control assessment evidence and authorization decisions and facilitates information sharing and collaboration. NIST continues to work with public and private sector entities to establish mappings and relationships between the standards and guidelines developed by NIST and those developed by other organizations. NIST anticipates using these mappings and the gaps they identify to improve the control catalog. | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n| EXECUTIVE SUMMARY......................................................................................................... iii | EXECUTIVE SUMMARY......................................................................................................... iii | EXECUTIVE SUMMARY......................................................................................................... iii |\n|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|\n| 1 INTRODUCTION................................................................................................................. | 1 INTRODUCTION................................................................................................................. | 1 |\n| 2 REPORTING CONVENTIONS.......................................................................................... | 2 REPORTING CONVENTIONS.......................................................................................... | 2 |\n| 3 SECURITY AWARENESS APPROACHES..................................................................... | 3 SECURITY AWARENESS APPROACHES....................................................................."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n## Guidelines for the Use of PIV Credentials in Facility Access\n\n## Guidelines for the Use of PIV Credentials in Facility Access\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n| Focus Group Design...................................................................................................\n| 3 |\n| 2.1.2 | Focus Group Recruitment........................................................................................... | 3 |\n| 2.1.3 | Focus Group Data Collection..................................................................................... | 3 |\n| 2.1.4 | Focus Group Data Analysis........................................................................................ | 4 |\n| 2.2 SURVEY METHODOLOGY ..................................................................................................... 4 | 2.2 SURVEY METHODOLOGY ..................................................................................................... 4 | 2.2 SURVEY METHODOLOGY ....................................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 3)"}, {"role": "assistant", "content": "n activities; provides scientific and technological advisory services and assistance to Federal agencies; and provides the technical foundation for computer-related policies of the Federal Government.\nThe Institute consists of the following centers:\n\nProgramming Science and Technology - Computer Systems Engineering. 'Headquarters and Laboratories at Gaithersburg, MD, unless otherwise noted;\n\nmailing address Washington, DC 20234. ^Some divisions within the center are located at Boulder, CO 80303. f). ## COMPUTER SCIENCE & TECHNOLOGY:\n\n## Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls NATIOIVAX. Proceedings of the NBS Invitational Workshop held at Miami Beach, Florida, November 28-30, 1978\n\nEditor:\n\nZella G. Ruthberg\n\nGeneral Co-Chairpersons:\n\nRobert G. McKenzie\n\nGeneral Accounting Office Washington, DC 20548\n\nSession Chairpersons:\n\nDonald L. Scantiebury Richard D. Webb Richard J. Guiitinan William H. Murray Jerry FitzGerald Theodore M. P. Lee Gerald E. Short Hart Will\n\n\n\n\n\nU.S. DEPARTMENT OF COMMERCE, Philip M. Klutznick, Secretary\n\nLuther H. Hodges, Jr., Deputy Secretary\n\nJordan J. Baruch, Assistant Secretary for Productivity, Technology, and Innovation\n\nNATIONAL BUREAU OF STANDARDS, Ernest Ambler, Director\n\nIssued April 1980\n\nBUEBAtJ OP BTAIfDAJtDS LIBBAST\n\nAPR 25 1980\n\nribi acc,\n\n~Ci^\n\nno. 6c>C) ' 5 7\n\n/no\n\n6. ^\n\nZella G. Ruthberg\n\nInstitute for Computer Sciences and Technology National Bureau of Standards Washington, DC 20234\n\n## Reports on Computer Science and Technology\n\nThe National Bureau of Standards has a special responsibility within the Federal Government for computer science and technology activities."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\ninks to malicious websites or to websites infected with malware. They centralize control, visibility, and reporting across many locations and types of users. They are not a replacement for WAFs,\n\n- a.\nVirtualized server-based approach: This approach is only applicable to networks that contain virtualized servers since it is implemented in the hypervisor. There are two possible mechanisms:\n1. Using virtual firewalls inside a hypervisor to isolate traffic destined for different VMs inside the hypervisor\n2. Using encapsulation techniques to create overlays (e.g., Virtual Extensible LAN ( VXLAN)) that run on top of an underlying network that consists of IP addresses designations; access control policies are enforced on the hypervisor itself outside of the workload (application or microservice)\n- b. Host-based microsegmentation: Alternatively (or additionally), host-based microsegmentation can be implemented using software agents on the endpoint artifacts (e.g., servers). It leverages native firewall functionality built into the host. Software agents can overlay a software-defined segmented network across data centers, cloud, bare metal, and hybrid environments. The agent provides context awareness and visibility for each workload and enables the definition and enforcement of fine-grained policies."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 4)"}, {"role": "assistant", "content": "on, DC 20234\n\n## Reports on Computer Science and Technology\n\nThe National Bureau of Standards has a special responsibility within the Federal Government for computer science and technology activities.\nThe programs of the NBS Institute for Computer Sciences and Technology are designed to provide ADP standards, guidelines, and technical advisory services to improve the effectiveness of computer utilization in the Federal sector, and to perform appropriate research and development efforts as foundation for such activities and programs. This publication series will report these NBS efforts to the Federal computer community as well as to interested specialists in the academic and private sectors. Those wishing to receive notices of publications in this series should complete and return the form at the end of this publicaton. ## National Bureau of Standards Special Publication 500-57\n\nNat. Bur. Stand. (U.S.), Spec. Publ. 500-57, 2 lOpages (Apr. 1980) CODEN: XNBSAV\n\nLibrary of Congress Catalog Card Number: 80-600034\n\n## U.S. GOVERNMENT PRINTING OFFICE\n\nWASHINGTON: 1980\n\n(Add 25 percent additional for other than U.S. mailing)\n\nThe use of computers by Government and private organizations for the storage and manipulation of records of all kinds has continued to Increase at a rapid rate in the three years since the first NBS-sponsored/ GAO-supported Invitational workshop on audit of computer security in March of 1977. The needs of the Individual as well as Government and private organizations for the security of sensitive data and its processing -Including accuracy, reliability, timeliness, and confidentiality -have therefore continued to remain a major concern to the public at large during this time Interval. In response to this need. Government laws and regulations in this arena have continued to grow and place legal requirements on computer systems."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Personnel Security?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nDocument maintenance requirements for the IoT device, such as: a. Cybersecurity maintenance expectations and associated instructions or procedures for the customer (e.g., account management, local and/or remote maintenance activities, and vulnerability/patch management plan) b. When maintenance will be performed by supporting parties that will need access (remote or onsite) to customer's IoT devices and their information security contract requirements c. Cybersecurity considerations of the maintenance process (e.g., how does customer data unrelated to the maintenance process remain confidential even to maintainers) | • Documentation of cybersecurity information enables better understanding of the potential risks related to the IoT device, which can inform customers and others in the IoT device ecosystem and guide on- going risk mitigation support. • Documentation helps personnel with the responsibility of securing IoT devices within the system understand the implementation and operation of controls and prevent misuse and compromise by unauthorized entities. • Documentation may be used to supply information about and support the management of supply chain risk, incident response, and other critical cybersecurity functions. | ( see above) |"}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n3 OMB Memorandum [M-05-24] and credentialing guidance issued the Office of Personnel Management (OPM) clarifies the eligibility requirements for a PIV Card.\n\nFigure 5-3 depicts a security posture of an FSL I or II campus. It includes one or more Controlled areas that are available to authorized personnel. Since an FSL I or II campus can be considered a low-risk area, a PACS may or may not be maintained to preclude unauthorized entries. When PACS is maintained, SOME confidence in the identity of the cardholder should be achieved. Implementation of PIV authentication mechanisms for Controlled areas would be an appropriate countermeasure for security. PKI-CAK, SYM-CAK, and BIO are the three recommended authentication mechanisms in this environment. Note that these authentication mechanisms validate 'something you have' or 'something you are' (one-factor authentication).\n\nIn addition to the use of a PIV credential for cardholder authentication during routine everyday use, the PIV credentials may also be used for access to federal facilities and federally controlled areas internal to disaster response and recovery incident scenes. Federal agencies should consider access for personnel from agencies with responsibilities under the National Response Framework, National Incident Management System, National Infrastructure Protection Plan, and the National Continuity Policy Implementation Plan when identifying and categorizing PACS perimeters as protecting Controlled, Limited, and Exclusion areas. Subsequently, agencies should apply appropriate (in accordance with Table 4-3) PIV authentication mechanisms to the areas to ensure that incident management personnel, emergency response providers, and other personnel (including temporary personnel) and resources likely needed to respond to a natural"}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 2)"}, {"role": "assistant", "content": "other than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 7)"}, {"role": "assistant", "content": "2\n\n23\n\n23\n\n24\n\niii\n\n\fNIST SP 800-63A-4\nJuly 2025\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\n3.7. Additional Requirements for Federal Agencies\n\n. . . . . . . . . . . . . . 3.8. 3.9.\nRequirements for Confirmation Codes . . . . . . . . . . . . . . . . . . . Requirements for Continuation Codes . . . . . . . . . . . . . . . . . . . 3.10. Requirements for Notifications of Identity Proofing . . . . . . . . . . . . 3.11. Requirements for the Use of Biometrics . . . . . . . . . . . . . . . . . . 3.12. Requirements for Visual Facial Image Comparison . . . . . . . . . . . . 3.13. Requirements for the Validation of Physical Evidence . . . . . . . . . . . 3.14. Digital Injection Prevention and Forged Media Detection . . . . . . . . . 3.15. Exception and Error Handling . . . . . . . . . . . . . . . . . . . . . . . 3.15.1. Requirements for Trusted Referees . . . . . . . . . . . . . . . . 3.15.2. Uses of Trusted Referees . . . . . . . . . . . . . . . . . . . . . . 3.15.3. Requirements for Applicant References . . . . . . . . . . . . . . 3.15.4. Uses of Applicant References\n\n. . . . . . . . . . . . . . . . . . . 3.15.5. Establishing Applicant Reference Relationships . . . . . . . . . . 3.15.6. Requirements for Interacting With Minors\n\n. . . . . . . . . . . . 3.16. Elevating Subscriber IALs . . . . . . . . . . . . . . . . . . . . . . . . . . 4. Identity Assurance Level Requirements . . . . . . . . . . . . . . . . . . . . . 4.1. Identity Assurance Level 1 Requirements . . . . . . . . . . . . . . . . . 4.1.1. Proofing Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.2. Evidence Collection . . . . . . . . . . . . . . . . . . . . . . . . 4.1.3. Attribute Collection . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4. Evidence Validation . . . . . . . . . . . . . . . . . . . . . . . . 4.1.5. Attribute Validation . . . . . . . . . . . . . . . . . . . . . . . . 4.1.6. Verification Requirements . . . . . . . . . . . . . . . . . . . . . 4.1.7."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . .\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.1. Truncation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.2. Nonce Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.3. AEAD Requirements.............................................................. | 19 |\n| 4.4. Security Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.1. Single-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.2. Multi-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.3. Nonce-Misuse Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 21 |\n| 5. Hash and eXtendable-Output Functions (XOFs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.1. Specification of Ascon-Hash256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.2. Specification of Ascon-XOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 25 |\n| 5.3. Specification of Ascon-CXOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 28 |\n| 5.4. Streaming API for XOF............................................................ | 30 |\n| 5.5. Security Strengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n+ Enhanced trust. PIV Cards are issued in accordance with standardized, audited processes, which exceeds the level for low- and moderate-impact legacy applications, and equals best practice reached for high-impact applications. + Resistance to misuse and cloning. Electronic validation of the PIV Card, using digital signatures, makes it tamper-resistant. Cryptographic challenge/response protocols make the PIV Card counterfeit-resistant. Biometric authentication makes the PIV Card non-transferable. + Status and revocation. PIV Card Issuer process assurance will extend beyond the issuance action to PIV Card validation and revocation services (see Section 4.4). These services are required elements of the PIV infrastructure, and will be implemented, monitored, and audited with the same care as the PIV issuance process. + Standard identity infrastructure. Application developers will assume, as a default, that registration and authentication will use a PIV Card identity, reducing\n\n| Contact Reader | A smart card reader that communicates with the integrated circuit chip in a smart card using electrical signals on wires touching the smart card's contact pad. The PIV contact interface is standardized by International Organization of Standards / International Electrotechnical Commission (ISO/IEC) 7816-3 [ISO/IEC7816]."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 7)"}, {"role": "assistant", "content": "Just as preventive maintenance on corporate fleet vehicles can help avoid costly breakdowns, patching should be viewed as a normal and necessary part of reliably achieving the organization's missions.\nIf an organization needs a particular technology to support its mission, it also needs to maintain that technology throughout its life cycle - and that includes patching. Leadership at all levels of the organization, business/mission owners, and security/technology management teams should jointly create an enterprise patch management strategy that simplifies and operationalizes patching while also improving its reduction of risk. This will strengthen organizational resiliency to active threats and minimize business and mission impacts. This publication provides recommendations for enterprise patch management planning. ## Table of Contents\n\n| Executive Summary..................................................................................................... | Executive Summary..................................................................................................... | Executive Summary....................................................................................................."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nNIST's Cybersecurity for IoT program has defined a set of device cybersecurity capabilities that device manufacturers should consider integrating into their IoT devices and that consumers should consider enabling/configuring in those devices. Device cybersecurity capabilities are cybersecurity features or functions that IoT devices or other system components (e.g., a gateway, proxy, IoT platform) provide through technical means (e.g., device hardware and software). Many IoT devices have limited processing and data storage capabilities and may not be able to provide these device cybersecurity capabilities on their own; instead, they may rely on other system components to provide these technical capabilities on their behalf. Nontechnical supporting capabilities are actions that a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device. Examples of nontechnical support include providing information about software updates, instructions for configuration settings, and supply chain information."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos...............................................24"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nNIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors. They are practical, user-friendly guides that facilitate the adoption of standards-based approaches to cybersecurity. They show members of the information security community how to implement example solutions that help them align with relevant standards and best practices, and provide users with the materials lists, configuration files, and other information they need to implement a similar approach. Ransomware, destructive malware, insider threats, and even honest mistakes present an ongoing threat to organizations that manage data in various forms. Database records and structure, system files, configurations, user files, application code, and customer data are all potential targets of data corruption and destruction."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n17 The Audit and Accountability, Maintenance, Media Protection, and Physical Protection families do not contain enhanced security requirements at this time.\n\n## 3.8 MEDIA PROTECTION"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| 1. The ability to change the device's software configuration settings 2. The ability to restrict configuration changes to authorized entities only 3. The ability for authorized entities to restore the device to a secure configuration defined by an authorized entity | • This capability supports vulnerability management, access management, data protection, and incident detection. • An authorized entity may want to alter a device's configuration for a variety of reasons, including cybersecurity, interoperability, privacy, and usability. Without a device configuration capability, an authorized entity cannot customize a device to meet its needs, integrate the device into the authorized entity's environment, etc. • Most cybersecurity capabilities are at least somewhat dependent on the presence of a device configuration capability. • Unauthorized entities may want to change a device's configuration for many reasons, such as gaining unauthorized access, causing the device to malfunction, or secretly monitoring the device's environment. • The ability to restore a secure configuration for a device is helpful when the current configuration contains errors, has been damaged or corrupted, or is otherwise no longer thought to be trustworthy. | • BITAG : 7.1 • CSA : 22 • ENISA : GP-TM-06 • IEC : CR 7.4, CR 7.6 • IIC : 7.3, 7.6, 8.10, 11.5 • IoTSF : 2.4.8.17, 2.4.15 • ISOC/OTA : 26 • OCF: 5.3.3, 8.2, 12, 13.3.1 • PSA : C2.3, R6.1, R7.1 |"}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nAssessing the SP 800-53controls of the system itself should ideally have a continual assessment component utilizing a monitoring program [13]. Frequent automated checks or scans should be conducted to detect changes in the system (as part of the MONITOR step below). Logging data should be used to detect possible malicious behavior that requires further investigations or remediation. This assessment may also include active processes such as red team testing of the system as input into the assessments."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | Documentation : The ability for the manufacturer and/or the manufacturer's supporting entity, to create, gather, and store information relevant to cybersecurity of the IoT device prior to customer purchase, and throughout the development of a device and its subsequent lifecycle."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "oval of the appropriate federal officials exercising policy authority over such systems. This\nguideline is consistent with the requirements of the Office of Management and Budget (OMB)\nCircular A-130.\nNothing in this publication should be taken to contradict the standards and guidelines made\nmandatory and binding on federal agencies by the Secretary of Commerce under statutory\nauthority. Nor should these guidelines be interpreted as altering or superseding the existing\nauthorities of the Secretary of Commerce, OMB Director, or any other federal official. This\npublication may be used by nongovernmental organizations on a voluntary basis and is not\nsubject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-53, Revision 5\nNatl. Inst. Stand. Technol. Spec. Publ. 800-53, Rev. 5, 492 pages (September 2020)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53r5\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe\nan experimental procedure or concept adequately. Such identification is not intended to imply\nrecommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or\nequipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by\nNIST in accordance with its assigned statutory responsibilities. The information in this publication,\nincluding concepts, practices, and methodologies may be used by federal agencies even before the\ncompletion of such companion publications. Thus, until each publication is completed, current\nrequirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | Documentation : The ability for the manufacturer and/or the manufacturer's supporting entity, to create, gather, and store information relevant to cybersecurity of the IoT device prior to customer purchase, and throughout the development of a device and its subsequent lifecycle."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| Data Protection : The IoT device can protect the data it stores and transmits from unauthorized access and modification."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication NIST SP 800-140Br1\n\n## Cryptographic Module Validation Program (CMVP) Security Policy Requirements:\n\nCMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B\n\nDavid Hawes Alexander Calis Roy Crombie\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-140Br1\n\n\n\n## NIST Special Publication NIST SP 800-140Br1\n\n## Cryptographic Module Validation Program (CMVP) Security Policy Requirements:\n\nCMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B\n\nDavid Hawes Alexander Calis\n\nComputer Security Division Information Technology Laboratory\n\nRoy Crombie Canadian Centre for Cyber Security https://doi.org/10.6028/NIST.SP.800-140Br1\n\nNovember 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\n## 3.3. Access Control Model Implementations\n\nFor data at rest, some NoSQL databases may allow users backdoor access to other users' data due to poor logging and log analysis methods [ZA]. In some systems, authorization is applied at a per-database level using a role-based approach, limiting certain roles to specific privileges at different database levels. In contrast, some systems may provide no authorization by default, allowing any action by any user [CJ]. In such cases, an external security enforcement mechanism is essential. For example, some systems utilize metadata and provide management functions based on the database structure implementing access control operations with authorization principles. This allows different applications to implement their own access control.\n\n## 4.6. Audit"}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n..................................................................... | 5.4 Specific Details ...........................................................................................................\n| 29 |\n|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|\n| 6 | Functional Demonstrations...............................................................30 | Functional Demonstrations...............................................................30 | Functional Demonstrations...............................................................30 | |\n| | 6.1 | Usage Scenarios Supported ....................................................................................... | Usage Scenarios Supported ......................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 6)"}, {"role": "assistant", "content": "& Company | U.S. Bank Corporation |\n\n| Technology Partner/Collaborator | Build Involvement |\n|-----------------------------------|---------------------|\n| Mira Security, Inc.\n| |\n\n## DOCUMENT CONVENTIONS\n\nThe terms 'shall' and 'shall not' indicate requirements to be followed strictly to conform to the publica�on and from which no devia�on is permited. The terms 'should' and 'should not' indicate that among several possibili�es, one is recommended as par�cularly suitable without men�oning or excluding others, or that a certain course of ac�on is preferred but not necessarily required, or that (in the nega�ve form) a certain possibility or course of ac�on is discouraged but not prohibited. The terms 'may' and 'need not' indicate a course of ac�on permissible within the limits of the publica�on. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical, or causal. NOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents a re not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Maintenance?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/171/r3/final, including related content, potential updates, and document history. | Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "tise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D.\nThe controls described assist organizations in defining the controls needed to satisfy minimum assurance requirements. Where additional assurance is desired to achieve risk management objectives, Table E-4 provides additional security controls and control enhancements to achieve enhanced assurance. Implementers should note that designation of assurance-related controls is not intended to imply a greater level of importance for such controls. Achieving adequate security for organizational information systems requires the correct combination of both functionality- and assurance-related security controls. ## 6 Security Controls\n\nAppendix F, the Security Control Catalog, provides a comprehensive range of countermeasures for organizations and information systems. The security controls are designed to be technologyneutral such that the focus is on the fundamental countermeasures needed to protect organizational information during processing, storage, or transmission. SP 800-53 Rev. 4, therefore, does not provide guidance on the application of security controls to specific technologies, environments of operation, or missions/business functions. These specific areas may be addressed using overlays (see below). Control enhancements are included with many security controls and are selected in order to increase the strength of the base control. Control enhancements are intended to be implemented only in conjunction with implementation of the base control. Some security controls and control enhancements include one or more assignment and selection statements. These are variable 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n## Conformance Testing\n\nConformance testing for implementations of this Recommendation will be conducted within the framework of the Cryptographic Algorithm Validation Program (CAVP) and the Cryptographic Module Validation Program (CMVP). The requirements of this Recommendation are indicated by the word 'shall.' Some of these requirements may be out-of-scope for CAVP or CMVP validation testing, and thus are the responsibility of entities using, implementing, installing or configuring applications that incorporate this Recommendation. | | 5.6.1.1.3 Key-Pair Generation Using Extra Random Bits .................. | 27 |\n|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------|\n| | 5.6.1.1.4 Key-Pair Generation by Testing Candidates........................ | 29 |\n| 5.6.1.2 | ECC Key-Pair Generation................................................................... | 30 |\n| | 5.6.1.2.1 Key Pair Generation Using Extra Random Bits .................. | 30 |\n| | 5.6.1.2.2 Key Pair Generation by Testing Candidates........................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nContinuous integration (CI) pipelines [22] and tests of scientific code on HPC platforms have recently become commonplace. Industry-standard identification of software weaknesses and the publication of Common Vulnerabilities and Exposures (CVEs) [23] is not routine, but the identification and remediation of performance regressions is generally a higher priority within the user community. There is a value-per-cycle trade-off for CI tests since cheaper cycles on commodity hardware may not expose bugs on much more expensive HPC resources. Complex test suites will eat into user allocations, and users and staff prefer that only a cardinal set of smoke tests run within user-developed testing pipelines on HPC systems.\n\n- Conduct tests to measure the performance penalty of security tools, which can be benchmarked to determine whether they are acceptable. Testing and measurement would also encourage more performance-aware tool design.\n- Incorporate security requirements in the initial HPC design rather than as an afterthought. For instance, independent add-on security tools tend to have more impact on performance than native security measures that come with the HPC software stack. Key management architecture plays an important role in HPC security but requires careful performance analysis.\n- Avoid 'one size fits all' security. Differentiate the types of nodes in the HPC system, and apply appropriate security rules and controls to different node types. For instance, classify the nodes in HPC systems into three categories: external nodes, internal nodes, and backend nodes. Apply individual security controls to each node category. Such a differentiation also mitigates performance impacts."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\n## 5.1 Integrity Techniques\n\n- Integrity Techniques - Specify the approved integrity techniques or EDC [error detection code] employed\n\n- Initiate on Demand - Specify how the operator can initiate the integrity test on demand"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\novides a gap analysis of SCAP v1 and an overview of how SCAP v2 will address these gaps; describes the SCAP 2.0 architecture; and provides a plan for completing the work necessary to finalize SCAP v2.\n| 1 | Introduction ............................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| 2 Gaps in SCAP | v1....................................................................................................2 |\n| 3 SCAP | v2..................................................................................................................3 |\n| 3.1 Design Goals for SCAP v2.............................................................................. | 3 |\n| 3.2 The SCAP v2 | Architecture.............................................................................. 4 |\n| 3.3 Adoption of International Standards | in SCAP v2 ............................................"}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nThe non-technical supporting capabilities in Table 1 describe the intended recipient of the value of the capability as the customer (i.e., those with whom the communications take place). This stems from an assumption that the customer of an IoT device will have cybersecurity needs, goals, and responsibilities related to the IoT device. For a specific customer or use case, there may be other individuals or entities from the IoT device ecosystem who may be part of that communication. For example, an enterprise customer may have several supporting contractors or entities as well as employees to whom the information described in the table may need to be communicated. Alternatively, a building owner incorporating IoT devices will need to pass information to building tenants using those IoT devices. In this case, it is also noteworthy how future owners/users of the IoT devices (i.e., future tenants) may not be considered customers in the traditional sense. Finally, in addition to the customer, for some sectors, there may be robust third-party ecosystem entities (e.g., product reviewers and assessors, retailers, and vendors) that may use non-technical supporting capabilities to help improve the cybersecurity for the sector broadly. - The first column describes the non-technical supporting capability. - The second column provides a numbered list of common actions within that supporting capability. These are actions that an organization implementing the non-technical supporting capability often (but not always) would use to achieve the capability. It is important to understand that the actions are not intended to be comprehensive nor are they presented in any particular order. 3\n- The third column explains the rationale for needing the non-technical support capability. - The last column lists IoT reference examples that indicate existing sources of IoT device cybersecurity guidance specifying a similar or related capability."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nent some incidents, prepare to handle incidents that do occur, reduce the impact of those incidents, and improve incident response and cybersecurity risk management practices based on lessons learned.\nDetect, Respond, and Recover help organizations discover, manage, prioritize, contain, eradicate, and recover from cybersecurity incidents, as well as perform incident reporting, notification, and other incident-related communications."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nDevice cybersecurity capabilities are cybersecurity features or functions that computing devices provide through their own technical means (i.e., device hardware and software). This publication defines an Internet of Things (IoT) device cybersecurity capability core baseline, which is a set of device capabilities generally needed to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 6)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . 4. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n. . . . . . . . . . . . Appendix A. List of Symbols, Abbreviations, and Acronyms\n\n. . . . . . . . . . . . . . . 1\n\n2\n\n3\n\n3\n\n3\n\n4\n\n4\n\n5\n\n5\n\n6\n\n6\n\n7\n\n7\n\n8\n\n8\n\n9\n\n9\n\n10\n\n10\n\n11\n\n11\n\n11\n\n12\n\n13\n\n14\n\n15\n\n21\n\nii\n\n\fList of Tables\n\nTable 1. Timeline of the Additional Digital Signatures for the NIST PQC Standardiza-\ntion Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. First-round digital signature candidates organized by category, with the can-\ndidates selected to advance to the second round bolded and in blue. The\nstarred signature schemes MIRA and MiRitH merged to form a new candi-\ndate Mirath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. Second-round digital signature candidates organized by category . . . . . . . 2\n\n3\n6\n\niii\n\n\fNIST IR 8528\nOctober 2024\n\nSupplemental Content\n\nAdditional Digital Signatures\nFirst Round Status Report\n\nThe NIST Additional Digital Signatures for PQC Standardization Process webpage is available at\nhttps://csrc.nist.gov/Projects/pqc-dig-sig/standardization. Acknowledgments\n\nNIST would like to thank all of the candidate submission teams who developed, designed, and an-\nalyzed the post-quantum public-key digital signature algorithms and prepared detailed submission\npackages. NIST is also grateful for the efforts of those in the cryptographic community who provided security,\nimplementation, and performance analyses of the candidate algorithms during the first round. NIST\nwould not be able to select additional post-quantum digital signature algorithms for standardization\nwithout the combined efforts of these individuals and the algorithm submitters."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\n2 | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology..........................................................................................................\n2 |\n| Study | Study | 2 |\n| 3.2. Data Collection............................................................................................................ | 3.2. Data Collection............................................................................................................ | ................................................................................................................. 3 |\n| 3.3. Data Analysis | 3.3. Data Analysis | .............................................................................................................. 3 |\n| | Participant and Organization Demographics..............................................................."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\n- I. All communication is secured regardless of network location. In zero trust, the network is always considered contested. A ZTA should be designed with the assumption that an attacker is present on the network and could observe/modify communications. Appropriate safeguards should be in place to protect the confidentiality and integrity of data in transit. If a resource cannot provide this functionality natively, a separate PEP component may be necessary.\n- II. Access to individual enterprise resources is granted on a per -session basis. In an ideal zero trust architecture, every unique operation would undergo authentication and authorization before the operation is performed. For example, a delete operation following a read operation to a database should trigger an additional authentication and authorization check. This level of granularity may not always possible and other mitigating solutions such as logging and backups, may be needed to detect and recover from unauthorized operations. Enterprise administrators will need to plan how to enforce fine grain access policies on individual resources. If the security tools used by\n\nthe enterprise do not allow this, other solutions such as logging, versioning tools, or backups may help achieve the desired access control outcome and manage this risk.\n\nAssessing the SP 800-53controls of the system itself should ideally have a continual assessment component utilizing a monitoring program [13]. Frequent automated checks or scans should be conducted to detect changes in the system (as part of the MONITOR step below). Logging data should be used to detect possible malicious behavior that requires further investigations or remediation. This assessment may also include active processes such as red team testing of the system as input into the assessments."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 4)"}, {"role": "assistant", "content": "pment of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems.\nThe Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThe protection of Controlled Unclassified Information (CUI) resident in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides federal agencies with recommended enhanced security requirements for protecting the confidentiality of CUI: (1) when the information is resident in nonfederal systems and organizations; (2) when the nonfederal organization is not collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency; and (3) where there are no specific safeguarding requirements for protecting the confidentiality of CUI prescribed by the authorizing law, regulation, or government-wide policy for the CUI category listed in the CUI Registry. The enhanced requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide security protection for such components when the designated CUI is associated with a critical program or high value asset. The enhanced requirements supplement the basic and derived security requirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Incident Response?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nosed of. - d. Vulnerability management options (e.g., configuration and patch management and anti-malware) available for the IoT product or its product components that could be used by customers. - e.\nAdditional information customers can use to make informed purchasing decisions about the security of the IoT product (e.g., the duration and scope of product support via software upgrades and patches)."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.6. PERK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.6. PERK"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nAbstract -Over the past decade, there has been an explosion in the deployment of implantable medical devices (IMDs) to facilitate the management and treatment of a wide variety of human health conditions. While functionality and patient safety requirements have driven new generation IMDs to be increasingly accessible through wireless communication channels, these changes cause significant concern in terms of increased risk from cyber threats whether malicious or unintentional. This paper investigates the risks associated with such devices from the cyber environment and proposes approaches to support decisions regarding the integration of adequate security and privacy measures to mitigate these risks. Deployment rates for implantable medical devices (IMDs) have skyrocketed over the past decade. Devices such as pacemakers, cardiac defibrillators, heart monitors, cochlear implants, insulin pumps, infusion pumps and other similar devices are routinely used to monitor and treat a plethora of medical conditions. These IMDs have been increasingly accessible through wireless channels to support functions such as emergency extraction of patient health history, remote monitoring of health status, firmware updates and local as well as remote therapy reprogramming. As with all things connected to the cyber world, there are known and unknown threats lurking that threaten the reliability and safety of these devices as well the privacy of patients who depends on them. Halperin et al have shown that a recent (2003) model of implantable cardioverter defibrillator (ICD), designed to com- municate wirelessly with an external programmer in the 175 kHz frequency range, is vulnerable to several radio-based attacks that threaten patient safety and privacy [2]. Several other research papers have pointed out similar vulnerabilities to cyber threats and possible mitigation mechanisms [3, 4, 5, 6]."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 9)"}, {"role": "assistant", "content": "...........12 |\n| 3. FORENSIC TOOLS.............................................................................................................15 | 3.\nFORENSIC TOOLS.............................................................................................................15 | |\n| 3.1 | MOBILE DEVICE TOOL CLASSIFICATION SYSTEM .......................................................... | 15 |\n| 3.2 | UICCTOOLS.................................................................................................................... | 23 |\n| 3.3 | OBSTRUCTED DEVICES | ....................................................................................................24 |\n| 3.4 | FORENSIC TOOL CAPABILITIES ........................................................................................"}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "sions. This documentation is essential when examining the security considerations for organizational information systems with respect to the potential impact on an organization's mission and business.\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3. Figure 3: Security Control Selection Process\n\n\n\n## 5 Assurance\n\nAppendix E in SP 800-53 Revision 4 provides an update to guidance regarding security assurance. This section outlines methods for agencies to establish measures of confidence that the implemented security controls provide the security capability required to protect critical missions and business operations. The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Machine Learning for Access Control Policy Verification:\n\nMachine learning has been used for device control, system analysis, and business forecasting. However, the use of ML for software testing is in the early stages [AWCS, CAT5]. In particular, ML applications for model proof are still elusive and have yet to be explored. ML classification allows for the generation or prediction of target classes for new input data using some sample training data produced by running the system instead of comprehensive input data. For access control policy verification, the training data is assigned attributes' values of policy rules, and the target for classification is access permissions (e.g., grant and deny) assigned to rules. The data is consumed by an ML classification algorithm to generate a classification model . Querying the accuracy of training data against the model allows for the detection of inconsistencies, indicating faults found among policy rules. In addition, to verify new or updated policy rules, they need to be contained in test data for additional accuracy analysis on test data. Applying the RFC algorithm to policy verification requires the preparation of a data table that contains classification-required training and test data transferred from specific access control policy rules. In the table, each column contains an attribute, action, or permission value. Each row represents a policy rule, and the access permission is based on the attribute and action values in the row. For verification of a policy that only has binary attribute values, there is no need for test data because instead of a general purpose of prediction from a classification algorithm, the goal is to analyze the accuracy (i.e., correctness) of rules specified in training data . Hence, in order to include all policy rules in training data, the ratio of test set data to training data must be kept to a minimum. However, the algorithm may require no empty test data."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 5)"}, {"role": "assistant", "content": ", and academic organizations. ## Supplemental Content\n\nNIST has established an Incident Response project page that hosts links to resources with additional information on incident response activities.\nBy moving links from this document to a website, NIST can update and expand them as needed without having to release a new version of this publication. For more information on CSF 2.0 Community Profiles, see the Framework Resource Center. ## Audience\n\nThe target audience for this publication includes cybersecurity program leadership, cybersecurity personnel, and others who are responsible for preparing for, detecting, responding to, or recovering from cybersecurity incidents. This publication is intended for use by most organizations, regardless of sector, size, or other factors. ## Trademark Information\n\nAll registered trademarks belong to their respective organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice PL.L2-3.15.4 (NIST 3.15.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.15.4. 3.15.4."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.15.4", "cmmc_practice_id": "PL.L2-3.15.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nn Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562.\nhttps://doi.org/10.6028/NIST.IR.8562\n\n## Author ORCID iDs\n\nKaterina Megas: 0000-0002-2815-5448 Michael Fagan: 0000-0002-1861-2609 Barbara Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Abstract\n\nThis report summarizes the feedback received by the NIST Cybersecurity for the Internet of Things (IoT) program at the in-person and hybrid workshop on \"Updating Manufacturer Guidance for Securable Connected Product Development\" held in December 2024. The purpose of this workshop was to consider how to update Foundational Cybersecurity Activities for IoT Device Manufacturers (NIST Internal Report (IR) 8259) based on concepts in risk management, operational technology concerns, product end of life concerns and recent trends in IoT cybersecurity and privacy. Over time, the NIST volume of work has built upon the concepts introduced in NIST IR 8259,to add technical (NIST IR 8259A) and nontechnical (NIST IR 8259B) concepts to help manufacturers and customers consider the cybersecurity of IoT devices. The NIST IR 8259 series has been used to inform and develop subsequent publications that elaborate on IoT cybersecurity across sectors and use cases (e.g., federal agency uses cases reflected in NIST SP 800-213 and consumer use cases reflected in NIST IR 8425 and the U.S. Cyber Trust Mark). ## Keywords\n\ncybersecurity baseline; Internet of Things (IoT); IoT products; manufacturing; privacy; risk management; securable products; security requirements; software development; threat modelling. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nInformation technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .\nISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nINCLUDES UPDATES AS OF 1 1 -01 -2024; SEE APPENDIX K\n\nBoyens J, Smith A, Bartol N, Winkler K, Holbrook A, Fallon M (2022) Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-161r1-upd1, Includes updates as of Novem ber 1, 2024. https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/161/r1/upd1/final, including related content, potential updates, and document history."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 3)"}, {"role": "assistant", "content": "ards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology.\nITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nThis publication documents the consumer profile of NIST's Internet of Things (IoT) core baseline and identifies cybersecurity capabilities commonly needed for the consumer IoT sector (i.e., IoT products for home or personal use). It can also be a starting point for businesses to consider in the purchase of IoT products. The consumer profile was developed as part of NIST's response to Executive Order 14028 and was initially published in Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products . The consumer profile capabilities are phrased as cybersecurity outcomes that are intended to apply to the entire IoT product. This document also discusses the foundations for developing the recommended consumer profile and related considerations. NIST reviewed a landscape of relevant source documents to inform the consumer profile and engaged with stakeholders across a year-long effort to develop the recommendations. ## Keywords\n\nInternet of Things (IoT); consumer IoT; cybersecurity; IoT products; privacy; safety; securable products. ## Audience\n\nThe intended audience for this report consists of manufacturers of consumer products, especially product security officers, retailers and related integrators and technical support firms serving the consumer and business sectors, and testing and certification bodies interested in establishing baselines of IoT cybersecurity capabilities."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n|\n| Intel | HP Inc.\nElitebook 360 830 G5, Lenovo ThinkPad T480, Transparent Supply Chain Tools, Key Generation Facility, Cloud Based Storage, TSCVerify and AutoVerify software tools |\n| National Security Agency (NSA) | Host Integrity at Runtime and Start-Up (HIRS), Subject Matter Expertise |\n| Seagate Government Solutions | (3) 18TB Exos X18 hard drives, 2U12 Enclosure, Firmware Attestation API, Secure Device Authentication API |\n\nThe terms 'shall' and 'shall not' indicate requirements to be followed strictly to conform to the publication and from which no deviation is permitted. The terms 'should' and 'should not' indicate that among several possibilities, one is recommended as particularly suitable without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. The terms 'may' and 'need not' indicate a course of action permissible within the limits of the publication. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical, or causal."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| Technology Partner/Collaborator | Build Involvement |\n|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Eclypsium | Eclypsium Analytics Service, Eclypsium Device Scanner |\n| HP Inc. | (2) Elitebook 840 G7, HP Sure Start, HP Sure Recover, Sure Admin, HP Client Management Script Library (CMSL), HP Tamperlock |\n| Hewlett Packard Enterprise | Proliant DL360 Gen 10, Platform Certificate Verification Tool (PCVT) |\n| IBM | QRadar SIEM |\n| Intel | HP Inc."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nAlmost two-thirds (65%) of survey participants measure RBT effectiveness by using training completion rates, and just under half evaluate success via audit reports or evaluations (Figure 14). Less than half (46%) gauge effectiveness from informal employee feedback (e.g., inperson discussions, emails), and 34% use employee surveys to determine training success. Just under a quarter (24%) examine behaviors (e.g., security incident trends and incident reporting) as evidence that employees are applying what they have learned through RBT. 9% of participants do not attempt to measure the effectiveness of their RBT activities at all.\n\n- Training on specific tools required for employees to perform security-related job duties\n- Training for employees who have privileged access to applications or systems\n- Training for oversight roles such as information systems security officer (ISSO), information systems security manager (ISSM), or auditors\n- Training for employees who manage access and authorizations to applications and systems\n- Training on organizational policies and procedures related to security and privacy configurations, settings, controls, etc.\n- Cybersecurity for employees in leadership positions, such as 'Cybersecurity for Executives,' Cybersecurity for System Owners,' or 'Becoming A Chief Information System Officer'\n\n□ IT Program Auditor"}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nforma estricta antes de permitir el acceso . Se trata de un ciclo constante de acceso, escaneo y evaluación de amenazas, adaptación y reevaluación continua de la confianza en permanente comunicación.\nAsí, se espera que la empresa que implemente una ZTA cuente con una gestión de la identidad, credenciales y acceso (ICAM, por su nombre en inglés Identity, Credential, and Access Management) y sistemas establecidos de gestión de activos. Entre ellos, se incluye el uso de la autenticación multifactor (MFA, por su denominación en inglés multifactor authentication ) para el acceso a algunos o todos los recursos de la empresa. La supervisión continua con posibles reautenticación y reautorización se produce a lo largo de las transacciones de los usuarios, según lo definido y aplicado por la política (por ejemplo, basada en el tiempo, modificación o nuevo recurso solicitado, actividad anómala de sujeto detectada), la cual procura establecer un equilibrio entre la seguridad, la disponibilidad, la usabilidad y la rentabilidad. 7. La empresa recopila toda la información posible sobre el estado actual de los activos, la infraestructura de la red y las comunicaciones, y la utiliza para mejorar la postura de seguridad. Una empresa debe reunir y procesar los datos sobre la postura de seguridad de sus bienes, el tráfico de red y las solicitudes de acceso. Además, tomará cualquier información obtenida para mejorar la creación y la aplicación de las políticas. Estos datos también servirán como contexto para las solicitudes de acceso de los sujetos (consultar la sección 3.3.1)."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Vulnerabilities are discovered by a variety of sources. Developers of software may find security bugs in already deployed code. Security researchers and penetration testers may find vulnerabilities by scanning or manually testing software and accessible systems (following published rules of behavior). While identifying an issue, users of systems may stumble across a vulnerability. Malicious actors may seek out unknown or unpublished vulnerabilities and use them in malware. Evidence of these attacks may then be discovered and analyzed by security experts, resulting in an identified vulnerability being reported. Regardless of who finds these vulnerabilities, it is critical that they are reported so that the owners of vulnerable software and systems can resolve or identify ways to mitigate the reported vulnerabilities. In many cases, owners should issue advisories to notify users of any actions to be taken (e.g., patches to be installed) or of potential damage to systems (i.e., potential consequences of the vulnerability having existed). vulnerability is a severe or widespread issue, coordination with public relations may be needed to prepare for contact from news media. Organization planning should consider facilitating close working relationships and supporting customer service to handle and respond to security vulnerabilities."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| | 5.1.1 | Business Cycles as an Auditing Framework | 9-16 | |------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------| | | 5.1.2 | Accounting System Control Objectives | 9-16 | | | 5.1.3 | Cycle Control Objectives | 9-17 | | | 5.1.4 | Advantages of the Control Objectives Approach | 9-17 | | 5.2 | Transaction Flow | Transaction Flow | 9-22 | | 5.3 | An Approach Towards Using Control Objectives and Transaction | An Approach Towards Using Control Objectives and Transaction | 9-22 | | 5.4 | Additional Considerations | Additional Considerations | 9-23 | | 6."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST 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.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory\n(ITL) promotes the U.S. economy and public welfare by providing technical leadership for the\nNation’s measurement and standards infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT). ITL’s responsibilities include the development\nof management, administrative, technical, and physical standards and guidelines for the cost-\neffective security of other than national security-related information in federal information\nsystems. The Special Publication 800-series reports on ITL’s research, guidelines, and outreach\nefforts in information systems security and privacy and its collaborative activities with industry,\ngovernment, and academic organizations. CHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n```\ntitle: \"Limit SSHD to FIPS 140 Validated Ciphers\" discussion: | If SSHD is enabled, then it _MUST_ be configured to limit the ciphers to algorithms that are FIPS 140-validated. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets federal requirements. Operating systems utilizing encryption _MUST_ use FIPS-validated mechanisms for authenticating to cryptographic modules. NOTE: /etc/ssh/sshd_config will be automatically modified to its original state following any update or major upgrade to the operating system. check: | /usr/bin/grep -c \"^Ciphers aes256-ctr,aes192-ctr,aes128-ctr\" /etc/ssh/sshd_config result: integer: 1\n```\n\nOperating systems utilizing encryption \\_MUST\\_ use FIPS-validated mechanisms for authenticating to cryptographic modules."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice PL.L2-3.15.3 (NIST 3.15.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.15.3. 3.15.3. 3.15.3."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.15.3", "cmmc_practice_id": "PL.L2-3.15.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.1.1 ID. 3.1.1 | Technology Configurations... 3.1.1 Technology Configurations\n\n## 3."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos...............................................24"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.14. Digital Injection Prevention and Forged Media Detection . . . . . . . . .\n\n• Cryptographic verification of the source and integrity of digital evidence or\n\n2. Based on the results of its privacy risk assessment, the CSP SHALL document the\nmeasures it takes to maintain the disassociability, predictability, manageability,\nconfidentiality, integrity, and availability of any personal information it collects\nor processes.4 In determining such measures, the CSP SHOULD apply relevant\nguidance and standards, such as the NIST Privacy Framework [NIST-Privacy] and\nNIST SP 800-53 [SP800-53]."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nance. 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.\nThe 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nalleviate some of the stated impacts. For example, conduct scanning at write, and conduct subsequent batch scanning at read. Protection against ransomware attacks on HPC data is especially important.\nIt is recommended to conduct risk assessments of ransomware attacks, and plan and implement mechanisms to protect the HPC system from ransomware attacks, as applicable [48,40,40]. Protecting data integrity is vital to HPC security. Granular data access provides the best protection and is highly recommended when possible."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 6)"}, {"role": "assistant", "content": "nce Level 1 . . . . . . . . . . . . . . . . . . . . . 2.1.1. Permitted Authenticator Types\n\n. . . . . . . . . . . . . . . . . . 2.1.2. Authenticator and Verifier Requirements . . . . . . . . . . . . .\n2.1.3. Reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2. Authentication Assurance Level 2 . . . . . . . . . . . . . . . . . . . . . 2.2.1. Permitted Authenticator Types\n\n. . . . . . . . . . . . . . . . . . 2.2.2. Authenticator and Verifier Requirements . . . . . . . . . . . . . 2.2.3. Reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3. Authentication Assurance Level 3 . . . . . . . . . . . . . . . . . . . . . 2.3.1. Permitted Authenticator Types\n\n. . . . . . . . . . . . . . . . . . 2.3.2. Authenticator and Verifier Requirements . . . . . . . . . . . . . 2.3.3. Reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4. General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.1. Security Controls . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.2. Records Retention Policy . . . . . . . . . . . . . . . . . . . . . . 2.4.3. Privacy Requirements . . . . . . . . . . . . . . . . . . . . . . . 2.4.4. Redress Requirements . . . . . . . . . . . . . . . . . . . . . . . 2.5. Summary of Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3. Authenticator and Verifier Requirements . . . . . . . . . . . . . . . . . . . . 3.1. Requirements by Authenticator Type . . . . . . . . . . . . . . . . . . . 3.1.1. Passwords\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2. Look-Up Secrets . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3. Out-of-Band Devices . . . . . . . . . . . . . . . . . . . . . . . . 3.1.4. Single-Factor OTP . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5. Multi-Factor OTPs\n\n. . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does IoT Non-Technical Supporting Capability Core Baseline provide?"}, {"role": "assistant", "content": "## NISTIR 8259B\n\n## IoT Non-Technical Supporting Capability Core Baseline\n\nMichael Fagan Jeffrey Marron Kevin G. Brady, Jr. Barbara B. Cuthill Katerina N. Megas Rebecca Herold\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8259B\n\n\n\n## NISTIR 8259B\n\n## Internet of Things Non-Technical Supporting Capability Core Baseline\n\nMichael Fagan Jeffrey Marron Kevin G. Brady, Jr. Barbara B. Cuthill Katerina N. Megas\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nRebecca Herold\n\nThe Privacy Professor\n\nDes Moines, IA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259B\n\nAugust 2021\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259B 21 pages (August 2021)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259B\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nIn addition, there are administrative activities occurring throughout the software vulnerability management life cycle, such as updating documentation, audit logging, and generating actionable insights and reports as part of enterprise change management. Having robust change management policies and processes in place is a fundamental part of software vulnerability management."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n..................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5.\nTraceability of CE Operations.....................................................................................................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1. Information Decisions in the System Life Cycle..........................................................................20 |\n| 4.3.2. Determination of Security Categorization..................................................................................21 |\n| 4.3.3. Reuse of Media...........................................................................................................................22 |\n| 4.3.4. Control of Media ........................................................................................................................22 |\n| 4.3.5. Data Protection Level .................................................................................................................23 |\n| 4.3.6. Sanitization and Disposal Decision.............................................................................................23 |"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nThe macOS Security Compliance Project (mSCP) provides resources that system administrators, security professionals, security policy authors, information security officers, and auditors can leverage to secure and assess macOS desktop and laptop system security in an automated way. This publication introduces the mSCP and gives an overview of the resources available from the project's GitHub site, which is continuously curated and updated to support each new release of macOS. The GitHub site provides practical, actionable recommendations in the form of secure baselines and associated rules. This publication also describes use cases for leveraging the mSCP content. Updates from the previous version of this publication mainly involve the new mSCP capability to create a custom benchmark by tailoring a baseline. The National Institute of Standards and Technology (NIST) has traditionally published secure configuration guides for Apple desktop/laptop operating system versions as prose-based Special Publications (SPs), such as NIST SP 800-179, Revision 1, Guide to Securing Apple macOS 10.12 Systems for IT Professionals: A NIST Security Configuration Checklist . In order to provide security configuration guidance to organizations more quickly and in a machine-consumable format, NIST established the open-source macOS Security Compliance Project (mSCP). NIST no longer produces SP guidance documents for each macOS release; instead, the mSCP continuously curates and updates machine-consumable macOS guidance. The latest macOS security baseline content is maintained and updated on the mSCP GitHub page [1]. The purpose of this document is to introduce the mSCP to broader audiences. This document provides a high-level overview of the mSCP, its components, and some common use cases. It refers readers to the online project documentation for in-depth technical information and use instructions."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## Analyzing Collusion Threats in the Semiconductor Supply Chain\n\nRekhi S, Amberiadis K, Akib AA, Srivastava A (2025) Analyzing Collusion Threats in the Semiconductor Supply Chain. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 46. https://doi.org/10.6028/NIST.CSWP.46\n\nThis work proposes a framework for analyzing threats related to the semiconductor supply chain. The framework introduces a metric that quantifies the severity of different threats subjected to a collusion of adversaries from different stages of the supply chain. Two different case studies are provided to describe the real-life application of the framework. The metrics and analysis aim to guide security efforts and optimize the trade-offs of hardware security and costs."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.1. 3.1.10. 3.1.11."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 5)"}, {"role": "assistant", "content": "................................................................... | Executive Summary.................................................................................................................\n| Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body ...................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe 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. The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.6. 3.2.6."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.6", "cmmc_practice_id": "AT.L2-3.2.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\nnd sensitive data are loaded into the manufactured IC. Standard data are generic and mostly available open source, but the sensitive data are anything whose disclosure would compromise IP or security.\nFor example, keys of crypto modules or logic locking keys are sensitive data. 7. Deployment and Use: This stage includes delivering the IC to customers and using the IC. Many hardware vulnerabilities are exploited at this stage. 8. End of Life: End-of-life for an IC is the stage where the manufacturer no longer sells or manufactures IC [8]. This is often because of technological advancements when new ICs exhibiting better performance have been launched. When a chip reaches its end-of-life, the deployed chips are gradually replaced and discarded. These discarded chips are"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\noutcomes from storage sanitization activities (e.g., identification of specific, acceptable sanitization techniques [13])\n- Documentation or evidence associated with sanitization activities (see Sec.\n4.6)\n- The identification of roles and responsibilities (see Sec. 4.7) and personnel competencies, skills, and training\n- The use of sanitization tools, including equipment calibration, testing, and maintenance\n- Type of assurances (e.g., guarantees, assessment results, formal certifications) that the ISM vendor should provide for the sanitization capabilities"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nThe objective of the guide is twofold: to help organizations evolve appropriate policies and procedures for dealing with mobile devices and to prepare forensic specialists to conduct forensically sound examinations involving mobile devices. This guide is not all-inclusive nor is it prescribing how law enforcement and incident response communities should handle mobile devices during their investigations or incidents. Specific vendors and mobile forensic acquisition guidance is not specified. However, from the principles outlined and other information provided, organizations should find this guide helpful in establishing their policies and procedures. This publication should not be construed as legal advice. Organizations should use this guide as a starting point for developing a forensic capability in conjunction with proper technical training and extensive guidance provided by legal advisors, officials, and management. This guide is the first revision to NIST SP800-101. While much of the information provided herein has been carried over from the original guide, the material has been updated and augmented to reflect the current state of the discipline. Level 1, Manual Extraction methods involve recording information brought up on a mobile device screen when employing the user interface. Level 2, Logical Extraction methods are used most frequently at this time and are mildly technical, requiring beginner-level training. Methods for levels 3 to 5 entail extracting and recording a copy or image of a physical store (e.g., a memory chip), compared to the logical acquisitions used at level 2 involve capturing a copy of logical storage objects (e.g., directories and files) that reside on a logical store (e.g., a\n\nfile system partition). Level 3, Hex Dumping/JTAG Extraction methods, entail performing a 'physical acquisition' of mobile device memory in situ and require advanced training."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\nNIST Internal Report\nNIST IR 8528\nStatus Report on the First Round of the\nAdditional Digital Signature Schemes for\nthe NIST Post-Quantum Cryptography\nStandardization Process\n\nStatus Report on the First Round of the\nAdditional Digital Signature Schemes for\nthe NIST Post-Quantum Cryptography\nStandardization Process\n\nHow to cite this NIST Technical Series Publication:\nAlagic G, Bros M, Ciadoux P, Cooper D, Dang Q, Dang T, Kelsey J, Lichtinger J, Liu YK, Miller C, Moody D,\nPeralta R, Perlner R, Robinson A, Silberg H, Smith-Tone D, Waller N (2024) Status Report on the First Round\nof the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization\nProcess. (National Institute of Standards and Technology, Gaithersburg, MD), NIST IR 8528.\nhttps://doi.org/10.6028/NIST.IR.8528"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 9)"}, {"role": "assistant", "content": "and technology usage are monitored to find potentially adverse events [DE.CM-03] ## Respond: - Incident Management: Incidents are escalated or elevated as needed [RS.MA-04] - Incident Response Reporting and Communication: Internal and external stakeholders are notified of incidents [RS.CO-02] ## Recover: - Incident Recovery Plan Execution: The integrity of backups and other restoration assets is verified before using them for restoration [RC.RP-03] - Incident Recovery Communication: Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders [RC.CO-03] ## NIST CSF 2.0: CYBERSECURITY SUPPLY CHAIN RISK MANAGEMENT (C-SCRM) A QUICK-START GUIDE ## HOW TO USE THE CSF TO DEFINE AND COMMUNICATE SUPPLIER REQUIREMENTS ## Create Target Profiles to Communicate Supplier Requirements by Supplier Criticality Level Follow these steps to create Target Profiles for communicating C-SCRM requirements to your suppliers."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n...... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................\n5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe predominant application architecture for cloud-native applications consists of multiple microservices, accompanied in some instances by a centralized application infrastructure, such as a service mesh, that provides all application services. This class of applications is generally developed using a flexible and agile software development paradigm called DevSecOps. A salient feature of this paradigm is the use of flow processes called continuous integration and continuous deployment (CI/CD) pipelines, which initially take the software through various stages (e.g., build, test, package, and deploy) in the form of source code through operations that constitute the software supply chain (SSC) in order to deliver a new version of software . This document outlines strategies for integrating SSC security measures into CI/CD pipelines.\n\nactor; artifact; attestation; CI/CD pipeline; package; provenance; repository; SBOM; SDLC; SLSA; software supply chain."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "ociated with products and services that may potentially contain malicious functionality, are counterfeit, or are vulnerable due to poor manufacturing and development practices within the supply chain.\nThese risks are associated with an enterprise's decreased visibility into and understanding of how the technology they acquire is developed, integrated, and deployed or the processes, procedures, standards, and practices used to ensure the security, resilience, reliability, safety, integrity, and quality of the products and services. This publication provides guidance to organizations on identifying, assessing, and mitigating cybersecurity risks throughout the supply chain at all levels of their organizations. The publication integrates cybersecurity supply chain risk management (C-SCRM) into risk management activities by applying a multilevel, C-SCRM-specific approach, including guidance on the development of C-SCRM strategy implementation plans, C-SCRM policies, C-SCRM plans, and risk assessments for products and services. ## Keywords\n\nacquire; C-SCRM; cybersecurity supply chain; cybersecurity supply chain risk management; information and communication technology; risk management; supplier; supply chain; supply chain risk assessment; supply chain assurance; supply chain risk; supply chain security. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nThe NIST Internet of Things (IoT) Cybersecurity Program has defined an IoT cybersecurity baseline for both technical capabilities and non-technical capabilities. Technical capabilities are those provided by digital products using software and hardware, such as Over-The-Air software update mechanisms or data encryption. Non-technical capabilities are those provided by organizations in support of digital product cybersecurity. Cybersecurity education and awareness is an example of a non-technical cybersecurity capability. The term 'education and awareness' is defined as 'The ability for the manufacturer and/or supporting entity to create awareness of and educate customers and others in the IoT device ecosystem about cybersecurity related information, considerations, features, etc. of the IoT device.' [1] There are many ways this capability can be implemented, but some examples include:\n\n- [1] Fagan M, Marron J, Brady KG, Jr, Cuthill BB, Megas KN, Herold R (2020) IoT Non-Technical Supporting Capability Core Baseline. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8259B. https://doi.org/10.6028/NIST.IR.8259B\n- [2] Fagan M, Megas KN, Scarfone K, Smith M (2020) Foundational Cybersecurity Activities for IoT Device Manufacturers. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8259. https://doi.org/10.6028/NIST.IR.8259\n- [3] Fagan M, Megas KN, Watrobski P, Marron J, Cuthill B (2022) Profile of the IoT Core Baseline for Consumer IoT Products. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8425. https://doi.org/10.6028/NIST.IR.8425\n- [4] Fagan M, Megas KN, Watrobski P, Marron J, Cuthill B, Lemire D, Hoehn B, Evans C (2024) Recommended Cybersecurity Requirements for Consumer-Grade Router Products."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 5)"}, {"role": "assistant", "content": "es and\n\ncause damage to equipment and/or injuries to workers. Furthermore, these incidents could significantly impact productivity and raise operating costs, depending on the extent of a cyber attack.\n## This practice guide can help your organization:\n\n-  detect and prevent unauthorized software installation\n-  protect ICS networks from potentially harmful applications\n-  determine changes made to a network using change management tools\n-  detect unauthorized use of systems\n-  continuously monitor network traffic\n-  leverage anti-malware tools\n\n## SOLUTION\n\nThe NCCoE, in conjunction with the NIST EL, collaborated with cybersecurity technology providers to develop and implement example solutions that demonstrate how manufacturing organizations can protect the integrity of their data from destructive malware, insider threats, and unauthorized software within manufacturing environments that rely on ICS. The example solutions use technologies and security capabilities from the project collaborators listed in the table below. These technologies were implemented in two distinct manufacturing lab environments that emulate discrete and continuous manufacturing systems. This project takes a modular approach in demonstrating two unique builds in each of the lab environments. The following is a list of the project's collaborators. \n\n| Collaborator | Component |\n|----------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| | Provides secure remote access with authentication and authorization support. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n...........................................................64 | |\n| A.1.2.\nSelecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7. FAMILY: CONFIGURATION MANAGEMENT................................................................................87 | |\n| A.2.8. FAMILY: CONTINGENCY PLANNING ...........................................................................................98 | |\n| A.2.9."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n- Identity Management, Authentication, and Access Control: Identities and credentials for authorized users, services, and hardware are managed by the organization [PR.AA-01]\n- Awareness and Training: Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind [PR.AT-02]"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 8)"}, {"role": "assistant", "content": ". Participants used the information on the Product Data Cards to develop a strategy for cybersecurity education and awareness for the product. The team's designs and ideas are documented in Section 4.\nTeams were successful in planning strategies that utilize novel techniques and sound best practices. From the participant teams' designs, the NIST team identified highlights and takeaways that are further elaborated in Section 5. ## 2. Background\n\n## Digital Product Cybersecurity Education and Awareness\n\nThe NIST Internet of Things (IoT) Cybersecurity Program has defined an IoT cybersecurity baseline for both technical capabilities and non-technical capabilities. Technical capabilities are those provided by digital products using software and hardware, such as Over-The-Air software update mechanisms or data encryption. Non-technical capabilities are those provided by organizations in support of digital product cybersecurity. Cybersecurity education and awareness is an example of a non-technical cybersecurity capability. The term 'education and awareness' is defined as 'The ability for the manufacturer and/or supporting entity to create awareness of and educate customers and others in the IoT device ecosystem about cybersecurity related information, considerations, features, etc. of the IoT device.' [1] There are many ways this capability can be implemented, but some examples include:\n\n- Instructions in a printed user manual. - How-to and other instructional videos available online. - In-person training sessions or remote webinars. - Information delivered via a product's mobile application. Cybersecurity education and awareness can provide critical support for the cybersecurity of digital products. Notably, the capability can inform and educate users about other cybersecurity capabilities, particularly technical capabilities."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nRansomware, destructive malware, insider threats, and even honest mistakes present an ongoing threat to organizations that manage data in various forms. Database records and structure, system files, configurations, user files, application code, and customer data are all potential targets of data corruption and destruction."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.1.2 | ZTA y el uso de la microsegmentación... 3.1.2 ZTA y el uso de la microsegmentación\n\nUna empresa puede optar por implementar una ZTA basada en el emplazamiento de los recursos individuales o grupos de recursos en un único segmento de red protegido por un componente de seguridad denominado puerta de enlace ( gateway )."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThe National Institute of Standards and Technology (NIST) hosted an in-person, all-day workshop on February 27, 2024, to discuss existing and emerging cybersecurity threats and mitigation techniques for semiconductors throughout their life cycle. The workshop obtained valuable feedback from industry, academia, and government to inform NIST's development of cybersecurity and supply chain standards, guidance, and recommended practices. The discussion focused on semiconductor development and highlighted cybersecurity measurements and metrics that utilize reference data sets to facilitate the testing, attestation, certification, verification, and validation of semiconductor components. It also emphasized the use of automated cybersecurity tools and techniques to secure manufacturing environments throughout the development life cycle. This report summarizes the content that was presented and discussed at the workshop. These activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle. The last panel member was Matthew Areno, Senior Principal Engineer for Intel Corporation. Matthew admitted that there is no industry standard to describe the phases of the supply chain for ICs."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 5)"}, {"role": "assistant", "content": "ncern to the public at large during this time Interval. In response to this need. Government laws and regulations in this arena have continued to grow and place legal requirements on computer systems.\nFor example:\n\n- o The Privacy Act (1974), which specified the appropriate handling of personal records by Federal agencies, has been followed by the Foreign Corrupt Practices Act (1977) that specifies the objectives of a public organization's system of Internal accounting controls and, by implication, its system of general management controls. - o The Office of Management and Budget (0MB), in Its Circular A-71 , Transmittal Memorandum #1 (1978), established requirements for Federal agencies to have a computer security program and appropriate audits of that security. - o The U. S. General Accounting Office (GAO), as a direct consequence of the session on Interna] Audit Standards at the first invitational workshop on audit of computer security, developed and issued in March of 1979 a set of three supplemental audit standards to help Government auditors effectively perform audits of computer-based systems\n\nAs a consequence, the establishment of processes and procedures for controlling computer systems from the physical, administrative, and technical viewpoints has continued to expand in importance, both to the computer community in general and the Institute for Computer Sciences and Technology of the National Bureau of Standards (NBS) in particular. In recognition of these growing needs and legal requirements for computer security and the adequate auditing of computer security, ^3BS, with the support of GAO, sponsored this second invitational workshop on audit of computer security In Miami Beach, Florida on November 28-30, 1978. Following the successful approach used in the first workshop, leading experts in the audit and computer communities were again invited to share their views -this time on a more focused arrangement of the subject."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nations prevailed. An important characteristic of a forensic tool is its ability to maintain the integrity of the original data source being acquired and also that of the extracted data.\nThe former is done by blocking or otherwise eliminating write requests to the device containing the data. The latter is done by computing a cryptographic hash over the contents of the evidence files created and recurrently verifying that this value remains unchanged throughout the lifetime of those files. Preserving integrity not only maintains credibility from a legal perspective, but it also allows any subsequent investigation to use the same baseline for replicating the analysis."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.3. 3.2.3 requires a physical authenticator to be\nauthenticated along with a biometric comparison. 3.2.3 requires a physical authenticator to be\nauthenticated along with the biometric comparison."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 5)"}, {"role": "assistant", "content": "blication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations.\ni\n\n\fNIST SP 800-63A-4\nJuly 2025\n\nPatent Disclosure Notice\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for\ncompliance with the guidance or requirements of this publication disclose such patent\nclaims to ITL. However, holders of patents are not obligated to respond to ITL calls for\npatents and ITL has not undertaken a patent search in order to identify which, if any,\npatents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims\nwhose use may be required for compliance with the guidance or requirements of this\npublication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid\npatent infringement in the use of this publication. ii\n\n\fNIST SP 800-63A-4\nJuly 2025\n\nTable of Contents\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\n1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1. 1.2. Expected Outcomes of Identity Proofing\n\n. . . . . . . . . . . . . . . . . Identity Assurance Levels\n\n. . . . . . . . . . . . . . . . . . . . . . . . . 1.3. Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4. Document Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. Identity Proofing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1. Identity Proofing and Enrollment\n\n. . . . . . . . . . . . . . . . . . . . . 2.1.1. Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2. Identity Proofing Roles . . . . . . . . . . . . . . . . . . . . . . . 2.1.3. Identity Proofing Types\n\n. . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n........................................................................................ 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE ..................................................\n6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThe National Institute of Standards and Technology (NIST) hosted an in-person, all-day workshop on February 27, 2024, to discuss existing and emerging cybersecurity threats and mitigation techniques for semiconductors throughout their life cycle. The workshop obtained valuable feedback from industry, academia, and government to inform NIST's development of cybersecurity and supply chain standards, guidance, and recommended practices. The discussion focused on semiconductor development and highlighted cybersecurity measurements and metrics that utilize reference data sets to facilitate the testing, attestation, certification, verification, and validation of semiconductor components. It also emphasized the use of automated cybersecurity tools and techniques to secure manufacturing environments throughout the development life cycle. This report summarizes the content that was presented and discussed at the workshop. These activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle. Furthermore, Jonathan stressed the importance and continued need for public-private partnerships, like the Semiconductor Research Corporation and the Semiconductor Industry Association."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nThe increasing use of computers by Government and private organiza-\ntions for the storage and manipulation of records of all kinds— personal\nas well as of a business nature— has placed computers and the systems in\nwhich they reside in an extremely sensitive position in our society. The\nneeds of the individual as well as Government and private organizations\nrequire that this data and their resident systems be accurate and reli-\nable.\ngiven adequate protection from threats and hazards. The establishment of\nsecure computer systems is the way in which the computer community as-\nsures the users of such systems that all of these requirements are being\nmet\n\nCOMPUTER SYSTEM, OPERATIONS, AND SOFTWARE\nDATA PROCESSING TECHNIQUES\nMANAGEMENT OF THE DATA PROCESSING FUNCTION „\nSECURITY OF THE DATA PROCESSING FUNCTION\nRISK ANALYSIS AND THREAT ASSESSMENT ..........\nMANAGEMENT CONCEPTS AND PRACTICES\nAUDITING CONCEPTS AND PRACTICES\nBASIC QUALIFICATIONS NEEDED TO EVALUATE COMUTER\nSECURITY\n\nRELEVANT THREATS AND THEIR SEVERITY"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n. . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . .\n. . . | 14 |\n| 3.4. | SIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 16 |\n| 4. Conclusion . . | . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| References . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms | . | 26 |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | 2 |\n| Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | 4 |\n| Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | 6 |\n| Table 4. Performance of HQC in thousands of cycles on x86_64 [1] . . . | Table 4."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nThe evaluation of specific PACS architectures or implementations is also outside the scope of this publication, as is the standardization of PACS. Unless normatively referenced, this document is a best practice guideline.\n\nAs per OMB policy, installed PACS readers are required to be from the approved products list of the General Services Administration (GSA) FIPS 201 Evaluation Program [FIPS 201 EP]. Each of these readers are capable of one or more PIV authentication mechanisms, such that each PACS reader can support the authentication of any PIV cardholder using a PIV authentication mechanism, including those with PIV Cards that do not implement any of the optional card capabilities. Note that in this document, a PACS reader's authentication capabilities is assumed to be supported by a PACS controller since the controller is usually the component to execute or support execution of the PIV authentication mechanisms, while the reader functions as the interface between the PIV Card and the controller.\n\nPACS readers come in varying configurations and offer multiple interface options for the card and the controller. [FIPS201] standardizes the use of the [ISO/IEC 14443] interface for the contactless reader to card communication. Note that the card reader may require additional conformance testing for federal acquisition. An authority for such conformance testing is the General Services Administration (GSA) FIPS 201 Evaluation Program [FIPS 201 EP], which defines tests and maintains a list of approved products. Not all existing PACS use this interface, so some agencies may have to plan to migrate from their legacy environment to the [ISO/IEC 14443] conformant interface. Alternatively, an agency may use the PIV Card's contact interface based on [ISO/IEC 7816]."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nCJI is commonly accessed using computer-aided dispatch (CAD) and record management system (RMS) software, which communicate with a state-level message switch application. CJI MFA architectures will likely need to integrate with one or both of these technologies. As agencies around the country begin to implement MFA solutions, the approaches they use require careful consideration and planning. This document provides a general overview of MFA, outlines design principles and architecture considerations for implementing MFA to protect CJI, and offers specific examples of use cases that agencies face today. It also outlines how CAD/RMS and message switch technologies can support standards and best practices that provide agencies with maximum optionality to implement MFA in a way that promotes security, interoperability, usability, and cost savings.\n\nAs agencies around the country begin to implement this requirement, they face several challenges that require careful consideration and planning. The purpose of this document is to help agencies identify and address their MFA implementation needs by providing insight into MFA architectures and how they can be used to meet law enforcement-specific use cases."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nMany manufacturing organizations rely on industrial control systems (ICS) to monitor and control their machinery, production lines, and other physical processes that produce goods. To stay competitive, manufacturing organizations are increasingly connecting their operational technology (OT) systems to their information technology (IT) systems to enable and expand enterprise-wide connectivity and remote access for enhanced business processes and capabilities.\n\nOnce malicious actors gain access, they can harm an organization by compromising data or system integrity, hold ICS and/or OT systems ransom, damage ICS machinery, or cause physical injury to workers. The statistics bear this out. The X-Force Threat Intelligence Index 2021 (ibm.com) stated that manufacturing was the second-most-attacked industry in 2020, up from eighth place in 2019.\n\nOne particular case study illustrates the long-lasting effects and damage a single cyber attack can inflict on an organization. It was reported that a global pharmaceutical manufacturer suffered a cyber attack that caused temporary production delays at a facility making a key vaccination. More than 30,000 laptop and desktop computers, along with 7,500 servers, sat idle. Although the company claimed that its operations were back to normal within six months of the incident; at this writing, news reports stated that the organization is locked in a legal battle with its insurers and is looking to reclaim expenses that include repairing its computer networks and the costs associated with interruptions to its operations. They are seeking more than $1.3 billion in damages."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| DATE | TYPE | REVISION | PAGE |\n|------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| 12-10-2020 | Editorial | Section 1.4: Change 'NIST SP 800-53 [SP 800-53]' to '[SP 800-53]' | 3 |\n| 12-10-2020 | Editorial | Section 2.4 (Footnote 26): Change 'See [SP 800-37], Task P-4.' to 'See [SP 800-37], Task P-4, Organizationally-Tailored Control Baselines and Cybersecurity Framework Profiles (Optional), for additional guidance on tailoring control baselines for organization- wide use."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 4)"}, {"role": "assistant", "content": "The main audience for this publication is IoT device manufacturers, especially with the emerging role of product security officers. This publication may also help IoT device customers or integrators.\n## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents, and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 10)"}, {"role": "assistant", "content": "he detecting effort. In other words, instead of checking by retracing the interrelations between rules after the policy is completed, it only checks the new added rule against previous 'correct' ones.\nEven though this method does not require comprehensive large numbers\n\nof test cases, requirements, or an oracle, the translation or mapping process for implementing the simulated system is a challenge [VK13]. This report proposes an innovative technique that applies a classification algorithm of machine learning [ML] to answer challenges of capability due to the coverage of test cases or oracle and the difficulty of system translation from traditional access control policy verification methods. In this report, the Introduction describes the challenges of traditional policy verification methods. Section 2 explains how an ML Classification method can be applied to policy verification. Section 3 demonstrates a policy verification approach for an ML random forest classification (RFC) algorithm. Section 4 describes general access control applications that can benefit from the proposed method. The last section is the Conclusion. ## 2 Machine Learning for Access Control Verification\n\nMachine learning has been used for device control, system analysis, and business forecasting. However, the use of ML for software testing is in the early stages [AWCS, CAT5]. In particular, ML applications for model proof are still elusive and have yet to be explored. ML classification allows for the generation or prediction of target classes for new input data using some sample training data produced by running the system instead of comprehensive input data. For access control policy verification, the training data is assigned attributes' values of policy rules, and the target for classification is access permissions (e.g., grant and deny) assigned to rules. The data is consumed by an ML classification algorithm to generate a classification model ."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 7)"}, {"role": "assistant", "content": "ine if additional supplier requirements are needed based on existing criticality criteria, such as your mission or business, data type being processed, or digital product or service being provided. 2.\nCreate CSF Target Profiles for Each Supplier Criticality Level. The next page explains how to express supplier requirements for each supplier criticality level."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nAccess to multiple cloud services, the geographic spread of enterprise Information Technology (IT) resources (including multiple data centers), and the emergence of microservices-based applications (as opposed to monolithic ones) have significantly altered the enterprise network landscape. This document is meant to provide guidance to this new enterprise network landscape from a secure operations perspective. Hence, it starts by examining the security limitations of current network access solutions to the enterprise network. It then considers security feature enhancements to traditional network appliances in the form of point security solutions, network configurations for various security functions (e.g., application/services security, cloud services access security, device or endpoint security), security frameworks that integrate these individual network configurations (e.g., zero trust network access [ZTNA]), and the evolving wide area network (WAN) infrastructure to provide a comprehensive set of security services for the modern enterprise network landscape (e.g., secure access service edge [SASE])."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 5)"}, {"role": "assistant", "content": "and the project documentation wiki is at https://github.com/usnistgov/macos\\_security/wiki. ## Trademark Information\n\nAll registered trademarks or trademarks belong to their respective organizations.\n## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| | Introduction ...................................................................................................................... | Introduction ......................................................................................................................"}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.2.2 Resolution\n\nThe build provides several mechanisms to detect and mitigate this use case."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n- Subverting, removing, or introducing a step within the SSC to maliciously modify or sabotage the resulting software product\n- Stealing credentials from the build system to mint and sign unauthorized malicious software\n- Causing naming collisions\n\n- Source code\n- Credentials\n- Sensitive data\n- Internal operations\n- Build systems\n\nA software developer's workstation typically contains various assets, including source code, credentials, and access to sensitive information, such as personally identifiable information (PII), protected health information (PHI), intellectual property (IP), cryptographic materials (e.g., software artifact signing keys), and proprietary information. Companies should identify critical assets and implement controls to protect them from unauthorized access, such as access controls, multi-factor authentication, encryption of data at rest and in transit, and data loss prevention (DLP) measures."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 8)"}, {"role": "assistant", "content": "Barrett, Kathleen Coupe, Jeff Eisensmith, Chris Enloe, Ned Goren, Matthew Halstead, Jody Jacobs, Ralph Jones, Martin Kihiko, Raquel Leone, and the scientists, engineers, and research staff from the Computer Security Division and the Applied Cybersecurity Division for their exceptional contributions in helping to improve the content of the publication."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.13. Requirements for the Validation of Physical Evidence . . . . . . . . . . .\n\n• Physical or digital address: A physical (i.e., mailing address) or digital (e.g., phone\nnumber or email) address at which the applicant can receive communications\nrelated to the proofing process.\n\ncryptographically protected and can be validated using approved cryptography\nthrough verification of a digital signature applied by the issuing source."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos...............................................24"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n..................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5.\nTraceability of CE Operations.....................................................................................................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1. Information Decisions in the System Life Cycle..........................................................................20 |\n| 4.3.2. Determination of Security Categorization..................................................................................21 |\n| 4.3.3. Reuse of Media...........................................................................................................................22 |\n| 4.3.4. Control of Media ........................................................................................................................22 |\n| 4.3.5. Data Protection Level .................................................................................................................23 |\n| 4.3.6. Sanitization and Disposal Decision.............................................................................................23 |"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\ncredential; e-authentication; identity credential; issuance; personal identity verification (PIV); physical access control system (PACS); PIV authentication mechanisms; PIV cards; public key infrastructure (PKI); validation\n\nThis document is intended for government officials responsible for implementing Homeland Security Presidential Directive-12 (HSPD-12) compliant physical access control systems (PACS). Information in this document is also useful to government contractors and physical security vendors that provide HSPD-12 systems, products, and integration services. It is expected that readers have a general knowledge of PIV standards, including [FIPS 201-2], [SP800-73], and [SP800-78].\n\nMany changes in this document were made to align SP 800-116 with revision 2 of FIPS 201 (FIPS 201-2). For example, credential validation is now required (see Section 4.4). The CHUID authentication mechanism has been deprecated due to security concerns. For this reason, this publication marks the authentication mechanism as deprecated to signify that it is not a viable authentication mechanism to deploy for physical access control system (PACS). The CHUID data element on the PIV Card, however, remains a mandatory element as the BIO(-A) and SYMCAK authentication mechanisms use the data element as a source for the card's expiration date. It also provides unique identifiers for PACS ACLs. The previous version of this document also included the combined VIS + CHUID authentication mechanism as an option to transitioning from Unrestricted to Controlled areas. VIS + CHUID, however, is not included in this version of the document since it provides 'LITTLE or NO' confidence in the identity of the cardholder."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Access Control on NoSQL Databases provide? (Part 3)"}, {"role": "assistant", "content": "weak authorization mechanisms. As access control is a fundamental data protection requirement of any database management system DBMS, this document focuses on access control on NoSQL database systems.\n## Keywords\n\naccess control; attribute-based access control; authorization; database systems; No-SQL; SQL. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 5)"}, {"role": "assistant", "content": "|\n| 5.1.1. Benefits.................................................................................................................. | 5.1.1.\nBenefits.................................................................................................................. | 6 |\n| 5.1.2. Challenges ............................................................................................................. | 5.1.2. Challenges ............................................................................................................. | 8 |\n| 5.2. Testing/Validation Programs and Certifications ....................................................... | 5.2. Testing/Validation Programs and Certifications ....................................................... | 15 |\n| 5.2.1. Benefits................................................................................................................ | 5.2.1. Benefits................................................................................................................ | 15 |\n| 5.2.2."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.1.2 | Asset Inventory and Discovery ... 3.1.2 Asset Inventory and Discovery\n\nOrganizational members with access to the enterprise database of computing devices can access a listing by authenticating to the Archer system. 3.1.2."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology promotes the United States economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof-of-concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of non-national-security-related information in federal information systems. This Special Publication 800 series reports on ITL's research, guidelines, and outreach efforts in information system security and its collaborative activities with industry, government, and academic organizations. applications 3 are not required because the security controls for those applications are typically provided by the general support system or major application in which they operate. In those cases where the minor application is not connected to a major application or general support system, the minor application should be briefly described in a general support system plan that has either a common physical location or is supported by the same organization. Additional information is provided in Chapter 2. system to the high watermark or highest impact level must be applied when grouping minor applications/subsystems with varying FIPS 199 impact levels into a single general support system or major application unless there is adequate boundary protection, e.g., firewalls and encryption, around those subsystems or applications with the highest impact level. Additionally, there must be assurance that the shared resources, i.e., networks, communications, and physical access within the whole general support system or major application, are protected adequately for the highest impact level."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Standard | Sections | Implementation Specifications (R) = Required, (A) = Addressable | |-----------------------------------------------------|---------------------------|-------------------------------------------------------------------| | Administrative Safeguards | Administrative Safeguards | Administrative Safeguards | | Security Management Process | 164.308(a)(1) | Risk Analysis (R) | | Security Management Process | 164.308(a)(1) | Risk Management (R) | | Security Management Process | 164.308(a)(1) | Sanction Policy (R) | | Security Management Process | 164.308(a)(1) | Information System Activity Review (R) | | Assigned Security Responsibility | 164.308(a)(2) | (R) | | Workforce Security | 164.308(a)(3) | Authorization and/or Supervision (A) | | Workforce Security | 164.308(a)(3) | Workforce Clearance Procedure (A) | | Workforce Security | 164.308(a)(3) | Termination Procedures (A) | | Information Access Management | 164.308(a)(4) | Isolating Health care Clearinghouse Function (R) | | Information Access Management | 164.308(a)(4) | Access Authorization (A) | | Information Access Management | 164.308(a)(4) | Access Establishment and Modification (A) | | Security Awareness and Training | 164.308(a)(5) | Security Reminders (A) | | Security Awareness and Training | 164.308(a)(5) | Protection from Malicious Software (A) | | Security Awareness and Training | 164.308(a)(5) | Log-in Monitoring (A) | | Security Awareness and Training | 164.308(a)(5) | Password Management (A) |"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n1. Know when new software vulnerabilities affect your organization's assets, including applications, operating systems, and firmware. This involves knowing what assets your organization uses and which software and software versions those assets run down to the level of packages and libraries, as well as keeping track of new vulnerabilities in that software. For example, your organization might subscribe to vulnerability feeds from software vendors, security researchers, and the National Vulnerability Database (NVD). 2. Plan the risk response. This involves assessing the risk the vulnerability poses to your organization, choosing which form of risk response (or combination of forms) to use, and deciding how to implement the risk response. For example, you might determine that risk is elevated because the vulnerability is present in many organization assets and is being exploited in the wild, then choose mitigation as the risk response and mitigate the vulnerability by upgrading the vulnerable software and altering the software's configuration settings. 3. Execute the risk response. This will vary depending on the nature of the selected risk response, but common phases include the following:\n- a. Prepare the risk response. This encompasses any preparatory activities, such as acquiring, validating, and testing patches for the vulnerable software; deploying additional security controls to safeguard the vulnerable software; or acquiring a replacement for a legacy asset that cannot be patched. It might also include scheduling the risk response and coordinating deployment plans with enterprise change management, business units, and others. - b. Implement the risk response. Examples of this include distributing and installing a patch, purchasing cybersecurity insurance, deploying additional security controls, and changing asset configurations and state (e.g., software reset,\n\n- Distribute the patch."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 10)"}, {"role": "assistant", "content": "............................................................ 18 | REFERENCES............................................................................................................................\n18 |\n| List of Appendices | List of Appendices | List of Appendices |\n| APPENDIX A-ACRONYMS................................................................................................. 20 | APPENDIX A-ACRONYMS................................................................................................. 20 | APPENDIX A-ACRONYMS................................................................................................. 20 |\n| APPENDIXB-FOCUS GROUP DEMOGRAPHICS QUESTIONS................................. 21 | APPENDIXB-FOCUS GROUP DEMOGRAPHICS QUESTIONS................................. 21 | APPENDIXB-FOCUS GROUP DEMOGRAPHICS QUESTIONS................................. 21 |\n| APPENDIXC-FOCUS GROUP QUESTIONS.................................................................... 25 | APPENDIXC-FOCUS GROUP QUESTIONS.................................................................... 25 | APPENDIXC-FOCUS GROUP QUESTIONS...................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................3 |\n| 2. An Overview of MFA Technologies and Concepts ............................................................................5 |\n| 2.4.1. Benefits of Identity Federation ....................................................................................................7 |\n| 2.4.2. Benefits of Single Sign-On ............................................................................................................8 |\n| 3. Choosing an MFA Implementation for Protecting CJI .....................................................................11 |\n| 3.1.1. Principle 1: Authenticator Reusability........................................................................................12 |\n| 3.1.2. Principle 2: Authenticator Optionality .......................................................................................12 |\n| 3.1.3. Principle 3: Minimize the Passing of Memorized Secrets ..........................................................12 |\n| 3.1.4. Principle 4: Ensure MFA Is Integrated to Protect CJI..................................................................13 |\n| 3.2.1. MFA Users ..................................................................................................................................13 |\n| 3.2.2."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Personnel Security?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\n| Vulnerability | Relevant Consumer Profile Capabilities |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Commands can be launched using the device | Interface Access Control Documentation |\n| Unauthorized Publication of Fitness Tracker Data - Fitness tracker location data for military personnel were publicly posted even when product was configured for privacy. | Unauthorized Publication of Fitness Tracker Data - Fitness tracker location data for military personnel were publicly posted even when product was configured for privacy."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\n'For our main enterprise network, it's computer-based training that's taken annually…But for those who don't have access to the enterprise network often for certain other networks that we might maintain,…those are physical briefings done by the ISSOs [information system security officers] to those personnel. And then they sign an acknowledgment form.' (D03)\n\n'You've got IT security, physical security, personnel security, etc. And they have their own training requirements…It's inefficient.' (S11)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nother than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n□ Audit reports or FISMA (Federal Information Security Modernization Act of 2014) evaluations"}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 10)"}, {"role": "assistant", "content": "| FORENSIC TOOL CAPABILITIES ........................................................................................\n| 25 |\n| 4. PRESERVATION................................................................................................................ | 4. PRESERVATION................................................................................................................ | 27 |\n| 4.1 | SECURINGAND EVALUATINGTHE SCENE .......................................................................27 | |\n| 4.2 | DOCUMENTINGTHE SCENE.............................................................................................. | 28 |\n| 4.3 | ISOLATION | ........................................................................................................................"}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control. 9 Reciprocity is an agreement between organizations to accept one another's security assessment results in order to reuse system resources or to accept each other's assessed security posture in order to share information. 10 [SP 800-64] and [SP 800-160 v1] provide guidance on security considerations in the SDLC. Organizations may choose to divide security and privacy requirements into more granular categories depending on where the requirements are employed in the SDLC and for what purpose. Organizations may use the term capability requirement to describe a capability that the system or organization must provide to satisfy a stakeholder protection need. In addition, organizations may refer to system requirements that pertain to particular hardware, software, and firmware components of a system as specification requirements -that is, capabilities that implement all or part of a control and that may be assessed (i.e., as part of the verification, validation, testing, and evaluation processes)."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 3)"}, {"role": "assistant", "content": "-88r1 (Revision 1) (December 2014) https://doi.org/10.6028/NIST.SP.800-88r1\n\n## How to Cite this NIST Technical Series Publication\n\nChandramouli R, Hibbard EA (2025) Guidelines for Media Sanitization.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-88r2. https://doi.org/10.6028/NIST.SP.800-88r2\n\n## Author ORCID iDs\n\nRamaswamy Chandramouli: 0000-0002-7387-5858 Eric Hibbard: 0009-0001-8112-1263\n\n## Contact Information\n\nsp800-88-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/88/r2/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nMedia sanitization refers to a process that renders access to target data on the media infeasible for a given level of effort. This guide will assist organizations and system owners in setting up a media sanitization program with proper and applicable techniques and controls for sanitization and disposal based on the sensitivity of their information. ## Keywords\n\nCryptographic erase; ensuring confidentiality; media sanitization; media sanitization program; media types; sanitization methods; secure erase. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nFurther, this project is not intended to cover the entire supply chain risk management process; it focuses on the acceptance testing portion of a more holistic defense-in-depth/defense-in breadth supply chain risk management strategy. The project enables verification of the identity of computing devices (including replacement parts and updates or upgrades) once they have been acquired but before they are implemented or installed."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 4)"}, {"role": "assistant", "content": "|\n| 3.3 Adoption of International Standards | in SCAP v2 ............................................\n6 |\n| 4 SCAP v2 Development | Plan..................................................................................7 |\n| List of Appendices | List of Appendices |\n| Appendix A-Applications of the SCAP 2.0 Architecture.........................................9 | Appendix A-Applications of the SCAP 2.0 Architecture.........................................9 |\n| A.1 Vulnerability Assessment................................................................................ | 9 |\n| A.2 Configuration Setting Checklist | Assessment ................................................"}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- Based on NIST SP 800-53, Revision 5 and the NIST SP 800-53B moderate impact control baseline.\n- Applies updated tailoring criteria addressing stakeholder feedback (adding new, consolidating, and withdrawing requirements).\n- Includes increased specificity in security requirements.\n- Introduces organization-defined parameters (ODP) to increase flexibility to better manage organizationspecific risks.\n\nControl Baseline: A set of controls you can implement to meet strategic, legal, regulatory, or contractual security and privacy requirements and manage risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n## Guidelines for the Use of PIV Credentials in Facility Access\n\n## Guidelines for the Use of PIV Credentials in Facility Access\n\nThis recommendation provides a technical guideline to use Personal Identity Verification (PIV) Cards in facility access; enabling federal agencies to operate as government-wide interoperable enterprises. These guidelines cover the risk-based strategy to select appropriate PIV authentication mechanisms as expressed within Federal Information Processing Standard (FIPS) 201."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nThe HIPAA Security Rule focuses on safeguarding electronic protected health information (ePHI) held or maintained by regulated entities. The ePHI that a regulated entity creates, receives, maintains, or transmits must be protected against reasonably anticipated threats, hazards, and impermissible uses and/or disclosures. This publication provides practical guidance and resources that can be used by regulated entities of all sizes to safeguard ePHI and better understand the security concepts discussed in the HIPAA Security Rule. administrative safeguards; Health Insurance Portability and Accountability Act; implementation specification; physical safeguards; risk assessment; risk management; Security Rule; standards; technical safeguards. | Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................4 |\n| 2. HIPAA Security Rule .......................................................................................................................9 |\n| 3. Risk Assessment Guidance............................................................................................................14 |\n| 4. Risk Management Guidance .........................................................................................................24 |\n| 5. Considerations When Implementing the HIPAA Security Rule........................................................28 |\n| 5.1.2. Assigned Security Responsibility (§ 164.308(a)(2)) ....................................................................35 |\n| 5.1.3."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n- zero-day vulnerabilities\n- vulnerabilities due to outdated or unpatched systems\n- custom software vulnerabilities/errors\n- social engineering and user-driven events\n- poor access control\n\n| Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | Standards & Best Practices | Standards & Best Practices |\n|--------------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------------|--------------------------------------------------|------------------------------|\n| Function | Category | Subcategory | NIST SP 800- 53 R4 | ISO/IEC 27001:2013 | NIST SP 800- 181 |\n| PROTECT (PR) | Data Security (PR.DS) | PR.DS-6: Integrity check- ing mechanisms are used to verify software, firmware, and infor- mation integrity. | SC-16, SI-7 | A.12.2.1, A.12.5.1, A.14.1.2, A.14.1.3, A.14.2.4 | OM-DTA-001 |\n| DETECT (DE) | Anomalies and Events (DE.AE) | DE.AE-1: A baseline of network operations and expected data flows for users and systems is es- tablished and managed. | AC-4, CA-3, CM-2, SI-4 | A.12.1.1, A.12.1.2, A.13.1.1, A.13.1.2 | SP-ARC-001 |\n| DETECT (DE) | Anomalies and Events (DE.AE) | DE.AE-2: Detected events are analyzed to understand attack tar- gets and methods."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.......................................................................75 |\n| 5.4.1.\nBusiness Associate Contracts or Other Arrangements (§ 164.314(a)).......................................77 |\n| 5.4.2. Requirements for Group Health Plans (§ 164.314(b))................................................................79 |\n| 5.5.1. Policies and Procedures (§ 164.316(a))......................................................................................81 |\n| 5.5.2. Documentation (§ 164.316(b))...................................................................................................83 |\n| References.......................................................................................................................................85 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................87 |\n| Appendix B. Glossary .......................................................................................................................91 |\n| Appendix C."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| | | 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| 5.2.4. Device and Media Controls (§ 164.310(d)).................................................................................63 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 5.3.1. Access Control (§ 164.312(a)).....................................................................................................65 |\n| 5.3.2. Audit Controls (§ 164.312(b)).....................................................................................................69 |\n| 5.3.3. Integrity (§ 164.312(c))...............................................................................................................71 |\n| 5.3.4. Person or Entity Authentication (§ 164.312(d)).........................................................................73 |\n| 5.3.5. Transmission Security (§ 164.312(e)(1)).....................................................................................75 |\n| 5.4.1."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nPACS readers come in varying configurations and offer multiple interface options for the card and the controller. [FIPS201] standardizes the use of the [ISO/IEC 14443] interface for the contactless reader to card communication. Note that the card reader may require additional conformance testing for federal acquisition. An authority for such conformance testing is the General Services Administration (GSA) FIPS 201 Evaluation Program [FIPS 201 EP], which defines tests and maintains a list of approved products. Not all existing PACS use this interface, so some agencies may have to plan to migrate from their legacy environment to the [ISO/IEC 14443] conformant interface. Alternatively, an agency may use the PIV Card's contact interface based on [ISO/IEC 7816].\n\nThe interface from the door reader to the controller also comes in different configurations. [FIPS201] does not specify which protocols can be used for this interface, as long as the necessary data can be communicated to the controller. Typical deployed implementations support transmitting a small amount of data (on the order of 10 to 15 bytes), but [FIPS201] defines data elements that are much larger. Therefore, depending on the agency's implementation strategy, an upgrade to the door reader to controller interface may also be required. At a minimum, a 14-decimal-digit FASC-N Identifier or the full 16-byte Card UUID will be supported. Note that any change to this interface may also necessitate changes to the physical wiring and cabling infrastructures."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| Operational Audits of Automated Information Systems (AISs) | Operational Audits of Automated Information Systems (AISs) | Operational Audits of Automated Information Systems (AISs) | 4 | | | 1.1.5 | Relevant Laws and Regulations | Relevant Laws and Regulations | 4 | | | 1.1.5.1 | Requirements for Audit Involvement | Requirements for Audit Involvement | 4 | | | | 1.1.5.2 | Requirements for Internal Control | 5 | | 1.2 | RISKS GENERATED BY COMPUTER TECHNOLOGY | RISKS GENERATED BY COMPUTER TECHNOLOGY | RISKS GENERATED BY COMPUTER TECHNOLOGY | 6 | | | 1.2.1 Overview of Risks | 1.2.1 Overview of Risks | 1.2.1 Overview of Risks | 6 | | | 1.2.1.1 | | Definitions | 7 | | | | 1.2.1.2 | Vulnerability/Risk Related Requirements | 7 | | | 1.2.2 | Risks in a Computerized Environment | Risks in a Computerized Environment | 8 | | | | 1.2.2.1 | Additional Risks Present in a Computerized Environment | 8 | | | | 1.2.2.2 | Assessing Vulnerabilities Through the Audit Process | 9 | | 1.3 | CONTROL OBJECTIVES AND STANDARDS IN A COMPUTER ENVIRONMENT | CONTROL OBJECTIVES AND STANDARDS IN A COMPUTER ENVIRONMENT"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nDescription: Ensuring personnel are made aware of the security risks associated with their activities and of the applicable laws, directives, policies, standards, regulations, or procedures related to the security of organizational systems; and ensuring that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.\n\nRegularly provide basic and advanced security literacy training to new and existing staff. Customize the content to make it relevant -based on the systems that personnel have authorized access to, contextualized to the work environments of personnel (e.g., telework, shop floor), and tailored to the specific roles of personnel. The content should include:"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.2.2 | Test Results... 3.2.2 Test Results\n\nThe user connects to the Dispel VDI as shown in Figure D-33 and then connects to the PCS workstation as shown in Figure D-34. 3.2.2 Forescout Console\n\nForescout Console was installed following the standard installation procedures."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.5.1 DE."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nAs advances in technology permit automatic control of more and more of the functions of physical systems, the opportunity for cyber attacks that include exploitation of such automation capabilities becomes a greater risk. For example, in the 2010 Stuxnet attack an embedded infection in control systems was used to successfully damage a large number of nuclear power related centrifuges in Iran. While the application of perimeter security technologies have been applied to help manage the likelihood of SCADA-based cyber attackers exploiting highly automated physical systems, successful attacks have occurred, and furthermore, perimeter solutions do not address important classes of insider and supply chain initiated attacks. As a result, it has been recognized that perimeter security needs to be augmented by other approaches for addressing potential cyber attacks [1]."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.2.2 | Communication Channels... 3.2.2 Communication Channels\n\nParticipants indicated how their organizations communicate and disseminate security awareness information."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n## Federal Cybersecurity Awareness Programs\n\n## Federal Cybersecurity Awareness Programs\n\nPrior industry surveys and research studies have revealed that organizational cybersecurity awareness (hereafter shortened to 'security awareness') programs may face a number of challenges, including lack of: leadership support; resources; and staff with sufficient background and skills to implement an effective and engaging program. However, no prior research has explored security awareness programs specifically in the United States (U.S.) government (federal) sector. To address this gap, NIST conducted a two-phase, mixed methods research study to understand the needs, challenges, and practices of federal security awareness programs. This report describes the research background and methodology, along with the characteristics of the participants, organizations, and programs represented in the study. Research results can serve as a resource for federal security awareness professionals, managers, and organizational decision makers to improve and advocate for their organizations' security awareness programs. Results can also inform the development of federal security awareness guidance, policies, sharing forums, and initiatives meant to aid programs in becoming more effective. While focused on the U.S. government, findings may also have implications for organizational security awareness programs in other sectors."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| | | 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. Information disposition and sanitization decisions occur throughout the information system life cycle. Critical factors that affect information disposition and media sanitization are decided at the start of a system's development. Initial system requirements should include hardware and software specifications as well as interconnections and data flow documents that will assist the system owner in identifying the types of ISM used in the system."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nControl AC-19 Discussion: Change “Many controls for mobile\ndevices are reflected in other controls allocated to the initial control\nbaselines as starting points for the development of security plans\nand overlays using the tailoring process."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 5)"}, {"role": "assistant", "content": "s and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n## Overview\n\n## Structure of SP 800-171\n\nSP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page). | Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Understanding the Security Requirements in SP 800-171\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n\n\n## Top 5 Frequently Asked Questions\n\n## Top five questions NIST receives on SP 800-171:\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 8)"}, {"role": "assistant", "content": "|\n| 5. Cryptographic Elements .......................................................................................\n| 5. Cryptographic Elements ....................................................................................... | 5. Cryptographic Elements ....................................................................................... | 20 |\n| 5.1 | | Cryptographic Hash Functions ...................................................................................... | 20 |\n| | 5.2 | Message Authentication Code (MAC) Algorithm......................................................... | 20 |\n| | | 5.2.1 MACTag Computation for Key Confirmation ................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n-  Custom Network-Based IPS or IDS Signature. Writing a custom IPS or IDS signature that identifies infected hosts is often a highly effective technique. Some organizations have separate IPS or IDS sensors with strong signature-writing capabilities that can be dedicated to identifying malware infections. This provides a high-quality source of information while keeping other sensors from becoming overloaded with malware alerts.\n-  Packet Sniffers and Protocol Analyzers. Configuring packet sniffers and protocol analyzers to look only for network traffic matching the characteristics of a particular malware threat can be effective at identifying infected hosts. An example of what to monitor is to look for botnet command and control communications being carried over IRC. These packet examination techniques are most helpful if most or all malware-generated network traffic attempts to pass through the same network device or a few devices."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 3)"}, {"role": "assistant", "content": "| help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n## Audience\n\n\n\n\n\nPages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality\n\n\n\nConfidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 \"Controlled Unclassified Information.\"\n\n## A Suite of Guidance\n\nNIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . \n\n\n\n\n\nNIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.13 (NIST 3.2.13)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.13. 3.2.13). 3.2.13) or non-\nexportable."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.13", "cmmc_practice_id": "AT.L2-3.2.13", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . | . . . | 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|\n| 1.1. | Purpose and Organization of This Document . . . . | 3 |\n| 2. Evaluation Criteria and Selection Process . . | . . . . . . . . | 4 |\n| 2.1. | Acceptance of the Fourth-Round Candidates . . . . | 4 |\n| 2.2. | Evaluation Criteria . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.1. Security . . . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.2.Cost and Performance . . . . . . . . . . . . . | 5 |\n| | 2.2.3.Algorithm and Implementation Characteristics | 8 |\n| 2.3. | Selection of the Candidates for Standardization . . . | 8 |\n| 3. Summary of the Fourth-Round Candidates . | . . . . . . . . | 10 |\n| 3.1. | HQC . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication NIST SP 800-140Cr2\n\n## Cryptographic Module Validation Program (CMVP)-Approved Security Functions:\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nAlexander Calis\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-140Cr2\n\n\n\n## NIST Special Publication NIST SP 800-140Cr2\n\n## Cryptographic Module Validation Program (CMVP)-Approved Security Functions:\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nAlexander Calis\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-140Cr2\n\nJuly 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nLaurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 4)"}, {"role": "assistant", "content": "osure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1. | Introduction ...................................................................................................................... | 2 |\n| 2."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Contingency Planning Guide for Federal Information Systems provide? (Part 10)"}, {"role": "assistant", "content": "Information System Contingency Planning Process................................13 | | 3.1 | Develop the Contingency Planning Policy Statement...............................................14 | Develop the Contingency Planning Policy Statement...............................................14 | | | 3.2 | Conduct the Business Impact Analysis (BIA)............................................................15 | Conduct the Business Impact Analysis (BIA)............................................................15 | | | 3.2 | 3.2.1 | Determine Business Processes and Recovery Criticality..............................16 | | | 3.2 | 3.2.2 | Identify Resource Requirements ...................................................................19 | | | 3.2 | 3.2.3 | Identify System Resource Recovery Priorities ..............................................19 | | | 3.3 | Identify Preventive Controls......................................................................................19 | Identify Preventive Controls......................................................................................19 | | | 3.4 | Create Contingency Strategies .................................................................................20 | Create Contingency Strategies .................................................................................20 | | | 3.4 | 3.4.1 | Backup and Recovery ...................................................................................20 | | | 3.4 | 3.4.2 | Backup Methods and Offsite Storage............................................................21 | | | 3.4 | 3.4.3 | Alternate Sites ...............................................................................................21 | | | 3.4 | 3.4.4 | Equipment Replacement ...............................................................................24 | | | 3.4 | 3.4.5 | Cost Considerations ......................................................................................25 | | | 3.5 | 3.4.6 Roles and Responsibilities ............................................................................26 Plan Testing, Training, and Exercises (TT&E)..........................................................27 | 3.4.6 Roles and Responsibilities ............................................................................26 Plan Testing, Training, and Exercises (TT&E)..........................................................27 | | | | | | Testing...........................................................................................................27 | | | 3.5.1 | | | | |"}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Getting Started with Awareness and Training\n\n## Family: Awareness and Training"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n- Stolen keys . If threat actors gain unauthorized access to symmetric keys used for data encryption or private keys used in public key cryptograph y, they can bypass authentication systems or gain access to other keys . If symmetric or private keys are stored without encrypt ion, they are especially at risk of being exploited to undermine the security protections that TLS provides. -  Inadequately protected keys are subject to unauthorized access by direct theft, hacking, or other means. The more data a key protects, the more severe the consequences typically are if a threat actor gains unauthorized access. -  TLS 1.3 symmetric keys are used with Authenticated Encryption with Associated Data (AEAD) algorithms-providing confidentiality and integrity for the keys. - Certificate compromise . Public keys used during authentication are often exchanged in certificates issued by a CA. A real threat exists if the issuing CA is compromised or if the registration system, persons, or process are used to obtain an unauthorized certificate in the name o f a legitimate entity to compromise the clients. - Handshake data replay . Parties to cryptographically protected communications like TLS exchange keys use protocols often called 'handshakes,' which often include multiple steps. TLS 1.3 allows the client to send data (known as 0 -RTT data) in the first flight of a handshake with a server that previously connected to the client. Replayable 0 -RTT data presents several security threats to TLS-using applications unless those applications are specifically engineered to be safe under replay (minimally, an HTTP method that is idempotent, but could require stronger conditions, such as constant -time response). Many applications do not allow 0 -RTT to avoid the replay concern (e.g., draft -ietf-netconf-overtls13). | Analytics | The discipline that applies logic and mathematics to data to provide insights for event recognition and for making response decisions."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nSCAP is a suite of specifications for expressing, exchanging, and processing security automation content. SCAP content describes what endpoint posture information to collect and how to compare this information against a desired state using implementation-neutral, standardized formats. SCAP tools use these formats to drive the collection and evaluation of posture information to determine if software vulnerabilities and misconfigurations exist on a specific managed endpoint. By identifying endpoints with these problems, organizations can make informed decisions about how to remediate these issues.\n\nNo Component-level Interoperability: SCAP v1 products that support different use cases often require similar information, such as software inventory and configuration information. While SCAP v1 supports data interoperability, control of collected posture information and evaluation remains with each tool. The lack of standardized interfaces between tools prevents transport layer interoperability, forces redundant posture information collection and evaluation that adds to system and network load, reduces modularity of solutions, and increases integration costs.\n\nBy realizing these design goals, SCAP v2 will support timely endpoint posture collection and evaluation that provides a strong foundation for enabling more advanced cyber defense capabilities and the next generation of security automation solutions."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology promotes the United States economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof-of-concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of non-national-security-related information in federal information systems. This Special Publication 800 series reports on ITL's research, guidelines, and outreach efforts in information system security and its collaborative activities with industry, government, and academic organizations. | EXECUTIVE SUMMARY.......................................................................................................... | VII |\n|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1. INTRODUCTION ........................................................................................................................ | 1 |\n| 1.1 BACKGROUND............................................................................................................................"}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | Documentation : The ability for the manufacturer and/or the manufacturer's supporting entity, to create, gather, and store information relevant to cybersecurity of the IoT device prior to customer purchase, and throughout the development of a device and its subsequent lifecycle."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| 3.4.5.1.1 Mission Impact/Strategic Value/Organization | 55 | | | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | | | | | | | 56 | | | 3.4.5.2.1 | 3.4.5.2.1 | System Size/Scale/Complexity | 56 | | | 3.4.5.2.2 | 3.4.5.2.2 | System Environment/Stability | 57 | | | 3.4.5.2.3 | 3.4.5.2.3 | Reliability/Integrity | 58 | | | 3.4.5.2.4 | 3.4.5.2.4 | Technology Integration | 59 | | 3.5 | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | 59 | | | 3.5.1 Implementation of the Scheme | 3.5.1 Implementation of the Scheme | 3.5.1 Implementation of the Scheme | 59 | | | 3.5.2 | A Simple Scoring Approach | A Simple Scoring Approach | 60 | | | 3.5.3 | A Detailed Scoring Approach | A Detailed Scoring Approach | 60 | | | 3.5.4 | Discretionary Audits | Discretionary Audits | 60 | | 3.6 | USES OF THE WORK PRIORITY SCHEME | USES"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n- NIST research and publications on trustworthy and responsible AI, including the Artificial Intelligence Risk Management Framework (AI RMF 1.0) [2], Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations [3], Towards a Standard for Identifying and Managing Bias in Artificial Intelligence [4], and the Dioptra experimentation testbed for security evaluations of machine learning algorithms [5]. - NIST's Secure Software Development Framework (SSDF) Version 1.1 [6], which is a set of fundamental, sound, and secure software development practices. It provides a common language to help facilitate communications among stakeholders, including software producers and software acquirers. The SSDF has also been used in support of EO 14028, Improving the Nation's Cybersecurity [7], to enhance software supply chain security. - NIST general cybersecurity resources, including The NIST Cybersecurity Framework (CSF) 2.0 [8], Security and Privacy Controls for Information Systems and Organizations [9], and Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations [10]. - AI model developers, AI researchers, AI system developers, and secure software practitioners from industry and government with expertise in the unique security challenges of AI models and the practices for addressing those challenges. This expertise was primarily captured through NIST's January 2024 workshop, where speakers and attendees shared suggestions for adapting secure software development practices and tasks to accommodate the unique aspects of AI model development and the software leveraging them. AI model producers, AI system producers, AI system acquirers, and others can use the SSDF to foster their communications regarding secure AI model development throughout the software development life cycle."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.2.2 Machine Operation | 4-10 |\n| | | 3. 3.2.2 Man-made Hazards | 3. 3.2.2 Machine Operation ."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 10)"}, {"role": "assistant", "content": "tiality, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies.\n[FISMA2014]\n\n## Examples of incidents include an attacker:\n\n- Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state\n\nBecause of the damage that cybersecurity incidents can inflict on organizations and their customers, business partners, and others, it is vital to respond quickly and effectively when an incident occurs. Effective implementation of incident response processes enables systematic responses to and recovery from incidents by analyzing information and taking appropriate action. This reduces cybersecurity and enterprise risks by minimizing data loss or theft, the disruption of services, and the overall impact of incidents."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nCybersecurity, Fraud, and Identity Program Integrity . . . . . . . . . . .\n\n1.3.1.\nIt is increasingly important for organizations to assess and manage digital identity\nsecurity risks, such as unauthorized access due to impersonation. As organizations\nconsult these guidelines, they should consider potential impacts to the confidentiality,\nintegrity, and availability of information and information systems that they manage, and\n\nThe exact nature of the interaction is important in determining the overall security\nof the system. Well-designed protocols protect the integrity and confidentiality of\ncommunication between the claimant and the verifier both during and after the\nauthentication and can help limit the damage done by an attacker masquerading as a\nlegitimate verifier (i.e., phishing)."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Digital Identity Guidelines provide?"}, {"role": "assistant", "content": "NIST Special Publication\nNIST SP 800-63-4\n\nDigital Identity Guidelines\n\nDavid Temoshok\nDiana Proud-Madruga\nYee-Yin Choong\nRyan Galluzzo\nSarbari Gupta\nConnie LaSalle\nNaomi Lefkovitz\nAndrew Regenscheid\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-63-4\n\n\fNIST Special Publication\nNIST SP 800-63-4\n\nDigital Identity Guidelines\n\nDavid Temoshok\nRyan Galluzzo\nConnie LaSalle\nNaomi Lefkovitz *\nApplied Cybersecurity Division\nInformation Technology Laboratory\n\nAndrew Regenscheid\nComputer Security Division\nInformation Technology Laboratory\n\nYee-Yin Choong\nInformation Access Division\nInformation Technology Laboratory\n\nDiana Proud-Madruga\nSarbari Gupta\nElectrosoft\n\n* Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-63-4\n\nJuly 2025\n\nNational Institute of Standards and Technology\nCraig Burkhardt, Acting Under Secretary for Standards and Technology and Acting NIST Director\n\nU.S. Department of Commerce\nHoward Lutnick, Secretary\n\n\fCertain equipment, instruments, software, or materials, commercial or non-commercial,\nare identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product\nor service by NIST, nor does it imply that the materials or equipment identified are\nnecessarily the best available for the purpose. There may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nAuthentication Infrastructure...............................................................................6 | 2.4 Limitation of Authentication Infrastructure...............................................................................6 | 2.4 Limitation of Authentication Infrastructure...............................................................................6 | | Network Security Appliances in the Enterprise Network Landscape ............................8 | Network Security Appliances in the Enterprise Network Landscape ............................8 | | | Cloud Access Security Broker (CASB)..........................................................................8 | Cloud Access Security Broker (CASB)..........................................................................8 | | | Enhanced Firewall Capabilities | Enhanced Firewall Capabilities | .....................................................................................8 | | Appliance-set with Integrated Functions | Appliance-set with Integrated Functions | .....................................................................10 | | Network Security Automation Tools | Network Security Automation Tools | ............................................................................11 | | 3.4.1."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. 2 OT refers to 'programmable systems or devices that interact with the physical environment (or manage devices that interact with the physical environment). These systems/devices detect or cause a direct change through the monitoring and/or control of devices, processes, and events. Examples include industrial control systems, building management systems, fire control systems, and physical access control mechanisms.' [from NIST SP 800-37 Rev. 2]\n\nOrganizations should establish and constantly maintain up-to-date software inventories for their physical and virtual computing assets, including OT, IoT, and container assets. This information could be in a single enterprise asset inventory, or it could be split among multiple resources. While a comprehensive inventory of all assets is ideal, it may be impossible to achieve, given the highly dynamic nature of assets and software. A realistic goal is to maintain a close-to-comprehensive inventory by relying on automation to constantly discover new assets and collect up-to-date information on all assets."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. All information systems process, store, or transmit some type of information. For example, information about the temperature in a remote facility collected and transmitted by a sensor to a monitoring station, location coordinates transmitted by radio to a controller on a weapons system, photographic images transmitted by a remote camera (land/satellite-based) to a server, or health IT devices transmitting patient information via a hospital network, require protection. This information can be protected by: categorizing the information to determine the impact of loss; assessing whether the processing of the information could impact individuals' privacy; and selecting and implementing controls that are applicable to the IT resources in use. Therefore, cloud-based systems, industrial/process control systems, weapons systems, cyber-physical systems, applications, IoT devices, or mobile devices/systems, do not require a separate risk management process but rather a tailored set of controls and specific implementation details determined by applying the existing RMF process."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.1.4. 3.1.4): A one-time secret obtained\n\nfrom a device or application held by the subscriber\n\n• Multi-factor OTP (Sec. 3.1.4)\n\n• Single-factor cryptographic authentication (Sec."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "s\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV.\n5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nIn addition to the above acknowledgments, a special note of thanks goes to Jeff Brewer, Jim\nFoti, and the NIST web team for their outstanding administrative support. The authors also wish\nto recognize Kristen Baldwin, Carol Bales, John Bazile, Jennifer Besceglie, Sean Brooks, Ruth\nCannatti, Kathleen Coupe, Keesha Crosby, Charles Cutshall, Ja’Nelle DeVore, Jennifer Fabius, Jim\nFenton, Hildy Ferraiolo, Ryan Galluzzo, Robin Gandhi, Mike Garcia, Paul Grassi, Marc Groman,\nMatthew Halstead, Kevin Herms, Scott Hill, Ralph Jones, Martin Kihiko, Raquel Leone, Jason\nMarsico, Kirsten Moncada, Ellen Nadeau, Elaine Newton, Michael Nieles, Michael Nussdorfer,\nTaylor Roberts, Jasmeet Seehra, Joe Stuntz, Jeff Williams, the professional staff from the NIST\nComputer Security Division and Applied Cybersecurity Division, and the representatives from\nthe Federal CIO Council, Federal CISO Council, Federal Privacy Council, Control Baseline\nInteragency Working Group, Security and Privacy Collaboration Working Group, and Federal\nPrivacy Council Risk Management Subcommittee for their ongoing contributions in helping to\nimprove the content of the publication. Finally, the authors gratefully acknowledge the\ncontributions from individuals and organizations in the public and private sectors, both\nnationally and internationally, whose insightful and constructive comments improved the\noverall quality, thoroughness, and usefulness of this publication."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nThis practice guide documents the approach the NCCoE used to develop example solutions, called builds, to support information and system integrity objectives. The approach includes a logical design, example build development, testing, security control mapping, and analysis.\n\n## 5.2 Example Solution Testing\n\nThis section presents a summary of the solution testing and results. A total of eleven tests were developed for the builds. The following information is provided for each scenario:"}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n| Executive Summary.................................................................................................................\n1 | Executive Summary................................................................................................................. 1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Introduction ...................................................................................................................... | Introduction ...................................................................................................................... | 2 |\n| | Background - Zero Trust Principles and Zero Trust Architecture................................"}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| | 4.3.2 | Recovery Procedures....................................................................................39 | | |---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| | | 4.3.3 Recovery Escalation and Notification ............................................................40 | 4.3.3 Recovery Escalation and Notification ............................................................40 | | | 4.4 | Reconstitution Phase................................................................................................41 | Reconstitution Phase................................................................................................41 | | | 4.5 | Plan Appendices.......................................................................................................42 | Plan Appendices.......................................................................................................42 | | | Chapter 5."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 5)"}, {"role": "assistant", "content": "tion for such activities and programs. This publication\nseries will report these NBS efforts to the Federal computer community as well as to\ninterested specialists in the academic and private sectors.\nThose wishing to receive\nnotices of publications in this series should complete and return the form at the end\nof this publication. National Bureau of Standards Special Publication 500-19\n\nNat. Bur. Stand. (U.S.), Spec. Publ. 500-19, 256 pages (Oct. 1977)\nCODEN: XNBSAV\n\nLibrary of Congress Catalog Card Number: 77-600045\n\nU.S. GOVERNMENT PRINTING OFFICE\nWASHINGTON: 1977\n\nFor sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, D.C. 20402\nPrice $4—Stock No. 003-003-01848-1\n\n\f. FOREWORD\n\nThe increasing use of computers by Government and private organiza-\ntions for the storage and manipulation of records of all kinds— personal\nas well as of a business nature— has placed computers and the systems in\nwhich they reside in an extremely sensitive position in our society. The\nneeds of the individual as well as Government and private organizations\nrequire that this data and their resident systems be accurate and reli-\nable. given adequate protection from threats and hazards. The establishment of\nsecure computer systems is the way in which the computer community as-\nsures the users of such systems that all of these requirements are being\nmet\n\nThese needs also require that this data and these systems be\n\nThe auditing and evaluating of computer systems for adequate secu-\n\nControls that provide computer security are of interest to both\n\nrity has been a natural outgrowth of this widening interest in this\narea. the financial and internal auditors and has been made a subject of spe-\ncial consideration by organizations such as the Institute of Internal\nAuditors, the American Institute of Certified Public Accountants, and\nthe EDP Auditors Associtation. The National Bureau of Standards, with the support of the U.S."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\nn M, Hash J (2003) Building an Information Technology Security Awareness and Training Program. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-50.\nhttps://doi.org/10.6028/NIST.SP.800-50 |\n| [WOELK] | Woelk, B (2015) The Successful Security Awareness Professional: Foundational Skills and Continuing Education Strategies. EDUCAUSE Center for Analysis and Research . Available at https://library.educause.edu/~/media/files/library/2016/8/ erb1608.pdf |"}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 4)"}, {"role": "assistant", "content": "ble at https://csrc.nist.gov/pubs/sp/800/223/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA).\n## Abstract\n\nSecurity is essential component of high-performance computing (HPC). HPC systems often differ based on the evolution of their system designs, the applications they run, and the missions they support. An HPC system may also have its own unique security requirements, follow different security guidance, and require tailored security solutions. Their complexity and uniqueness impede the sharing of security solutions and knowledge. This NIST Special Publication aims to standardize and facilitate the information and knowledge-sharing of HPC security using an HPC system reference architecture and key components as the basis of an HPC system lexicon. This publication also analyzes HPC threats, considers current HPC security postures and challenges, and makes best-practice recommendations. ## Keywords\n\nhigh-performance computing; HPC reference architecture; HPC security; HPC security posture; HPC threat analysis; security guidance. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\ns of computing platforms, including\ngeneral purpose computing systems, cyber-physical systems, cloud systems, mobile systems,\nindustrial control systems, and Internet of Things (IoT) devices.\nSafeguarding measures include\nboth security and privacy controls to protect the critical and essential operations and assets of\norganizations and the privacy of individuals. The objective is to make the systems we depend on\nmore penetration resistant to attacks, limit the damage from those attacks when they occur,\nand make the systems resilient, survivable, and protective of individuals’ privacy."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n• The provenance (e.g., manufacturer or supplier certification), health, and integrity"}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n| Purpose and Scope ........................................................................................\n| 1 |\n| | 1.2 | Changes from Previous Versions.................................................................... | 1 |\n| | 1.3 | Publication Structure......................................................................................."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n- 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. Legal experts can review incident response plans, policies, and procedures to ensure compliance with applicable laws and regulations, including the right to privacy. Legal experts can also review contracts with technology suppliers and other third parties when there are incident response implications. In addition, incident responders can seek guidance from their organization's legal department if a particular incident may have legal ramifications, such as the prosecution of a suspect, lawsuits, or situations that require a memorandum of understanding (MOU) or other binding agreement. - Public affairs and media relations. Depending on the nature and impact of an incident, it may be necessary to inform the media and, by extension, the public. Sometimes, the media learns of incidents through alternate sources (i.e., not through public affairs personnel). Having a media engagement strategy in place can greatly aid in this situation."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 3)"}, {"role": "assistant", "content": "h to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Email: piv\\_comments@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThis recommendation provides a technical guideline to use Personal Identity Verification (PIV) Cards in facility access; enabling federal agencies to operate as government-wide interoperable enterprises."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n..................................................................... | 5.4 Specific Details ...........................................................................................................\n| 29 |\n|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|\n| 6 | Functional Demonstrations...............................................................30 | Functional Demonstrations...............................................................30 | Functional Demonstrations...............................................................30 | |\n| | 6.1 | Usage Scenarios Supported ....................................................................................... | Usage Scenarios Supported ......................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 5)"}, {"role": "assistant", "content": "ochester Institute of Technology and Daren Melson for their assistance on technical issues that arose in our work. The authors would also like to thank all others who assisted with our review process.\n| Table of Contents | Table of Contents | Table of Contents |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| TABLE OFCONTENTS.............................................................................................................V | TABLE OFCONTENTS.............................................................................................................V | |\n| LIST OF FIGURES....................................................................................................................VII | LIST OF FIGURES....................................................................................................................VII | |\n| LIST OFTABLES...................................................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Contingency Planning Guide for Federal Information Systems provide? (Part 6)"}, {"role": "assistant", "content": "| | Introduction ....................................................................................................1 | | |-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | 1.1 | | Purpose.......................................................................................................................1 | | | 1.2 | | Scope..........................................................................................................................2 | | | 1.3 | | Audience.....................................................................................................................3 | | | 1.4 | Document | Structure....................................................................................................4 | | | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.1 (NIST 3.6.1)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.6.1 | Trusted Computing Group... 3.6.1 Trusted Computing Group\n\nThe technology providers for this prototype implement standards from the TCG, a not-for-profit organization formed to develop, define, and promote open, vendor-neutral, global industry standards supportive of hardware-based roots of trust for interoperable trusted computing platforms. 3.6.1."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.6.1", "cmmc_practice_id": "IR.L2-3.6.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nmay wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2022-09-08\n\n## How to Cite this NIST Technical Series Publication:\n\nFagan M, Megas KN, Watrobski P, Marron J, Cuthill B (2022) Profile of the IoT Core Baseline for Consumer IoT Products. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8425. https://doi.org/10.6028/NIST.IR.8425\n\n## Author ORCID iDs\n\nMichael Fagan: 0000-0002-1861-2609\n\nKaterina N. Megas: 0000-0002-2815-5448\n\nPaul Watrobski: 0000-0002-6449-3030\n\nJeffrey Marron: 0000-0002-7871-683X\n\nBarbara B. Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecuirty@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n- Risk Assessment: The authenticity and integrity of hardware and software are assessed prior to acquisition and use [ID.RA-09]; Critical suppliers are assessed prior to acquisition [ID.RA-10] - Improvement: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties [ID.IM-02] - Incident Recovery Plan Execution: The integrity of backups and other restoration assets is verified before using them for restoration [RC.RP-03] - Incident Recovery Communication: Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders [RC.CO-03] | Selected CSF Outcomes | Target Priority | Target Internal Practices | Selected Informative References | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------| | PR.PS, The hardware, software (e.g., firmware, operating systems, applications), and services of physical and virtual platforms are managed consistent with the organization's risk strategy to protect their confidentiality, integrity, and availability | High | 1."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. Different mobile devices have different technical and physical characteristics (e.g., size, weight, processor speed, memory capacity). Mobile devices may also use different types of expansion capabilities to provide additional functionality. Furthermore, mobile device capabilities sometimes include those of other devices such as handheld Global Positioning Systems (GPS), cameras (still and video) or personal computers. Overall, mobile devices can be classified as feature phones that are primarily simple voice and messaging communication devices or smartphones that offer more advanced capabilities and services for multimedia, similar to those of a personal computer. Table 1 highlights the general hardware characteristics of feature and smartphone models, which underscore this diversity. A UICC can contain up to three applications: SIM, USIM and CSIM. UICCs used in GSM and UMTS mobile devices use the SIM and UMTS SIM (USIM) applications, while CDMA devices use the CSIM application."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.6 (NIST 3.1.6)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.1.6. 3.1.6): Proof of possession\n\nand control via an authentication protocol of a cryptographic key held by the\nsubscriber\n\n• Multi-factor cryptographic authentication (Sec. 3.1.6)\n\n6\n\n\fNIST SP 800-63B-4\nJuly 2025\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nA biometric characteristic is not recognized as an authenticator\nby itself."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.1.6", "cmmc_practice_id": "AC.L2-3.1.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nOrganizations must exercise due diligence in managing information security and privacy risk. This is accomplished, in part, by establishing a comprehensive risk management program that uses the flexibility inherent in NIST publications to categorize systems, select and implement security and privacy controls that meet mission and business needs, assess the effectiveness of the controls, authorize the systems for operation, and continuously monitor the systems. Exercising due diligence and implementing robust and comprehensive information security and privacy risk management programs can facilitate compliance with applicable laws, regulations, executive orders, and government-wide policies. Risk management frameworks and risk management processes are essential in developing, implementing, and maintaining the protection measures necessary to address stakeholder needs and the current threats to organizational operations and assets, individuals, other organizations, and the Nation. Employing effective risk-based processes, procedures, methods, and technologies ensures that information systems and organizations have the necessary trustworthiness and resiliency to support essential mission and business functions, the U.S. critical infrastructure, and continuity of government. '…The Task Force notes that the cyber threat to U.S. critical infrastructure is outpacing efforts to reduce pervasive vulnerabilities, so that for the next decade at least the United States must lean significantly on deterrence to address the cyber threat posed by the most capable U.S. adversaries. It is clear that a more proactive and systematic approach to U.S. cyber deterrence is urgently needed…'\n\nThe security and privacy controls specified in the baselines represent the state-of-the-practice protection measures for individuals, information systems, and organizations."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 3)"}, {"role": "assistant", "content": "r operational technology (OT) systems to their information technology (IT) systems to enable and expand enterprise-wide connectivity and remote access for enhanced business processes and capabilities.\nAlthough the integration of IT and OT networks is helping manufacturers boost productivity and gain efficiencies, it has also provided malicious actors, including nation states, common criminals, and insider threats a fertile landscape where they can exploit cybersecurity vulnerabilities to compromise the integrity of ICS and ICS data to reach their end goal. The motivations behind these attacks can range from degrading manufacturing capabilities to financial gain, and causing reputational harm. Once malicious actors gain access, they can harm an organization by compromising data or system integrity, hold ICS and/or OT systems ransom, damage ICS machinery, or cause physical injury to workers. The statistics bear this out. The X-Force Threat Intelligence Index 2021 (ibm.com) stated that manufacturing was the second-most-attacked industry in 2020, up from eighth place in 2019. One particular case study illustrates the long-lasting effects and damage a single cyber attack can inflict on an organization. It was reported that a global pharmaceutical manufacturer suffered a cyber attack that caused temporary production delays at a facility making a key vaccination. More than 30,000 laptop and desktop computers, along with 7,500 servers, sat idle. Although the company claimed that its operations were back to normal within six months of the incident; at this writing, news reports stated that the organization is locked in a legal battle with its insurers and is looking to reclaim expenses that include repairing its computer networks and the costs associated with interruptions to its operations. They are seeking more than $1.3 billion in damages."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.4.4 | Content Filtering/Inspection... 3.4.4 Content Filtering/Inspection\n\nOrganizations should use content inspection and filtering technologies for stopping email-based malware threats."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.4.4", "cmmc_practice_id": "CM.L2-3.4.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines provide? (Part 8)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . . . . . . . . . . . List of Tables\nTable 1. Table 2. Table 3. Table 4. IAL Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AAL Summary . . . .\n. . . . . . . . . . . . . . . . . . . . . . . . . . . FAL Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . 33\n\n33\n\n38\n\n40\n\n41\n\n42\n\n44\n\n44\n\n45\n\n46\n\n47\n\n47\n\n50\n\n50\n\n51\n\n52\n\n54\n\n57\n\n62\n\n85\n\n85\n\n85\n\n85\n\n86\n\n35\n36\n37\n47\n\niv\n\n\fNIST SP 800-63-4\nJuly 2025\n\nDigital Identity Guidelines\n\nList of Figures\nFig. 1. Fig. 2. Fig. 3. Fig. 4. Fig. 5. Fig. 6. . . . . . Sample Identity Proofing and Enrollment Digital Identity Model\nSample Authentication Process\n. . . . . . . . . . . . . . . . . . . . . . Non-Federated Digital Identity Model Example . . . . . . . . . . . . . . Federated Digital Identity Model Example . . . . . . . . . . . . . . . . . Federated Digital Identity Model with Subscriber-Controlled Wallet Exam-\nple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High-level diagram of the Digital Identity Risk Management Process Flow\n\n11\n13\n16\n17\n\n19\n25\n\nv\n\n\fNIST SP 800-63-4\nJuly 2025\n\nPreface\n\nDigital Identity Guidelines\n\nThis publication and its companion volumes — [SP800-63A], [SP800-63B], and\n[SP800-63C] — provide technical and process guidelines to organizations for the\nimplementation of digital identity services. Acknowledgments\n\nThe authors would like to thank their fellow collaborators — Christine Abruzzi, James\nL. Fenton, Justin P. Richer, and Maria Vachino — on the current revision of this special\npublication, as well as Kerrianne Buchanan and Evelyn Petrella for their contributions\nand review. The authors would also like to acknowledge the past contributions of Donna\nF. Dodson, Elaine M. Newton, Ray A. Perlner, W. Timothy Polk, Emad A. Nabbus, Paul A. Grassi, Michael E."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 2)"}, {"role": "assistant", "content": "IST, the Information Technology Laboratory (ITL) and Communications Technology Laboratory (CTL) is also available. Zero trust related information is also found on the zero trust topic page.\nSubmit comments on this publication to: zerotrust-arch@nist.gov\n\nNational Institute of Standards and Technology Attn: Wireless Networks Division, Communications Technology Laboratory 100 Bureau Drive (Mail Stop 8920) Gaithersburg, MD 20899-8920\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Acknowledgments\n\nThe author would like to thank the members of the NIST Risk Management Framework team and the Zero Trust Architecture project team for their input and review. ## Audience\n\nThis document was written to help enterprise administrators, system operators and IT security officers understand how the various roles and tasks in the NIST Risk Management Framework (RMF) can be used when moving to a zero trust architecture. This document briefly introduces zero trust, and how the RMF process can be used in a zero trust migration process. It is assumed that the reader is familiar with the concepts of zero trust as described in NIST SP 800-207 and has had exposure to federal information security practices. ## Trademark Information\n\nAll registered trademarks or trademarks belong to their respective organizations."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of information other than national security-related information in federal information systems.\n\nCaution: What makes phishing attacks so dangerous is the way they can bypass physical and network security protections. Simply sending a phishing email to an employee of a target agency could result in the attacker gaining legitimate credentials and using them to access agency systems, potentially including CJI. Phishing attacks do not require physical access to buildings, servers, or data, nor do they require hacking or intrusion. Instead, phishing attacks rely upon tricking users into giving up valid user credentials, effectively letting the attacker through the 'front door . ' Phishing-resistant MFA is the best defense against these attacks. Although phishing resistance is an optional requirement at AAL2, it is recommended that agencies implement phishing-resistant MFA at AAL2, given the prevalence of phishing attacks."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 6)"}, {"role": "assistant", "content": "....................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1.\nInformation Decisions in the System Life Cycle..........................................................................20 |\n| 4.3.2. Determination of Security Categorization..................................................................................21 |\n| 4.3.3. Reuse of Media...........................................................................................................................22 |\n| 4.3.4. Control of Media ........................................................................................................................22 |\n| 4.3.5. Data Protection Level .................................................................................................................23 |\n| 4.3.6. Sanitization and Disposal Decision.............................................................................................23 |\n\n| 4.5.1. Sanitization Verification .............................................................................................................24 | |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|\n| 4.5.2. Sanitization Validation................................................................................................................24 | |\n| 4.7.1."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.2.1 | Determine Business Processes and Recovery Criticality... 3.2.1 Determine Business Processes and Recovery Criticality\n\nAn information system can be very complex and often supports multiple mission/business processes, resulting in different perspectives on the importance of system services or capabilities."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n| 1 INTRODUCTION.................................................................................................................\n1 | 1 INTRODUCTION................................................................................................................. 1 |\n| 2 REPORTING CONVENTIONS.......................................................................................... 2 | 2 REPORTING CONVENTIONS.......................................................................................... 2 | 2 REPORTING CONVENTIONS.......................................................................................... 2 |\n| 3 PROFESSIONAL DEMOGRAPHICS............................................................................... 3 | 3 PROFESSIONAL DEMOGRAPHICS............................................................................... 3 | 3 PROFESSIONAL DEMOGRAPHICS..............................................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 2)"}, {"role": "assistant", "content": "er statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official.\nThis publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-83 Revision 1 Natl. Inst. Stand. Technol. Spec. Publ. 800-83r1, 47 pages (July 2013)\n\nhttp://dx.doi.org/10.6028/NIST.SP.800-83r1\n\nCODEN: NSPUE2\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST Computer Security Division publications, other than the ones noted above, are available at http://csrc.nist.gov/publications."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 4-15 |\n| 5.6 | System Testing | 4-15 |\n| 5.7 6.\n| Conversion | 4-16 |\n| | INTERNAL CONTROL | 4-16 |\n| 6.1 | General | 4-16 4-16 |\n| 6.2 | Control Policies | 4-17 |\n| 6.3 7. | Control Procedures HARDWARE SUPPORT | 4-17 |\n| 7.1 | General | 4-17 |\n| 7.2 | Introduction | 4-17 |\n| 7.3 | Control Policies | 4-18 |\n| | BIBLIOGRAPHY | 4-19 |\n| 8. | | |\n| PART V: | SESSION 3 - MANAGERIAL AND ORGANIZATIONAL VULNERABILITIES AND CONTROLS - LINE LEVEL - GENERAL | 5-1 |\n| EDITOR'S 1. | NOTE INTRODUCTION | 5-2 5-3 |\n| 2."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nsecurity architecture during the specification and planning phases. The dynamic nature of the IC development process may impact the metrics that need to be developed, and a security metric that is suitable for the register-transfer level (RTL) may not be appropriate at the gate or physical level. He noted that time-to-market constraints still run on an approximately six- to nine-month cycle, but complexity has increased, leading to the need for automation in security, reliability, and testing. This increased complexity also increases the number of assets to protect and the number of potential vulnerabilities to mitigate. Regardless of what security techniques and associated security metrics are used early in the development life cycle (i.e., pre-silicon), verification is still needed during the physical layout and post-silicon stages. Finally, he identified the need for the continued development of security solutions at the material, physical, and device levels of semiconductors."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n| | 8.2 KAS1 Key Agreement...................................................................................................... | 75 |\n|----|--------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|\n| | 8.2.1 KAS1 Assumptions................................................................................................ | 75 |\n| | 8.2.2 KAS1-basic ............................................................................................................ | 76 |\n| | 8.2.3 KAS1 Key Confirmation........................................................................................ | 78 |\n| | 8.2.3.1 KAS1 | Key-Confirmation Components...................................................... 78 |\n| | 8.2.3.2 | KAS1-Party_V-confirmation ..................................................................... 78 |\n| | 8.3 KAS2 Key Agreement......................................................................................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\n0B]. In the focus groups, we found that security awareness professionals were often also assigned responsibilities for role-based training activities, for which they identified significant challenges.\nHowever, at the time, no one had taken a broader look across federal organizations to see how RBT activities were implemented and what issues organizations were experiencing. This lack of understanding hindered the development of improvements and resources for federal RBT."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST. These guidelines cover the identity proofing, authentication, and federation of users\n(e.g., employees, contractors, or private individuals) who interact with government\ninformation systems over networks. They define technical requirements in each of\nthe areas of identity proofing, enrollment, authenticators, management processes,\nauthentication protocols, federation, and related assertions. They also offer technical\nrecommendations and other informative text as helpful suggestions. The guidelines are\nnot intended to constrain the development or use of standards outside of this purpose. This publication supersedes NIST Special Publication (SP) 800-63-3. The Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n| 5.2.1 | Scenario 1: Protect Host from Malware Infection via USB..................................... | 37 |\n|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| 5.2.2 | Scenario 2: Protect Host from Malware Infection via Network Vector.................. | 37 |\n| 5.2.3 | Scenario 3: Protect Host from Malware via Remote Access Connections ............. | 39 |\n| 5.2.4 | Scenario 4: Protect Host from Unauthorized Application Installation ................... | 40 |\n| 5.2.5 | Scenario 5: Protect from Unauthorized Addition of a Device ................................ | 42 |\n| 5.2.6 | Scenario 6: Detect Unauthorized Device-to-Device Communications................... | 43 |\n| 5.2.7 | Scenario 7: Protect from Unauthorized Deletion of Files....................................... | 43 |\n| 5.2.8 | Scenario 8: Detect Unauthorized Modification of PLC Logic.................................. | 45 |\n| 5.2.9 | Scenario 9: Protect from Modification of Historian Data....................................... | 46 |\n| 5.3.1 | PR.AC-1: Identities and Credentials are Issued, Managed, Verified, Revoked, and Audited for Authorized Devices, Users, and Processes........................ | 50 |\n| 5.3.2 | PR.AC-3: Remote Access is Managed ..................................................................... | 50 |\n| 5.3.3 | PR.AC-4: Access Permissions and Authorizations are Managed, Incorporating the Principles of Least Privilege and Separation of Duties ........................."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\n|\n| 3.3 Adoption of International Standards | in SCAP v2 ............................................\n6 |\n| 4 SCAP v2 Development | Plan..................................................................................7 |\n| List of Appendices | List of Appendices |\n| Appendix A-Applications of the SCAP 2.0 Architecture.........................................9 | Appendix A-Applications of the SCAP 2.0 Architecture.........................................9 |\n| A.1 Vulnerability Assessment................................................................................ | 9 |\n| A.2 Configuration Setting Checklist | Assessment ................................................"}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n5. The CSP SHALL assess risks associated with its use of third-party services and apply\nappropriate controls, as provided in the [SP800-161] Cybersecurity Supply Chain\nRisk Management Practices for Systems and Organizations.\n\n[SP800-161] Boyen H, Smith A, Bartol N, Winkler K, Holbrook A (2022) Cybersecurity\nSupply Chain Risk Management Practices for Systems and Organizations. (National\nInstitute of Standards and Technology, Gaithersburg, MD) NIST Special Publication (SP)\nNIST SP 800-161r1. https://doi.org/10.6028/NIST.SP.800-161r1"}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| 3.4.5.1.1 Mission Impact/Strategic Value/Organization | 55 | | | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | | | | | | | 56 | | | 3.4.5.2.1 | 3.4.5.2.1 | System Size/Scale/Complexity | 56 | | | 3.4.5.2.2 | 3.4.5.2.2 | System Environment/Stability | 57 | | | 3.4.5.2.3 | 3.4.5.2.3 | Reliability/Integrity | 58 | | | 3.4.5.2.4 | 3.4.5.2.4 | Technology Integration | 59 | | 3.5 | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | 59 | | | 3.5.1 Implementation of the Scheme | 3.5.1 Implementation of the Scheme | 3.5.1 Implementation of the Scheme | 59 | | | 3.5.2 | A Simple Scoring Approach | A Simple Scoring Approach | 60 | | | 3.5.3 | A Detailed Scoring Approach | A Detailed Scoring Approach | 60 | | | 3.5.4 | Discretionary Audits | Discretionary Audits | 60 | | 3.6 | USES OF THE WORK PRIORITY SCHEME | USES"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.3.2. 3.3.2), and the purposes for collecting, using, and retaining biometrics\n(see Sec. 3.3.2."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.2.4. 3.2.4. 3.2.4) do not differentiate between identity\nproofing, authentication, and federation risks, the selected initial xALs may still be\ndifferent."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 3)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST.\nMany NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. Submit comments on this publication to: sec-cert@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe NIST Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, implementations, proofs of concept, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThe protection of Controlled Unclassified Information (CUI) in nonfederal systems and organizations is important to federal agencies and can directly impact the ability of the Federal Government to successfully carry out its assigned missions and business operations."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Developing Security Plans for Federal Information Systems provide? (Part 9)"}, {"role": "assistant", "content": "|\n| 3.10 SYSTEM ENVIRONMENT .........................................................................................................\n| 22 |\n| 3.11 SYSTEM INTERCONNECTION/INFORMATION SHARING............................................................ | 23 |\n| 3.12 LAWS, REGULATIONS, AND POLICIES AFFECTING THE SYSTEM............................................. | 23 |\n| 3.13 SECURITY CONTROL SELECTION............................................................................................ | 24 |\n\nv\n\n| 3.14 MINIMUM SECURITY CONTROLS............................................................................................ | 24 |\n|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 3.15 COMPLETION AND APPROVAL DATES .................................................................................... | 26 |\n| 3.16 ONGOING SYSTEM SECURITY PLAN MAINTENANCE .............................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 2)"}, {"role": "assistant", "content": "ory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nOrganizational cybersecurity awareness (hereafter shortened to 'security awareness') programs may experience a number of challenges, including lack of funding and staff with the appropriate knowledge and skills to manage an effective program."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 5)"}, {"role": "assistant", "content": "se IT infrastructure, this plan is called a zero trust architecture (ZTA). Enterprise administrators and system operators need to be involved in the planning and deployment for a ZTA to be successful.\nZTA planning requires input and analysis from system and workflow owners as well as professional security architects. Zero trust cannot be simply added onto an existing workflow but needs to be integrated into all aspects of the enterprise. This document introduces NIST Risk Management Framework (RMF) [2] concepts for administrators and operators who are in the process of migrating to a ZTA. The RMF lays out an approach that includes set of steps and tasks that is integrated into enterprise risk analysis, planning, development, and operations. Administrators who normally do not perform the steps and tasks detailed in the RMF may find that they will need to become familiar with them as they migrate to a ZTA. NIST Special Publication 800-207 [1] provides a conceptual framework for zero trust. While not comprehensive to all information technology this conceptual framework can be used as a tool to understand and develop a ZTA for an enterprise. This publication also provides an abstract logical architecture that can be used to map solutions and gaps upon. The abstract architecture is reproduced in figure 1 below. Figure 1: Core Zero Trust Logical Components\n\n\n\nIn this diagram, the components are depicted by logical function, and thus do not necessarily represent the composition of capabilities in operational systems. It is possible that multiple components may serve one logical function in a distributed manner, or a single solution may fulfill multiple logical roles. The roles are described in NIST SP 800-207, but are summarized below:\n\n- Policy Engine (PE): The 'brain' of a ZTA implementation and the components that ultimately evaluate resource access requests."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 10)"}, {"role": "assistant", "content": "| Implementación basada en enclaves....................................................................................................26 | | | 3.2.3 | Despliegue basado en un portal de recursos........................................................................................27 | | | 3.2.4 | Entorno de pruebas (sandbox) para aplicaciones en dispositivos........................................................28 | | | 3.3 | ALGORITMOS DE CONFIANZA .............................................................................................................................29 | | | 3.3.1 | Variaciones del algoritmo de confianza................................................................................................31 | | | 3.4 | COMPONENTES DE LA RED Y EL ENTORNO ............................................................................................................33 | | | 3.4.1 | Requisitos de la red para admitir una ZTA............................................................................................33 | | | ESCENARIOS DE IMPLEMENTACIÓN Y CASOS DE USO......................................................................................35 | ESCENARIOS DE IMPLEMENTACIÓN Y CASOS DE USO......................................................................................35 | | | 4.1 | E MPRESA CON INSTALACIONES SATÉLITES .............................................................................................................35 | | | 4.2 | E MPRESA MULTINUBE O NUBE A NUBE ................................................................................................................36 | | | 4.3 | E MPRESA CON SERVICIOS CONTRATADOS O ACCESO DE PERSONAL EXTERNO ................................................................37 | | | 4.4 | COLABORACIÓN MÁS ALLÁ DE LOS LÍMITES DE LA EMPRESA ......................................................................................39 | | | 4.5 | E MPRESA CON SERVICIOS ORIENTADOS AL PÚBLICO O AL CLIENTE ..............................................................................40 | | | 5 AMENAZAS ASOCIADAS A LA ARQUITECTURA DE CONFIANZA CERO..............................................................41 | 5 AMENAZAS ASOCIADAS A LA ARQUITECTURA DE CONFIANZA CERO..............................................................41 | | | 5.1 | S UBVERSIÓN DEL PROCESO DE DECISIONES DE LA ZTA............................................................................................41"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\nAdditional Information\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8528/final,\nincluding related content, potential updates, and document history.\n\n3.7. RYDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\nAs with the PQC Standardization Process, security was the most important factor when\nevaluating the candidate signature algorithms. NIST intends to standardize post-quantum\nsignatures for use in a wide variety of internet protocols (e.g., TLS, SSH, IKE, IPsec, OCSP,\nand DNSSEC) and other applications (e.g., certificate transparency, document signing, code\nsigning, and firmware updates)."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 7)"}, {"role": "assistant", "content": "formats. SCAP tools use these formats to drive the collection and evaluation of posture information to determine if software vulnerabilities and misconfigurations exist on a specific managed endpoint.\nBy identifying endpoints with these problems, organizations can make informed decisions about how to remediate these issues. The initial release of SCAP v2, SCAP 2.0, will enhance the range of security automation capabilities supported by SCAP. This document presents a core SCAP 2.0 architecture and key components. In addition to the architecture, several design goals for SCAP v2 are identified that, when addressed, will increase the interoperability, modularity, and usability of SCAP tools. SCAP v2 implementations will enhance the assessment of network hygiene while providing a strong standardized foundation for more advanced cyber defense techniques. To support the SCAP 2.0 architecture and SCAP v2 design goals, some existing specifications used in SCAP 1.3 need to be revised, and new standards and extensions need to be defined. The remainder of this document is organized as follows:\n\n- Section 2 presents a set of gaps in the existing SCAP v1 specifications;\n- Section 3 presents SCAP v2 design goals, an initial draft SCAP architecture, and how existing international standards can be leveraged to support the SCAP v2 design goals;\n- Section 4 describes a transition plan for migrating from SCAP v1 to SCAP v2; and\n- The appendices include additional supporting information, including how SCAP v2 can support vulnerability and configuration setting management use cases. ## 2 Gaps in SCAP v1\n\nSCAP was created as a NIST program in 2006, and the first SCAP v1 specification, SCAP 1.0, was published in 2009. Since this initial version, there have been three SCAP v1 revisions. The current revision, SCAP 1.3, was released in February 2018 as NIST Special Publication (SP) 800-126 Revision 3 [2]."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative.\nFor planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment\nperiods and provide feedback to NIST. Many NIST cybersecurity publications, other than\nthe ones noted above, are available at https://csrc.nist.gov/publications. Authority\n\nThis publication has been developed by NIST in accordance with its statutory\nresponsibilities under the Federal Information Security Modernization Act (FISMA)\nof 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible\nfor developing information security standards and guidelines, including minimum\nrequirements for federal information systems, but such standards and guidelines shall\nnot apply to national security systems without the express approval of appropriate\nfederal officials exercising policy authority over such systems. This guideline is consistent\nwith the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines\nmade mandatory and binding on federal agencies by the Secretary of Commerce\nunder statutory authority. Nor should these guidelines be interpreted as altering or\nsuperseding the existing authorities of the Secretary of Commerce, Director of the\nOMB, or any other federal official. This publication may be used by nongovernmental\norganizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\n| Executive Summary............................................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Overview of NoSQL Database Systems............................................................................................3 |\n| 2.1.1. Key-Value Model ..........................................................................................................................3 |\n| 2.1.2. Wide-Column Model....................................................................................................................4 |\n| 2.1.3. Document Model..........................................................................................................................4 |\n| 2.1.4. Graph Model.................................................................................................................................5 |\n| 2.2.1. Flexible Data Model......................................................................................................................6 |\n| 2.2.2. Horizontal Scalability....................................................................................................................6 |\n| 2.2.3. Fast Queries..................................................................................................................................6 |\n| 2.2.4. Security Deficiencies.....................................................................................................................7 |\n| 3."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.2 (NIST 3.7.2)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.7.2 Resolution\n\nThe build has several layers of defense against this use case."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.7.2", "cmmc_practice_id": "MA.L2-3.7.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\ns://doi.org/10.6028/NIST.IR.8425\n- [4] Fagan M, Megas KN, Watrobski P, Marron J, Cuthill B, Lemire D, Hoehn B, Evans C (2024) Recommended Cybersecurity Requirements for Consumer-Grade Router Products.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8425A. https://doi.org/10.6028/NIST.IR.8425A\n- [5] Fagan MJ, Megas KN, Marron JA, Brady KG, Jr., Cuthill BB, Herold R, Lemire D, Hoehn B (2021) IoT Device Cybersecurity Guidance for the Federal Government: IoT Device Cybersecurity Requirement Catalog. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-213A. https://doi.org/10.6028/NIST.SP.800-213A\n- [6] Zhang-Kennedy L and Chiasson S. (2021) \"A systematic review of multimedia tools for cybersecurity awareness and education.\" ACM Computing Surveys (CSUR) 54, no. 1, pp. 139. https://dl.acm.org/doi/abs/10.1145/3427920\n- [7] Plain Writing Act of 2010, Pub. L. No. 111-274, 124 Stat. 2861, 2862 and 2863 (2010) Available at https://www.govinfo.gov/app/details/PLAW-111publ274\n- [8] Balash DG, Ali MM, Kanich C, and Aviv AJ. (2024) \" I would not install an app with this label\": Privacy Label Impact on Risk Perception and Willingness to Install {iOS} Apps. (USENIX, Berkeley, CA) Twentieth Symposium on Usable Privacy and Security (SOUPS 2024), pp. 413-432. Available at https://www.usenix.org/system/files/soups2024balash.pdf\n- [9] Prange S, Knierim P, Knoll G, Dietz F, De Luca A, and Alt F. (2024) {'I} do (not) need that {Feature!'}-Understanding {Users'} Awareness and Control of Privacy Permissions on Android Smartphones. (USENIX, Berkeley, CA) Twentieth Symposium on Usable Privacy and Security (SOUPS 2024), pp. 453-472. Available at https://www.usenix.org/system/files/soups2024-prange.pdf\n- [10] Chen X, Doublet S, Sergeeva A, Lenzini G, Koenig V, and Distler V."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 6)"}, {"role": "assistant", "content": "---------------------------------------------------------|\n| 1. Introduction ...................................................................................................................... | 1.\nIntroduction ...................................................................................................................... | 1. Introduction ......................................................................................................................"}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Security Assessment?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | Documentation : The ability for the manufacturer and/or the manufacturer's supporting entity, to create, gather, and store information relevant to cybersecurity of the IoT device prior to customer purchase, and throughout the development of a device and its subsequent lifecycle."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Access Control on NoSQL Databases provide?"}, {"role": "assistant", "content": "\n\n## NIST Internal Report NIST IR 8504\n\n## Access Control on NoSQL Databases\n\nVincent C. Hu\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8504\n\n\n\n## NIST Internal Report\n\n## NIST IR 8504\n\n## Access Control on NoSQL Databases\n\nVincent C. Hu Computer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8504\n\nMay 2024\n\n\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 9)"}, {"role": "assistant", "content": ".....11 | |\n| 2.7.1.\nDetermine | Whether Public Disclosure is Warranted ................................................11 | |\n| 2.7.2. Produce | Advisory ....................................................................................................12 | |\n| 2.7.3."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n| Executive Summary....................................................................................................................1 | Executive Summary....................................................................................................................1 | Executive Summary....................................................................................................................1 | |------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| | Introduction .........................................................................................................................2 | Introduction .........................................................................................................................2 | | | Structural Implications of Drivers on the Enterprise Network Landscape .....................2 | Structural Implications of Drivers on the Enterprise Network Landscape .....................2 | | | Security Implications of Drivers on the Enterprise Network Landscape........................3 | Security Implications of Drivers on the Enterprise Network Landscape........................3 | | | The Need for a Security Guide......................................................................................3 | The Need for a Security Guide......................................................................................3 | | | Scope............................................................................................................................4 | Scope............................................................................................................................4 | | | Target Audience............................................................................................................4 | Target Audience............................................................................................................4 | | | Organization of This Document.....................................................................................4 | Organization of This Document.....................................................................................4 | | | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | | Limitations of Network Perimeter-based Protections ....................................................5 | Limitations of Network Perimeter-based Protections ....................................................5 | | | Limitations of VPN-based Access .................................................................................5 | Limitations of VPN-based Access .................................................................................5 | | | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 | | 2.4 Limitation of"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice PL.L2-3.15.5 (NIST 3.15.5)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.15.5. 3.15.5."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.15.5", "cmmc_practice_id": "PL.L2-3.15.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the US economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nThese activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle.\n\nThe National Strategy on Microelectronics Research has emphasized the prioritization of hardware integrity and security. In response, NIST convened its inaugural workshop, 'Enhancing Security of Devices and Components Across the Supply Chain' 1 on February 27, 2024, at the National Cybersecurity Center of Excellence (NCCoE) facility. At this workshop,"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.1.1 Functional Responsibilities | 4-9 |\n| | | Control Requirements | 4-9 4-9 |\n| | 3. 3.1.1 | Vul nerabl llties of Data and Prog ranis •••••••••••«••«•••••••«••••••••• | 6~5 |\n| | | Vulnerabilities of Terminals | 6-7 |\n| | 3. 3.1.1 The Data Base Management System as as Operating System | Implementation Issues relevant to Secure Data Management Systems 3."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nCybersecurity utility: The ability to change aspects of how the IoT product functions can help customers tailor the IoT product's functionality to their needs and goals. Customers can configure their IoT products to avoid specific threats and risk they know about based on their risk appetite. 1. Throughout the development lifecycle, the IoT product developer creates or gathers and stores information relevant to the cybersecurity of the IoT product and its product components, including :\n- a. Assumptions made during the development process and other expectations related to the IoT product, including :\n- i. Expected customers and use cases. - ii. Physical use and characteristics, including security of the location of the IoT product and its product components (e.g., a camera for use inside the home that has an off switch on the device vs. a security camera for use outside the home that does not have an off switch on the device). - iii. Network access and requirements (e.g., bandwidth requirements). - iv. Data created and handled by the IoT product. - v. Any expected data inputs and outputs (including error codes, frequency, type/form, range of acceptable values, etc.). - vi. The IoT product developer's assumed cybersecurity requirements for the IoT product. - vii. Any laws and regulations with which the IoT product and related support activities comply. - viii. Expected lifespan and anticipated cybersecurity costs related to the IoT product (e.g., price of maintenance) and length and terms of support. - b. All IoT components, including but not limited to the IoT device, that are part of the IoT product. - c. How the baseline product criteria are met by the IoT product across its product components, including which baseline product criteria are not met by IoT product components and why (e.g., the capability is not needed based on risk assessment). - d. Product design and support considerations related to the IoT product, for example :\n- i."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . | . . . | 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|\n| 1.1. | Purpose and Organization of This Document . . . . | 3 |\n| 2. Evaluation Criteria and Selection Process . . | . . . . . . . . | 4 |\n| 2.1. | Acceptance of the Fourth-Round Candidates . . . . | 4 |\n| 2.2. | Evaluation Criteria . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.1. Security . . . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.2.Cost and Performance . . . . . . . . . . . . . | 5 |\n| | 2.2.3.Algorithm and Implementation Characteristics | 8 |\n| 2.3. | Selection of the Candidates for Standardization . . . | 8 |\n| 3. Summary of the Fourth-Round Candidates . | . . . . . . . . | 10 |\n| 3.1. | HQC . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nThe Na�onal Cybersecurity Center of Excellence (NCCoE), a part of the Na�onal Ins�tute of Standards and Technology (NIST), is a collabora�ve hub where industry organiza�ons, government agencies, and academic ins�tu�ons work together to address businesses' most pressing cybersecurity issues. This public -private partnership enables the crea�on of prac�cal cybersecurity solu�ons for specific industries, as well as for broad, cross -sector technology challenges. Through consor�a under Coopera�ve Research and Development Agreements (CRADAs), including technology partners-from Fortune 50 market leaders to smaller companies specializing in informa�on technology securitythe NCCoE applies standards and best prac�ces to develop modular, adaptable example cybersecurity solu�ons using commercially available technology. The NCCoE documents these example solu�ons in the NIST Special Publica�on 1800 series, which maps capabili�es to the NIST Cyber security Framework and details the steps needed for another en�ty to re -create the example solu�on. The NCCoE was established in 2012 by NIST in partnership with the State of Maryland and Montgomery County, M aryland .\n\nThe Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register. Respondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution. We worked with:\n\nA significant constraint in meeting the visibility challenges attendant on TLS 1.3 is the lack of workable approaches that don 't change the current TLS 1.3 standard or require the development or adoption of additional or alternative standards."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Blockchain for Access Control Systems provide? (Part 5)"}, {"role": "assistant", "content": "r an access control mechanism to support the requirements of decentralization, scalability, and trust for accessing objects, all of which are challenging for traditional mechanisms.\nBlockchains are tamper-evident and tamper-resistant cryptographically linked blocks of data (which create digital ledgers) implemented in a distributed fashion (i.e., without a central repository) and usually without a central authority (i.e., a bank, company, or government). It uses replicated, shared, and synchronized digital blocks between the users of a private or public distributed computer network located in different sites or organizations. Blockchain can be utilized for access control systems as a trustable alternative for a single entity/organization or a member of a large-scale system to enforce access control policies. The robust, distributed nature of blockchain technology can overcome the limitations of traditional access control systems in a decentralized and efficient way. It is supported by the following infrastructural properties that are not included in traditional access control mechanisms unless specifically implemented:\n\n- Tamper-evident and tamper-resistant design prevents the alteration of access control data (i.e., attributes, policy rules, environment conditions, and access requests) and access control logs (i.e., request permissions and previous access control data) and reduces the probability of frauds. - The control of authorization processing is decentralized, and the storage of access control data/logs has no single point of failure, thus providing more system tolerance and availability. - The traceability of blocks allows access control data/logs and system states to be seen and tracked. - The execution of arbitrary programs in smart contracts allows for controls on distributed access control data and authorization processes."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 3)"}, {"role": "assistant", "content": "| Background: NIST Cryptographic Standards and Testing/Validation Programs ...\n1 Methodology.......................................................................................................... 2 | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology.......................................................................................................... 2 |\n| Study | Study | 2 |\n| 3.2. Data Collection............................................................................................................ | 3.2. Data Collection............................................................................................................ | ................................................................................................................. 3 |\n| 3.3. Data Analysis | 3.3. Data Analysis | .............................................................................................................."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nTitle III of the E-Government Act, entitled the Federal Information Security Management Act (FISMA), requires each federal agency to develop, document, and implement an agency-wide information security program to provide information security for the information and information systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor, or other source. System security planning is an important activity that supports the system development life cycle (SDLC) and should be updated as system events trigger the need for revision in order to accurately reflect the most current state of the system. The system security plan provides a summary of the security requirements for the information system and describes the security controls in place or planned for meeting those requirements. The plan also may reference other key security-related documents for the information system such as a risk assessment, plan of action and milestones, accreditation decision letter, privacy impact assessment, contingency plan, configuration management plan, security configuration checklists, and system interconnection agreements as appropriate. During the security certification and accreditation process, the system security plan is analyzed, updated, and accepted. The certification agent confirms that the security controls described in the system security plan are consistent with the FIPS 199 security category determined for the information system, and that the threat and vulnerability identification and initial risk determination are identified and documented in the system security plan, risk assessment, or equivalent document."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n3.3.2 Investigative Methods\n\nInvestigative methods are procedures the investigative team can apply, which require no forensic software or hardware tools."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| | | | 6-4 | |---------------|--------------------------------------------------------|---------------------------------------------------------------------------------|-----------| | 2.3 | Quantity of Terminals | Quantity of Terminals | 6-4 | | 2.4 | Terminal Characteristics | Terminal Characteristics | 6-4 | | | 2.4.1 | Portability | 6-4 6-4 | | | 2.4.2 | Bandwidth | 6-4 | | | 2.4.3 | Storage | 6-4 | | | 2.4.4 | Value | 6-4 | | | 2.4.5 | Construction, Modularity and Assembly | 6-5 | | | 2.4.6 | Intelligence | 6-5 | | | 2.4.7 | Emanations | 6-5 | | | 2.4.8 | Media | 6-5 | | 3."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nsystems). If a VDPO chooses to conduct its own vulnerability research and testing, it should forward all pertinent information to its FCB member for inclusion in an FCB vulnerability report database.\nThis capability may be used to generate vulnerability reports for internally discovered vulnerabilities (i.e., reporters within the agency) or for external reports sent directly to the ITSO closest to the affected system (i.e., reporters that notify an IT system of a vulnerability in that system). By doing this, agencies can choose to handle vulnerability disclosure duties themselves for their own systems while keeping their associated FCB member apprised of incoming reports and leveraging them for vulnerability advisory publications."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nRequirements Document | 41 | | | | 2.6.8.1 | | | | | 2.6.8.2 Functional Security and Internal Control Requirements | 2.6.8.2 Functional Security and Internal Control Requirements | 2.6.8.2 Functional Security and Internal Control Requirements | | | | | Document | Document | 42 | | | | 2.6.8.3 Data Requirements Document | 2.6.8.3 Data Requirements Document | 42 | | | | 2.6.8.4 Data Sensitivity/Criticality Description | 2.6.8.4 Data Sensitivity/Criticality Description | 42 | | | 2.6.9 | Specifications Documents | Specifications Documents | 42 | | | 2.6.9.1 | | System/Subsystem, Program and Data Base Specifications | 42 | | | 2.6.9.2 | Security and Internal Control Related Specifications | Security and Internal Control Related Specifications | 43 | | | 2.6.10 | Validation, Verification and Testing Plan and Specifications | Validation, Verification and Testing Plan and Specifications | 43 | | | 2.6.11 | User Manual | User Manual | 44 | | | 2.6.12 | Operations/Maintenance Manual | Operations/Maintenance Manual | 44 | | | 2.6.13 | Installation and Conversion Plan | Installation and Conversion Plan | 44 | | | 2.6.14 | Test Analysis and Security Evaluation Report | Test Analysis and"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 4)"}, {"role": "assistant", "content": "urers and is looking to reclaim expenses that include repairing its computer networks and the costs associated with interruptions to its operations. They are seeking more than $1.3 billion in damages.\nTo address the cybersecurity challenges facing the manufacturing sector, the National Institute of Standards and Technology's (NIST's) National Cybersecurity Center of Excellence (NCCoE) launched this project in collaboration with NIST's Engineering Laboratory (EL) and cybersecurity technology providers. Together, we have built example solutions that manufacturing organizations can use to mitigate ICS integrity risks, strengthen the cybersecurity of OT systems, and protect the data that these systems process. ## CHALLENGE\n\nThe manufacturing industry is critical to the economic well-being of the nation, and is constantly seeking ways to modernize its systems, boost productivity, and raise efficiency. To meet these goals, manufacturers are modernizing their OT systems by making them more interconnected and integrated with other IT systems and introducing automated methods to strengthen their overall OT asset management capabilities. As OT and IT systems become increasingly interconnected, manufacturers have become a major target of more widespread and sophisticated cybersecurity attacks, which can disrupt these processes and\n\ncause damage to equipment and/or injuries to workers. Furthermore, these incidents could significantly impact productivity and raise operating costs, depending on the extent of a cyber attack."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n...........13 |\n| 3.2.1. MFA Users ..................................................................................................................................13 |\n| 3.2.2.\nIT Support Staff...........................................................................................................................14 |\n| 3.2.3. Other Agencies ...........................................................................................................................14 |\n| 3.2.4. Procurement Teams...................................................................................................................14 |\n| 3.2.5. Compliance Teams .....................................................................................................................15 |\n| 3.2.6. Legal Teams................................................................................................................................15 |\n| 3.2.7. Technology Vendors...................................................................................................................15 |\n| 3.4.1. Local Agency MFA Architectures................................................................................................17 |\n| 3.4.2. State MFA Deployments.............................................................................................................21 |\n| 3.4.3. Implementing MFA with VPNs ...................................................................................................25 |\n| 4. Key Takeaways.............................................................................................................................29 |\n| References.......................................................................................................................................31 |\n| Appendix A."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nThreat actors may seek to compromise various components of the SDLC process, including source code, testing environments, development tools, and build pipelines. They may introduce vulnerabilities, malware, or stolen credentials to gain access to other systems or compromise sensitive data. Such threats can result in financial losses, reputational damage, physical damage and legal consequences. DevSecOps is an agile paradigm used for the development and deployment of cloud-native repositories (e.g., first-party or in-house, third parties or open-source/commercial) to perform tasks or activities, such as building, packaging, testing, and deploying. applications. This paradigm consists of a series of stages that takes code from variously sourced In this document, the term 'artifacts' denotes source code as well as the things generated from it, such as builds and packages. Each of the artifacts is associated with an owner. The logical containers that hold these artifacts are called repositories. The build process is based on application logic-driven dependencies and generates builds using many individual source-code artifacts that are stored in build repositories. The build artifacts are tested and used to generate packages whose artifacts are then stored in designated repositories and scanned before being deployed in testing or production environments. These stages and the various tasks performed at each stage are collectively called CI/CD pipelines. In other words, CI/CD pipelines use processes called workflows to transform source artifacts to deployable packages in production environments. A common approach to SSC security in all of these workflows is to generate as much provenance data as possible. Provenance data are associated with the chronology of the origin, development, ownership, location, and changes to a system or system component, including the personnel and processes that enabled those changes or modifications."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nesses at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems.\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThe system component inventory includes system-specific information required for component accountability and to provide support to identify, control, monitor, and verify configuration items in accordance with the authoritative source. The information necessary for effective accountability of system components includes the system name, hardware and software component owners, hardware inventory specifications, software license information, software version numbers, andfor networked components-the machine names and network addresses. Inventory specifications include the manufacturer, supplier information, component type, date of receipt, cost, model, serial number, and physical location. Organizations also use automated mechanisms to implement and maintain authoritative (i.e., up-to-date, complete, accurate, and available) baseline configurations for systems that include hardware and software inventory tools, configuration management tools, and network management tools. Tools can be used to track version numbers on operating systems, applications, types of software installed, and current patch levels.\n\n- 3.11.6e Assess, respond to, and monitor supply chain risks associated with organizational systems and system components.\n\nSupply chain events include disruption, use of defective components, insertion of counterfeits, theft, malicious development practices, improper delivery practices, and insertion of malicious code. These events can have a significant impact on a system and its information and, therefore, can also adversely impact organizational operations (i.e., mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation. The supply chain-related events may be unintentional or malicious and can occur at any point during the system life cycle. An analysis of supply chain risk can help an organization identify systems or components for which additional supply chain risk mitigations are required."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Access Control on NoSQL Databases provide? (Part 4)"}, {"role": "assistant", "content": "publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication.\n## Table of Contents\n\n| Executive Summary............................................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Overview of NoSQL Database Systems............................................................................................3 |\n| 2.1.1. Key-Value Model ..........................................................................................................................3 |\n| 2.1.2. Wide-Column Model....................................................................................................................4 |\n| 2.1.3. Document Model..........................................................................................................................4 |\n| 2.1.4. Graph Model.................................................................................................................................5 |\n| 2.2.1. Flexible Data Model......................................................................................................................6 |\n| 2.2.2. Horizontal Scalability....................................................................................................................6 |\n| 2.2.3. Fast Queries..................................................................................................................................6 |\n| 2.2.4."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n| 1. | Introduction........................................................................................................................... 1 |\n|------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | Background....................................................................................................................1 |\n| 1.2 | Purpose and Scope.........................................................................................................1 |\n| 2. | Characteristics of PIV Implementations ............................................................................ 3 |\n| 2.1 | Benefits of the Complete Implementation.....................................................................3 |\n| 2.2 | Qualities of the Complete Implementation....................................................................4 |\n| 2.3 | Interoperability Qualities...............................................................................................5 |\n| 2.4 | Infrastructure Requirements ..........................................................................................6 |\n| 3. | Threat Environment............................................................................................................."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| ^ | 3.2.2 | Size of Review Task | Size of Review Task | 49 | |-----------|------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------|-----------| | 3.3 | BACKGROUND ON THE METHODOLOGY | BACKGROUND ON THE METHODOLOGY | BACKGROUND ON THE METHODOLOGY | 49 | | | 3.3.1 | The Invitational Workshop | The Invitational Workshop | 49 | | | 3.3.2 | Workshop Points of Agreement | Workshop Points of Agreement | 49 | | 3.4 | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | 50 | | | 3.4.1 | Assumptions and Caveats | Assumptions and Caveats | 50 | | | 3.4.2 | Audit Planning/Prioritization Process | Audit Planning/Prioritization Process | 51 | | | 3.4.3 | Non-Discretionary Audits | Non-Discretionary Audits | 51 | | | 3.4.4 | Risk Evaluation Levels and Dimensions | Risk Evaluation Levels and Dimensions | 53 | | | 3.4.5 | Two Level Work Priority Dimensions/Characteristics | Two Level Work Priority Dimensions/Characteristics | 54 | | | 3.4.5.1 Level I: | 3.4.5.1 Level I: | 3.4.5.1 Level I: | .....55 | | | 3.4.5.1.1 Mission Impact/Strategic Value/Organization | 3.4.5.1.1 Mission Impact/Strategic Value/Organization"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.2.1. 3.2.1. 3.2.1."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\ned and available to the enterprise. This step also does not change in a zero trust planning process. The baseline controls for LOW, MODERATE and HIGH-impact systems are listed in NIST SP 800-53B [10].\nAdditional controls may be added or removed as part of control tailoring, adjusting the controls to manage risk to the resource, its known attack surface, and its position in the workflow. The use of control overlays 6 may assist in this, but the overlay should not be considered immutable and should be tailored for the unique resource, workflow, and proposed or added ZTA components. The planners should also consider what controls will be met by the PEP, and what may need to be implemented in the resource itself. As with the CATEGORIZE step, the resource owners and owners of the workflows that use the resource may provide valuable input in this step. As zero trust places importance on continuous monitoring and updating of security postures, cybersecurity architects and administrators need to develop a comprehensive monitoring process"}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process.\nThe baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . A separate guideline, SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, provides specific guidelines that facilitate periodic assessment of security controls to ensure that controls have been implemented correctly, are operating as intended, and are meeting the organization's security requirements. ## 2 NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)\n\nNIST SP 800-39, Managing Information Security Risk , defines risk management as 'the program and supporting processes to manage information security risk to organizational operations (including mission, functions, and reputation), organizational assets, individuals, other organizations, and the Nation'. To integrate the risk management process throughout an organization and to address its mission and business concerns, a three-tiered approach is employed. The process is carried out across three tiers with the objective of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n| 1. Introduction...................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. HPC System Reference Architecture and Main Components ............................................................2 |\n| 2.1.1. Components of the High-Performance Computing Zone.............................................................3 |\n| 2.1.2. Components of the Data Storage Zone........................................................................................4 |\n| 2.1.3. Parallel File System.......................................................................................................................4 |\n| 2.1.4. Archival and Campaign Storage....................................................................................................5 |\n| 2.1.5. Burst Buffer ..................................................................................................................................5 |\n| 2.1.6. Components of the Access Zone..................................................................................................6 |\n| 2.1.7. Components of the Management Zone.......................................................................................6 |\n| 2.1.8. General Architecture and Characteristics ....................................................................................6 |\n| 2.1.9. Basic Services................................................................................................................................7 |\n| 2.1.10."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nderal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?\n| The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. |\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| | being consumed as part of AI model training, testing, fine-tuning, and aligning."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nIMDs are tiny computing platforms that run firmware in extremely power constrained environments. They offer data storage for static data (such as device information), relatively static data (such as patient identification, medical condition, therapy configuration) and dynamic data (such as recent patient readings and audit logs). IMDs offer wireless access for read and write operations to the data on the IMD (including the firmware) to a variety of stakeholders and roles.\n\nSome of the threats to wireless IMDs include device reprogramming, data extraction, data tampering, repeated access attempts and data flooding. Vulnerabilities include unsecured communication channels, inadequate authentication and access control, weak audit mechanisms and meager storage. The resulting risks include patient safety compromise resulting from firmware malfunction or therapy misconfiguration, device unavailability due to battery power depletion, patient privacy loss due to data leakage to unauthorized parties, and inappropriate medical follow-up due to tampering of patient readings. While some cyber threats may be unintentional, various motivations exist for deliberate cyber attacks, such as patient information gathering, negative impact to patient health status, ego satisfaction of the attacker, as well as gaining competitive advantage over another vendor through negative press.\n\nIdentification of the various data types within an IMD is an essential step in analyzing the security and privacy risks of such devices. Possible data types include firmware (though technically not 'data'), device identification data, patient identification and health condition data, therapy configuration data, patient readings, audit log data, and other data."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Software Supply Chain (SSC) -Definition and Model .....................................................................4 |\n| 2.4.1. Software Supply Chain Defects ....................................................................................................6 |\n| 2.4.2. Software Supply Chain Attacks.....................................................................................................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1. Developer Environment ...............................................................................................................8 |\n| 3.1.2. Threat Actors................................................................................................................................8 |\n| 3.1.3. Attack Vectors ..............................................................................................................................9 |\n| 3.1.4. Attack Targets (Assets).................................................................................................................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 9)"}, {"role": "assistant", "content": "| 2 | | | 2.1 | Forms of Malware......................................................................................................2 | | | 2.2 | | Attacker Tools | ...........................................................................................................3 | | | 2.3 | The Nature of Today's Malware.................................................................................4 | | | 3."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nshould be part of a comprehensive OT/ICS security plan that addresses the NIST Cybersecurity Framework Protect and Detect functions.\n\nThe staging environment was configured without the Dispel multifactor authentication (MFA) settings because personal identity verification (PIV) cards were not available as a supported mechanism, and the lab environment did not support authenticator application or security keys. However, MFA is very important for implementation and is strongly encouraged when planning the implementation. For this effort, to reduce the risk of not having the MFA implementation, NCCoE worked with Dispel to limit access to the cloud infrastructure and the VDI instances to only approved source IP addresses. The additional protection of restricting access to the cloud infrastructure and VDI instances is also encouraged to reduce the risks associated with the internet-accessible web and RDP service s."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n3.2.4. 3.2.4."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nDEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..................................................................................\n7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................"}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n## Recommendations for Federal Vulnerability Disclosure Guidelines\n\n## Recommendations for Federal Vulnerability Disclosure Guidelines\n\nSchaffer K, Mell P, Trinh H, Van Wyk I (2023) Recommendations for Federal Vulnerability Disclosure Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST (Special Publication) NIST SP 800-216. https://doi.org/10.6028/NIST.SP.800-216"}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n| Technology Partner/Collaborator | Build Involvement | |-----------------------------------|--------------------------------------------------------------------------------------------------------| | Symantec Corporation | Symantec Information Centric Analytics v6.5.2 Symantec Security Analytics v8.0.1 | | Cisco Systems | Cisco Identity Services Engine v2.4, Cisco Advanced Malware Protection v5.4, Cisco Stealthwatch v7.0.0 | | Glasswall Government Solutions | Glasswall FileTrust Advanced Threat Protection (ATP) for Email v6.90.2.5 | | Tripwire | Tripwire Log Center v7.3.1, Tripwire Enterprise v8.7 | | Micro Focus | Micro Focus ArcSight Enterprise Security Manager v7.0 Patch 2 | | Semperis | Semperis Directory Services Protector v2.7 | | 1 | Summary..............................................................................................1 | Summary..............................................................................................1 | |-----|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | 1.2 | Solution..........................................................................................................................2 | | | 1.3 | Benefits..........................................................................................................................3 | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | 2.1 | Typographic Conventions..............................................................................................5 | | 3 | Approach .............................................................................................6 | Approach .............................................................................................6 | | | 3.1 | Audience........................................................................................................................6 | | | 3.2 | Scope .............................................................................................................................6 | | | 3.3 | Assumptions..................................................................................................................7 | | | 3.4 | Risk Assessment ............................................................................................................7 | | | 3.4.1 | Risk................................................................................................................................8 | | | | 3.4.2 Security Control Map....................................................................................................9 | | | 3.5 Technologies................................................................................................................13 | 3.5 Technologies................................................................................................................13 | | 4 | Architecture .......................................................................................16"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\nABE provides confidentiality and data integrity when used in a public environment with a large scope (e.g., cloud) of users. However, relying only on user-specified attributes may create various security issues from the perspectives of key management processes and intentional threats or attacks.\n\nIntegrity: If an ABE system is outsourced, it requires trust so that the decrypted ciphertext is a legitimate message based on legitimate user attributes. Additionally, the message uploaded to the resource provider can be falsified, and it is unknown whether the value calculated by the\n\nResearchers are currently working on blockchain fundamentals and customizing blockchainbased ABE models for IoT applications to provide privacy and minimize computational overhead. For example, [QYLPYH] describes the use of a lightweight blockchain ABE to outsource decryption based on the blockchain, which can be extended to effectively reduce the burden of encryption computation on the user side. Blockchain technology can also provide integrity (i.e., the secret key does not contain specific information about users who may share their secret keys with other users) and the non-repudiation of data, as well as prevent the leaking of sensitive information from the ABE access structure [WZZGZZ]."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements\n\nNIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-07-21\n\n## How to Cite this NIST Technical Series Publication\n\nFagan M, Haney J, Eliot D, Cuthill B, Rigopoulos K (2025) Report on the Design-A-Thon: Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8558. https://doi.org/10.6028/NIST.IR.8558\n\n## Author ORCID iDs\n\nMichael Fagan: 0000-0002-1861-2609 Julie Haney: 0000-0002-6017-9693 Daniel Eliot: 0009-0006-3078-555X Barbara B. Cuthill: 0000-0002-2588-6165 Kristina Rigopoulos: 0000-0001-5223-8801\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory\n\n100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8558/final, including related content, potential updates, and document history. ## All comments are subject to release under the Freedom of Information Act (FOIA)."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.4.2 | Vulnerabilities... 3.4.2 | Test Results... 3.4.2 Vulnerabilities\n\nA vulnerability as defined in NISTIR 7298, Glossary of Key Information Security Terms [12] is a 'weakness in an information system, system security procedures, internal controls, or implementation that could be exploited by a threat source."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. | Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nDigital Identity Guidelines\n\nDigital Identity Guidelines\n\nTemoshok D, Galluzzo R, LaSalle C, Lefkovitz N, Regenscheid A, Choong YY, Proud-\nMadruga D, Gupta S (2025) Digital Identity Guidelines. (National Institute of Standards\nand Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-63-4.\nhttps://doi.org/10.6028/NIST.SP.800-63-4"}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.2.2\n\nClassification System\n\nOne important requirement for maintaining access\n\n7-25\n\n\fcontrol and other DP security controls is the adequacy of\nthe system for identifying sensitive resources."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759:\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nCalis A (2023) Cryptographic Module Validation Program (CMVP)-Approved Security Functions: CMVP Validation Authority Updates to ISO/IEC 24759. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-140Cr2. https://doi.org/10.6028/NIST.SP.800-140Cr2"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nost commonly used malware threat mitigation technical control is antivirus software; organizations should deploy antivirus software on all hosts for which satisfactory antivirus software is available.\nAdditional technical controls that are helpful for malware threat mitigation include intrusion prevention systems, firewalls, content filtering and inspection, and application whitelisting. The System and Information Integrity family of security controls in NIST Special Publication (SP) 800-53, Recommended Security Controls for Federal Information Systems and Organizations , recommends having malware protection mechanisms on various types of hosts, including workstations, servers, mobile computing devices, firewalls, email servers, web servers, and remote access servers."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nTable summarizes the criteria that can be employed to determine which type of alternate site meets the organization's requirements. Sites should be analyzed further by the organization, including considerations given to business impacts and downtime defined in the BIA. As sites are evaluated, the ISCP Coordinator should ensure that the system's security, management, operational, and technical controls are compatible with the prospective site. Such controls may include firewalls, physical access controls, and personnel security requirements of the staff supporting the site. - ƒ Obtaining authorization to access damaged facilities and/or geographic area;\n- ƒ Notifying internal and external business partners associated with the system;\n- ƒ Obtaining necessary office supplies and work space;\n- ƒ Obtaining and installing necessary hardware components;\n- ƒ Obtaining and loading backup media;\n- ƒ Restoring critical operating system and application software;\n- ƒ Restoring system data to a known state;\n- ƒ Testing system functionality including security controls;\n- ƒ Connecting system to network or other external systems; and\n- ƒ Operating alternate equipment successfully. At the successful completion of the validation testing, ISCP personnel will be prepared to declare that reconstitution efforts are complete and that the system is operating normally. This declaration may be made in a recovery/reconstitution log or other documentation of reconstitution activities. The ISCP Coordinator, in coordination with the Information System Owner, ISSO, SAISO and with the concurrence of the Authorizing Official, must determine if the system has undergone significant change and will require reassessment and reauthorization. 34 The utilization of a continuous monitoring strategy/program can guide the scope of the reauthorization to focus on those environment/facility controls and any other controls which would be impacted by the reconstitution efforts."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.3.4)."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "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.\nParameters 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. This report documents the first SOUPS Design-A-Thon, which was held on August 11 th , 2024, and focused on Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness. In total, eight individuals participated in the event, forming three teams. The teams each selected a mock product based on a selection of five Product Data Cards developed by the NIST team. Participants used the information on the Product Data Cards to develop a strategy for cybersecurity education and awareness for the product. Teams were successful in planning strategies that utilize novel techniques and sound best practices. From the participant teams' designs, the NIST team identified highlights and takeaways that are further elaborated in this report. | 1. Introduction.....................................................................................................................................1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\naccess control; attribute-based access control; attribute-based encryption; authorization; encryptions; identity-based encryption; public-key encryption. | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1. | Introduction ...................................................................................................................... | 2 |\n| 2. | Fundamental Theories ..................................................................................................... | 4 |\n| 2.1. | Elliptic Curve | .............................................................................................................. 4 |\n| 2.2. | Elliptic-Curve Cryptography ........................................................................................"}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 10)"}, {"role": "assistant", "content": "................................................................ 4 | 3.1.1 Security Awareness Roles and Percentage of Time....................................................\n3 3.1.2 Years of Security Awareness Experience.................................................................... 4 |\n| 3.2 WORK ROLES....................................................................................................................... 5 | 3.2 WORK ROLES....................................................................................................................... 5 | 3.2 WORK ROLES....................................................................................................................... 5 |\n| 3.2.1 Job Classifications...................................................................................................... 5 3.2.2 NICE Framework Work Roles .................................................................................... 7 | 3.2.1 Job Classifications...................................................................................................... 5 3.2.2 NICE Framework Work Roles .................................................................................... 7 | 3.2.1 Job Classifications...................................................................................................... 5 3.2.2 NICE Framework Work Roles .................................................................................... 7 |\n| 3.3 PROFESSIONAL BACKGROUNDS ..........................................................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ordered t-way Combinations for Testing State-based Systems provide? (Part 6)"}, {"role": "assistant", "content": "vers three 2-event orders: a followed by b and b followed by c , and a followed by c ). Denoting event a eventually followed by event b , possibly with other events interleaved, is written as a *→ b .\nConsider the notion of an s -order of t -way combinations of the input parameters as a series of rows of test data that contain a particular set of t-way combinations in a specified order, with possibly interleaved rows. Definition 1. The notation a *→ b denotes the presence of combination a eventually followed by combination b , possibly with other rows interleaved. A combination order c 1 *→ c 2 *→ … *→ cs of s sequence of t -way combinations, abbreviated s -order, is a set of t -way combinations in s rows. Each ci is a t -way combination of parameter values. Example. Fig. 2 shows combination order p 0 p 1 = ad *→ p 0 p 3 = ba *→ p 1 p 3 = ab , which is a 3-order of 2way combinations . Thus, the term ordered combinations refers to combinations in a row followed by combinations in rows below. Fig. 2. Ordered combinations\n\n\n\n| Test | p0 | p1 | p2 | p3 |\n|--------|------|------|------|------|\n| 1 | a | d | b | c |\n| 2 | b | a | c | d |\n| 3 | b | d | c | a |\n| 4 | c | a | b | d |\n| 5 | c | d | b | a |\n| 6 | d | a | c | b |\n\nWhen all s -orders of t -way combinations of the input parameters have been covered, it is referred to as an ordered combination cover (OCC) . For the OCCs, the combination orders are treated across rows (i.e., a combination in a row followed by combinations in rows below). A t-way combination occurs in some row and is eventually followed by other t-way combinations in other rows. For three Boolean parameters a, b, c in Fig. 3, ab =00 is followed by ab =10 ab =00 ac =11 ac =01 bc =01 ( ac =01 and bc =01 are also followed by this group). Fig 3."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n'We depend on pulling in other resources to help with [the security awareness program], and that, again, goes back to being tied to the threat team and to the policy team.' (D03)"}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CA.L2-3.12.1 (NIST 3.12.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.12.1 of [SP800-63C]."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.12.1", "cmmc_practice_id": "CA.L2-3.12.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nperformed. | PE-20 | 5 |\n| Detect (DE) | Detection Processes (DE.DP) | DE.DP-2: Detection activities comply with all applicable requirements.\n| SR-9 | 1 |\n| NA | NA | NA | SR-10 | 5 |\n| NA | NA | NA | SR-11 | 1,3 |\n| NA | NA | NA | AU-10 | 4 |"}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication contains comprehensive updates to the Risk Management Framework . The updates include an alignment with the constructs in the NIST Cybersecurity Framework; the integration of privacy risk management processes; an alignment with system life cycle security engineering processes; and the incorporation of supply chain risk management processes. Organizations can use the frameworks and processes in a complementary manner within the RMF to effectively manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. Revision 2 includes a set of organization-wide RMF tasks that are designed to prepare information system owners to conduct system-level risk management activities. The intent is to increase the effectiveness, efficiency, and cost-effectiveness of the RMF by establishing a closer connection to the organization's missions and business functions and improving the communications among senior leaders, managers, and operational personnel. * Note: The publication pertains to information systems, which are discrete sets of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information, whether such information is in digital or non-digital form. Information resources include information and related resources, such as personnel, equipment, funds, and information technology. Therefore, information systems may or may not include hardware, firmware, and software. This publication is intended to help organizations manage security and privacy risk, and to satisfy the requirements in the Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | SP 800- | Security |\n|--------------------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------|---------------------------|\n| Function | Category | Subcategory | 53 R5 | Characteristics Addressed |\n| | | software, firmware, and information integrity. | | |\n| | | PR.DS-8: Integrity checking mechanisms are used to verify hardware integrity. | SA-10 | 4, 5 |\n| | Protective Technology (PR.PT) | PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy. | AU-2 | 5 |\n| Detect (DE) | Security Continuous Monitoring (DE.CM) | DE.CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed. | PE-20 | 5 |\n| Detect (DE) | Detection Processes (DE.DP) | DE.DP-2: Detection activities comply with all applicable requirements."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n1. Concept: Concept stage is the birthplace of an Integrated Circuit (IC). At this stage, the goals and purpose of an integrated circuit (IC) are formulated, and the scope and target of a hardware component are discussed. Customers, the design, planning, finance teams, and other key stakeholders are involved at this stage. 2. Design: Design stage gives a form to the ideas generated in the concept stage. This is the stage where prototypes of the concept are created with the help of different Computer Aided Design (CAD) tools and analysis of whether the goals identified during the concept stage are met. This stage also includes the use of third-party software and hardware prototyping. 3. Integration: Integration is the stage where different design components from designers and third parties are integrated together. This phase is crucial since many design elements already have tested solutions, so not everything needs to be created from the ground up. It is more feasible to purchase these solutions from third parties and integrate them into the design. 4. Manufacturing: After the IC's design is finished, the manufacturing phase begins. This stage includes several processes, including fabrication and packaging. Due to the high cost of building and maintaining manufacturing facilities, many design houses are fabless and outsource their designs to manufacturers located elsewhere. 5. Testing: Testing is the stage at which manufactured Integrated Circuits (ICs) are tested to ensure that they perform properly. Following the completion of fabrication, each IC undergoes testing. An IC's functionalities are tested here to make sure they adhere to design specifications. 6. Provisioning: Provisioning is the stage where standard and sensitive data are loaded into the manufactured IC. Standard data are generic and mostly available open source, but the sensitive data are anything whose disclosure would compromise IP or security."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. This publication offers general guidance and is provided for informational purposes. This publication should not be construed or relied upon as legal advice or guidance. This document does not modify the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Health Information Technology for Economic and Clinical Health (HITECH) Act, or any other federal law or regulation."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.5.3\n3. 3.5.3\n\nPrepare and Perform Test Procedures\n\nThe preparing and performing of the test procedures are themselves\n\nThe controls must ensure that the programs and pro-\n\nsubject to controls."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 3)"}, {"role": "assistant", "content": "efore the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\n- Policy Engine (PE): The 'brain' of a ZTA implementation and the components that ultimately evaluate resource access requests. The PE relies on information from the various data sources (access logs, threat intelligence, endpoint health, and network ID authentication, etc.)\n- Policy Administrator (PA): The executor function of the PE. The PA's role is to establish, maintain and ultimately terminate sessions 1 in the data plane between the subject and the resource. The PA, PE and PEP communicate on a logically (or physically) separate set of channels called the control plane. The control plane is used to establish and configure the data plane channels used to send application traffic.\n- Policy Enforcement Point (PEP): The component that applications, endpoints, etc. will interact with to be granted access permission to a resource. The PEP is responsible for gathering information for the PE and following the instructions issued by the PA to establish and terminate communication sessions. All data plane communications between enterprise resources must be managed by a PEP.\n- Information feeds (left and right ): Sometimes called policy information points (PIPs). These are not 'core' functional ZTA components themselves but used to support the PE. These feeds include the set of codified policies, identity and endpoint attributes, environmental factors and historical data used by the PE to generate resource access decisions.\n\nZero trust could be summarized as a set of principles (or tenets) used to plan and implement an IT architecture. The tenets below were originally defined in NIST SP 800-207 [1] but are repeated and expanded upon here and grouped as relating to network identity, endpoint health, or data flows. Some discussion of the tenets is included, and some considerations that planners should keep in mind when developing a zero trust architecture.\n\n## 1.1.1 Tenets that Deal with Network Identity Governance"}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST 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.\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n8 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products).\nSince many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 10)"}, {"role": "assistant", "content": "and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance.\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement. Tailoring: The process by which control baselines are modified to achieve certain organizational goals and objectives. Definitions provided are intended as plain language. Review the NIST Glossary for official NIST definitions. Determine if your business has CUI. ## General Tips for Getting Started with NIST SP 800-171\n\nEveryone will have different approaches to getting started, but here are a few tips to get you started down the right path:\n\nUnderstand current (or future) legal, regulatory, or contractual requirements for protecting CUI. The federal agency is responsible for communicating what CUI the business is responsible for protecting as part of the contractual arrangement. If there are questions, reach out to the contracting officer. The business may also have additional compliance requirements beyond SP 800-171. If so, an initial task might be to understand where the requirements overlap and where they differ. With that information, the business can begin addressing requirements that meet multiple compliance requirements. Understand how CUI flows into, within, and out of the business. \n\nInventorying what systems or components the business has, and how the data flows into, within, and out of those systems or components, helps practitioners understand the scope of applicability of SP 800-171 security requirements to business systems. \n\nScope and Applicability of SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 3. | POLICY | AND CONTROL STANDARDS | 3-6 |\n|------|----------------|-------------------------------------------------------------------------------------------------------|-----------|\n| | 3.1 | General | 3-6 |\n| | 3.2 | Assessing Security Safeguards | 3-6 |\n| | 3.3 | Establishing Control Standards | 3-6 |\n| | 3.4 | Require a Plan to Implement Controls | 3-7 |\n| | 3.5 | Establish Personnel Security Policies | 3-7 |\n| 4. | ALLOCATE | RESOURCES | 3-7 |\n| | 4.1 | General | 3-7 3-8 |\n| 5. | REPORT | ON SECURITY | |\n| | 5.1 | General | 3-8 |\n| Fig. | 1 | Responsibilities and Duties to Provide Security for Data Processing System .."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities. The information in this publication, including\nconcepts, practices, and methodologies may be used by federal agencies even before the completion of\nsuch companion publications. Thus, until each publication is completed, current requirements, guidelines,\nand procedures, where they exist, remain operative. For planning and transition purposes, federal\nagencies may wish to closely follow the development of these new publications by NIST. SP 800-53A provides guidance on assessing controls in information security program plans,\nprivacy program plans, system security plans, and privacy plans. Where the guidance refers to all\nplans listed above, the term “security and privacy plans” is used. If the guidance is specific to a\nsingle type of plan (e.g., system security plan), the specific type of plan is specified. CHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n|\n| Protect (PR) | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-6: Identities are proofed and bound to credentials and asserted in interactions.\n| IA-4 | 1 |\n| | Data Security (PR.DS) | PR.DS-6: Integrity checking mechanisms are used to verify | SI-7 | 4, 5 |"}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n- A built-in infrastructure for (a) providing service identities, (b) service discovery, and (c) external policy-based authorization engines in which policies incorporate contextual variables. Policies pertain to service-to-service and user-to-resource authentications and authorizations and ensure application integrity and confidentiality. These policies generally are expressed through a structure called access control. Some examples of access control models include: Next Generation Access Control (NGAC) model, and Attribute-based access control (ABAC) model.\n- Code for performing network-related functions (e.g., traffic routing) and for ensuring network resiliency through functions such as retries, timeouts, blue-green deployments, and circuit breaking.\n- More details on the container orchestration platform with an integrated service mesh can be found in [2], and an access control implementation in that platform is described extensively in [3].\n\n- Measure the integrity and security posture of all resources by establishing a continuous diagnostics and mitigation (CDM) or similar system to monitor the state of devices and applications and apply patches or fixes as needed.\n- An enterprise should collect data about the resource security posture, network traffic, and access requests; process that data; and use any insight gained to improve policy creation and enforcement. This data can also be used to provide context for access requests from subjects."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does IoT Non-Technical Supporting Capability Core Baseline support CMMC certification?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n## NISTIR 8259B\n\n## IoT Non-Technical Supporting Capability Core Baseline\n\nMichael Fagan Jeffrey Marron Kevin G. Brady, Jr. Barbara B. Cuthill Katerina N. Megas Rebecca Herold\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8259B\n\n\n\n## NISTIR 8259B\n\n## Internet of Things Non-Technical Supporting Capability Core Baseline\n\nMichael Fagan Jeffrey Marron Kevin G. Brady, Jr. Barbara B. Cuthill Katerina N. Megas\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nRebecca Herold\n\nThe Privacy Professor\n\nDes Moines, IA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259B\n\nAugust 2021\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259B 21 pages (August 2021)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259B\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 4)"}, {"role": "assistant", "content": "ations when implementing role-based training activities. This paper reports the results of the study and suggests actions that organizations can take to improve federal role-based training activities.\nKeywords:GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> cybersecurity,GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> role-basedGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> trainingGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium>\n\n## TABLEGLYPH<c=2,font=/EAAAAA+HKGrotesk-Bold> OFGLYPH<c=2,font=/EAAAAA+HKGrotesk-Bold> CONTENTSGLYPH<c=2,font=/EAAAAA+HKGrotesk-Bold>\n\n| NIST Usable Cybersecurity | 1 |\n|--------------------------------------------|-----|\n| Executive Summary | 2 |\n| Study Background and Purpose | 4 |\n| Methodology | 6 |\n| Results | 7 |\n| Training Assignment | 8 |\n| Role-Based Training Content and Approaches | 10 |\n| Training Compliance | 15 |\n| Support for Role-Based Training | 18 |\n| Determining Training Effectiveness | 21 |\n| Limitations | 23 |\n| Discussion | 24 |\n| Technical Appendix | 29 |\n| Detailed Study Methodology | 30 |\n| Survey Participant Demographics | 35 |\n| Survey Organizations | 38 |\n| - Role Based Training Programs | 39 |\n| References | 40 |\n| Study Instruments | 41 |\n\n## NIST USABLE CYBERSECURITY\n\nWe are the Usable Cybersecurity team within the National Institute of Standards and Technology (NIST) Visualization and Usability Group."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nstomize assessments based on organizational policies and requirements, known threat and vulnerability information, system and platform dependencies, operational considerations, and tolerance for risk.\n1\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST 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.\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| | Introduction ....................................................................................................1 | | |-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | 1.1 | | Purpose.......................................................................................................................1 | | | 1.2 | | Scope..........................................................................................................................2 | | | 1.3 | | Audience.....................................................................................................................3 | | | 1.4 | Document | Structure....................................................................................................4 | | | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 8)"}, {"role": "assistant", "content": "ms, analyses, and public comments; performed testing; provided technical and administrative support; and participated in numerous meetings to discuss the selection of the candidate to be standardized.\nThey are Zuzana Bajcsy, Lily Chen, Morris Dworkin, Sara Kerman, and Andrew Regenscheid. ## 1. Introduction\n\nThe National Institute of Standards and Technology (NIST) initiated the Post-Quantum Cryptography (PQC) Standardization Process in December 2016 to select quantum-resistant public-key cryptographic algorithms for standardization in response to the substantial development and advancement of quantum computing. After three rounds of evaluation and analysis, NIST announced the selection of the first algorithms to be standardized [2]. The key encapsulation mechanism (KEM) selected for standardization was CRYSTALS-Kyber (ML-KEM [3]). The digital signatures selected were CRYSTALS-Dilithium (ML-DSA [4]), Falcon (FN-DSA), and SPHINCS + (SLH-DSA [5]). For a detailed explanation of NIST's choices, as well as a summary of the third round, see NIST IR 8413 [2]. In addition to those initial selections, NIST advanced four KEM candidates to the fourth round for continued evaluation: BIKE [6], Classic McEliece [7], HQC [8], and SIKE [9]. These algorithms were all based on different security assumptions than ML-KEM. NIST indicated that it would select one or two of the algorithms for standardization at the conclusion of the fourth round. The fourth round began in July 2022 and involved a thorough analysis of the theoretical and empirical evidence used to justify the security of the candidates. During this time, the submitters of SIKE acknowledged its insecurity and recommended against its further use. The submission teams of the unbroken fourth-round candidates were invited to present updates for their candidate algorithms at the Fifth NIST PQC Standardization Conference in Rockville, Maryland, on April 10-12, 2024."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 10)"}, {"role": "assistant", "content": "| Malware Incident Prevention........................................................................................... | Malware Incident Prevention..........................................................................................."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Risk Assessment?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nfull, in part, or not at all. It is left to the implementing organization to understand the unique risk context in which it operates and what is appropriate for its given circumstance. For more information on how to conduct a risk assessment, see NIST Special Publication 800-30, Guide for Conducting Risk Assessments [3]."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to\nrespond to ITL calls for patents and ITL has not undertaken a patent search in order to identify\nwhich, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose\nuse may be required for compliance with the guidance or requirements of this publication, no\nsuch patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent\ninfringement in the use of this publication. v\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nNIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nDEVELOPING COMMON INFORMATION SECURITY AND PRIVACY FOUNDATIONS\nCOLLABORATION AMONG PUBLIC AND PRIVATE SECTOR ENTITIES\n\nIn developing standards and guidelines required by [FISMA], NIST consults with other federal agencies and\noffices as well as private sector entities to improve information security, avoid unnecessary and costly\nduplication of effort, and ensure that NIST publications complement the standards and guidelines\nemployed for the protection of national security systems. In addition to its comprehensive public review\nand vetting process, NIST collaborates with the Office of the Director of National Intelligence (ODNI), the\nDepartment of Defense (DoD), and the Committee on National Security Systems (CNSS) to establish and\nmaintain a unified framework and common foundation for information security across the Federal\nGovernment."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/218/a/final, including related content, potential updates, and document history."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 5)"}, {"role": "assistant", "content": "gement, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\nThe Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1. Introduction...................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. HPC System Reference Architecture and Main Components ............................................................2 |\n| 2.1.1. Components of the High-Performance Computing Zone.............................................................3 |\n| 2.1.2."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 9)"}, {"role": "assistant", "content": "xploitation data is unavailable but necessary to thoroughly test the performance of the LEV metric. The EPSS performance results are not of a form that enables a direct calculation of LEV performance.\nThus, while LEV performance is presumed to be high given the quality of its foundational EPSS data, performance results for the LEV probabilities themselves are not currently available. The National Institute of Standards and Technology (NIST) is seeking industry partners with relevant datasets to empirically measure the performance of LEV probabilities. The rest of this work is organized as follows. Section 2 provides background on vulnerability enumerations, EPSS, and KEV lists. Section 3 discusses LEV probability use cases. Section 4 presents the LEV equations. Section 5 derives the equations. Section 6 provides example LEV output. Section 7 presents empirical results. Section 8 discusses KEV list comprehensiveness measurements and possible sources of error. Section 9 covers performance. Section 10 discusses the LEV implementation and Section 11 concludes. Appendix A contain excerpts from the EPSS documentation. Appendix B is a list of abbreviations and acronyms. ## 2. Background\n\nThis section contains background necessary to understand the LEV equations and approach. It introduces vulnerability enumeration lists, EPSS scoring, and discusses KEV lists. ## 2.1. Common Vulnerabilities and Exposures\n\nThe Common Vulnerabilities and Exposures (CVE) is an enumeration of known vulnerabilities in information technology products, primarily software but also hardware [7]. It is widely accepted as the most comprehensive list available and is used extensively within the information technology security community. The United States National Vulnerability Database (NVD) provides information and references for all CVEs [8]. ## 2.2. Exploit Prediction Scoring System\n\nEPSS provides a daily updated score for each CVE."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nconsistency, and it also maintains the integrity of the source content. Because the YAML content is all command-driven, it is converted to Tenable's CMD\\_EXEC check type for use with the Unix plugin.\nThe YAML rules have a 'tags' section that was used to create unique audit profiles related to common frameworks. An example of these profiles can be seen in the audit file naming convention:"}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 9)"}, {"role": "assistant", "content": "elopment. These additions are documented in the form of an SSDF Community Profile ('Profile'), which is a baseline of SSDF practices and tasks that have been enhanced to address a particular use case.\nAn example of an addition is, 'Secure code storage should include AI models, model weights, pipelines, reward models, and any other AI model elements that need their confidentiality, integrity, and/or availability protected.'\n\nThis Profile supplements what SSDF version 1.1 already includes. The Profile is intended to be used in conjunction with NIST Special Publication (SP) 800-218, Secure Software Development Framework (SSDF) Version 1.1: Recommendations for Mitigating the Risk of Software Vulnerabilities [6] and should not be used without SP 800-218 . Readers should also utilize the implementation examples and informative references defined in SP 800-218 for additional information on how to perform each SSDF practice and task for all types of software development, as they are also generally applicable to AI model and AI system development. ## Scope\n\nThis Profile's scope is AI model development , which includes data sourcing for, designing, training, fine-tuning, and evaluating AI models, as well as incorporating and integrating AI models into other software. Consistent with SSDF version 1.1 and EO 14110, practices for the deployment and operation of AI systems with AI models are out of scope . Similarly, while cybersecurity practices for training data and other forms of data being used for AI model development are in scope, the rest of the data governance and management life cycle is out of scope. Practices and tasks in this Profile do not distinguish between human-written and AI-generated source code, because it is assumed that all source code should be evaluated for vulnerabilities and other issues before use."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.3.2 | Workshop Points of Agreement | Workshop Points of Agreement | 49 |\n| 3. 3.3.2 Review Initiation Phase Plans | 4. 3.3.2 Review Initiation Phase Plans | 81 |\n| | | Information on the Initiation | |\n| | 4."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide?"}, {"role": "assistant", "content": "## NISTIR 8420A\n\n## Approaches and Challenges of Federal Cybersecurity Awareness Programs\n\nJulie Haney Jody Jacobs Susanne Furman Fernando Barrientos\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8420A\n\n\n\n## NISTIR 8420A\n\n## Approaches and Challenges of Federal Cybersecurity Awareness Programs\n\nJulie Haney Jody Jacobs Susanne Furman Fernando Barrientos Information Access Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8420A\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8420A 73 pages (March 2022)\n\n## This publication is available free of charge from:\n\n## https://doi.org/10.6028/NIST.IR.8420A\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 6)"}, {"role": "assistant", "content": "Cybersecurity role-based training (RBT) includes specialized training on policies, procedures, and tools for individuals who are assigned roles having security and privacy responsibilities [SP800-53].\nMost United States (U.S.) Federal Government organizations are required to conduct RBT for applicable federal government personnel and supporting contractors [CISA2022]. Despite the training mandate, there has been little prior effort to look broadly across federal organizations to see how they are implementing RBT activities and what issues they are experiencing. This lack of understanding may be hindering the development of improvements and resources for federal RBT activities. To address this gap, we - the Usable Cybersecurity team at the National Institute of Standards and Technology (NIST) conducted a research study to gain insights into the approaches of and challenges faced by organizations when implementing RBT activities. Our research initially focused on cybersecurity awareness programs targeted at organizations' general workforce. However, during focus groups of 29 federal employees with cybersecurity awareness duties, many participants discussed role-based training as being an especially challenging and related aspect of their jobs. Spurred by these discoveries, we conducted a follow-up online survey solely focused on role-based training that was completed by 82 federal employees. ## We found:\n\n- RBT assignment: There is no standard way that organizations determine which employees should be assigned RBT. Some use the National Initiative for Cybersecurity Education (NICE) Workforce Framework for Cybersecurity (NICE Framework) as a guide, but others leave decisions up to the office of the Chief Information Officer (CIO) or even individual supervisors. - RBT content: About two-thirds of surveyed participants said that their organizations create at least some RBT content on their own, which could be resource-intensive."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| 1 | Summary.............................................................................................1 | Summary.............................................................................................1 | Summary.............................................................................................1 | |-----|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | | 1.2 | Solution..........................................................................................................................3 | | | | 1.3 | Benefits..........................................................................................................................4 | | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | | 2.1 | Typographic Conventions..............................................................................................5 | | | 3 | Approach.............................................................................................6 | Approach.............................................................................................6 | | | | 3.1 | Audience........................................................................................................................6 | | | | 3.2 | Scope .............................................................................................................................6 | | | | | 3.2.1 Scenario 1: Creation of Verifiable Platform | Artifacts ..................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Blockchain for Access Control Systems provide? (Part 9)"}, {"role": "assistant", "content": "The objectives of an AC system are often described in terms of protecting system resources against inappropriate or undesired user access. From a business perspective, this objective could just as well be described in terms of the optimal sharing of information [IR7316]. As current information systems and network architectures evolve to be more lightweight, pervasive, and interactive - such as the cloud and Internet of Things (IoT) - there is need for an AC mechanism to support the requirements of decentralization, scalability, and trust for accessing objects, all of which are challenging for traditional mechanisms. Blockchains are tamper-evident and tamper-resistant cryptographically linked blocks of data (which create digital ledgers) implemented in a distributed fashion (i.e., without a central repository) and usually without a central authority (i.e., a bank, company, or government). It uses replicated, shared, and synchronized digital blocks between the users of a private or public distributed computer network located in different sites or organizations. A block links to previous blocks by containing a cryptographic hash summary of the previous block's contents, thus making the blockchain tamper-resistant and tamper-evident (because to change a block, one must then change all subsequent blocks that follow it). A linked list of blocks (i.e., a blockchain) typically has no central control authority and utilizes a decentralized consensus mechanism for reliable data transactions. A smart contract is a transaction protocol that executes the terms of a contract (such as payment term, lien, confidentiality, and even enforcement) on a blockchain via code that is deployed to and executed by blockchain nodes. The main purpose of smart contracts is to satisfy common contractual conditions, as well as minimize exceptions (both malicious and accidental) and the need for trusted intermediaries [IR8202]."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nDEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..................................................................................\n7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................"}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 5)"}, {"role": "assistant", "content": "quirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.\n## Keywords\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors also wish to recognize the scientists, engineers, and research staff from the NIST Computer Security and the Applied Cybersecurity Divisions for their exceptional contributions in helping to improve the content of the publication. A special note of thanks to Pat O'Reilly, Jim Foti, Jeff Brewer, Chris Enloe, Ned Goren, and the entire NIST web team for their outstanding administrative support. Finally, the authors also gratefully acknowledge the contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 5)"}, {"role": "assistant", "content": "ibility matrixes (e.g., RACI charts) to document who will be responsible, accountable, consulted, and informed for C-SCRM activities and how those teams and individuals will be consulted and informed.\n☐ Include C-SCRM responsibilities and performance requirements in personnel descriptions to ensure clarity and improve accountability. ☐ Document performance goals for personnel with C-SCRM responsibilities, and periodically measure them to demonstrate and improve performance. ☐ Develop roles and responsibilities for suppliers, customers, and business partners to address shared responsibilities for applicable cybersecurity risks and integrate them into organizational policies and applicable third-party agreements. ☐ Internally communicate C-SCRM roles and responsibilities for suppliers. ☐ Establish rules and protocols for information sharing and reporting processes between the organization and its suppliers. ## C-SCRM requirements:\n\n- ☐ Establish security requirements for suppliers, products, and services commensurate with their criticality and potential impact if compromised. - ☐ Include all cybersecurity and supply chain requirements that suppliers must follow and how compliance with the requirements may be verified in default contractual language. - ☐ Define the rules and protocols for information sharing between the organization and its suppliers and sub-tier suppliers in contracts. ☐ Include security requirements in contracts based on their criticality and potential impact if compromised. - ☐ Define security requirements in service level agreements (SLAs) for monitoring suppliers for acceptable security performance throughout the supplier relationship lifecycle. - ☐ Specify in contracts the rights and responsibilities of the organization, its suppliers, and their supply chains with respect to potential cybersecurity risks."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 6)"}, {"role": "assistant", "content": "ns such as the Institute of Internal\nAuditors, the American Institute of Certified Public Accountants, and\nthe EDP Auditors Associtation. The National Bureau of Standards, with the support of the U.S.\nGen-\n\neral Accounting Office, sponsored an invitational workshop in March of\n1977 to explore the subject of \"Audit and Evaluation of Computer Securi-\nty.\" Leading experts in the audit and computer communities were invited\nto share their thoughts and develop a consensus view on ten aspects of\nthe subject. These Proceedings are the results of that meeting. To all those concerned with the audit and evaluation of computer\n\nsecurity today, we at the National Bureau of Standards offer this series\nThe views expressed do not\nof consensus reports for your consideration. necessarily reflect those of the National Bureau of Standards, the U. S. General Accounting Office, or any of the organizations that sponsored an\nindividual at the workshop. However, these reports do reflect the compo-\nsite thoughts of a group that deserves your serious attention. M. Zane Thornton\nActing Director\nInstitute for Computer\nSciences and Technology\n\niil\n\n\f. PREFACE\n\nThe National Bureau of Standards (NBS) initiated a Task Group\n\nwithin the Federal Information Processing Standards (FIPS) program in\n1973 to develop standards in Computer Systems Security. (TG-15) was composed of representatives from private industry as well as\nFederal, State and local governments. The NBS Invitational Workshop on\nAudit and Evaluation of Computer Security was organized as one phase of\na two-phase project defined by the Task Group in this important area of\ncomputer security. The\nsecond phase will be to adapt this information to the needs of Federal\nagencies in the form of Federal Information Processing Guidelines. latter effort will be carried out by a working group convened for this\npurpose and will result in a FIPS publication by NBS. These Proceedings are the result of phase one."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n..................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5.\nTraceability of CE Operations.....................................................................................................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1. Information Decisions in the System Life Cycle..........................................................................20 |\n| 4.3.2. Determination of Security Categorization..................................................................................21 |\n| 4.3.3. Reuse of Media...........................................................................................................................22 |\n| 4.3.4. Control of Media ........................................................................................................................22 |\n| 4.3.5. Data Protection Level .................................................................................................................23 |\n| 4.3.6. Sanitization and Disposal Decision.............................................................................................23 |"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\ncurity officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control.\nAs we push computers to 'the edge,' building a complex world of interconnected information systems and devices, security and privacy risks (including supply chain risks) continue to be a large part of the national conversation and topics of great importance. The significant increase in the complexity of the hardware, software, firmware, and systems within the public and private sectors (including the U.S. critical infrastructure) represents a significant increase in attack surface that can be exploited by adversaries. Moreover, adversaries are using the supply chain as an attack vector and effective means of penetrating our systems, compromising the integrity of system elements, and gaining access to critical assets."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 7)"}, {"role": "assistant", "content": "| 3. Definitions, Symbols and Abbreviations...............................................................................\n2 |\n| 3.1 Definitions........................................................................................................................... 2 | 3.1 Definitions........................................................................................................................... 2 | 3.1 Definitions........................................................................................................................... 2 |\n| 3.2 Symbols and Abbreviations................................................................................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nMany 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. The Community Profile is intended for use by most organizations, regardless of sector, size, or other factors. Additional versions of this Community Profile could be developed for narrower audiences, such as federal agencies, small businesses, or educational institutions. For more information on CSF 2.0 Community Profiles, see the Framework Resource Center."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.5.1. 3.5.1. 3.5.1."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nParticipants indicated topics that their security awareness programs addressed via training courses, events, or other communications in the past 1 - 2 years. Figure 9 shows the security awareness topics and percentages of programs addressing those topics. All participants' programs covered the topic of social engineering, and over 90% addressed passwords and authentication, malware, and privacy topics. Security considerations when installing or updating software was the least covered topic but still addressed by 64% of programs. Participants were asked what other teams/groups within their organization they collaborate with or consult in their security awareness mission (Figure 18). Over 70% collaborated with the incident response team (77%), the privacy team (73%), and the IT team (71%). Much fewer work with the General Counsel (39%) and Human Resources (HR) (38%). - 'I do consult with members of the SOC [Security Operations Center] to see if there's anything glaring that I need to include in my training each year.' (N09)\n- 'Also working with the help desk, just what type of problems our users encounter that are related to security issues.' (S05)\n- 'Being tied directly to the cybersecurity policy team has made it easier because the awareness team always has whatever the latest guidance is and can push that out very quickly.' (D03)\n- 'We've worked closely with the information security officials' (N08)\n- 'I'm located in the chief information security office, and there are…divisions in that office that provide a wide range of cybersecurity services to the Department. And those managers have responsibilities for things such as identity management, internet response, data loss prevention. So, within any year, I reach out to those stakeholders to ask, 'What's important for the user to understand about cybersecurity awareness? What do you want to talk to the customer about?"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nThe SSDF provides a common language for describing secure software development practices throughout the software development life cycle. This document augments the practices and tasks defined in SSDF version 1.1 by adding recommendations, considerations, notes, and informative references that are specific to generative AI and dual-use foundation model development. These additions are documented in the form of an SSDF Community Profile ('Profile'), which is a baseline of SSDF practices and tasks that have been enhanced to address a particular use case. An example of an addition is, 'Secure code storage should include AI models, model weights, pipelines, reward models, and any other AI model elements that need their confidentiality, integrity, and/or availability protected.'\n\nAll practices and tasks are unchanged from SSDF version 1.1 unless they are explicitly tagged as 'Modified from SSDF 1.1' or 'Not part of SSDF 1.1.' An example is the PW.3 practice, ' Confirm the Integrity of Training, Testing, Fine-Tuning, and Aligning Data Before Use' and all of its tasks."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 8)"}, {"role": "assistant", "content": "..............................................27 | |\n| 4.7.7.\nProperty Management Officer ...................................................................................................28 | |\n| 4.7.8. Records Management Officer ....................................................................................................28 | |\n| 4.7.9. Privacy Officer ............................................................................................................................28 | |\n| 4.7.10. Users.........................................................................................................................................28 | |\n| References.......................................................................................................................................29 | |\n| Appendix A. Glossary | .......................................................................................................................32 |\n| Appendix B."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n| F.1 | Traffic Visibility to Support Troubleshooting ............................................................. | Traffic Visibility to Support Troubleshooting ............................................................. | 51 |\n|------------|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|\n| F.2 | Traffic Visibility to Support Performance Monitoring ................................................ | Traffic Visibility to Support Performance Monitoring ................................................ | 51 |\n| F.3 | Traffic Visibility to Support Cybersecurity Threat Triage and Forensics ..................... | Traffic Visibility to Support Cybersecurity Threat Triage and Forensics ..................... | 51 |\n| F.4 | Traffic Visibility to Support Monitoring for Compliance and Hygiene ........................ | Traffic Visibility to Support Monitoring for Compliance and Hygiene ........................ | 51 |\n| F.5 | Functional Demonstration Scripts and Results .......................................................... | Functional Demonstration Scripts and Results .......................................................... | 51 |\n| | F.5.1 | Scenario 1.1 - Identify Failed Network Traffic Due to Expired TLS PKI Certificates (Layer 4) ......................................................................................................................"}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 3-8 |\n| Fig. | 1 | Responsibilities and Duties to Provide Security for Data Processing System ..\n| 3-5 |\n| PART | | SESSION 2 ~ MANAGERIAL AND ORGANIZATIONAL VULNERABILITIES AND CONTROLS ~ LINE LEVEL - DATA PROCESSING | |\n| | IV: | | 4-1 |\n| | | | 4-2 |\n| 1. | EDITOR'S | NOTE INTRODUCTION 4-3 | 4-3 4-3 |\n| | 1.1 1.2 1.3 | The Charge Intent of Paper | 4-3 4-3 |\n| 2. | 1.4 | Elements of Discussion Comments | 4-4 |\n| | DATA | PROCESSING \"."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nne or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control.\n- Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 3)"}, {"role": "assistant", "content": "ores disponibles para el propósito. En esta publicación puede haber referencias a otras que actualmente están siendo desarrolladas por NIST de acuerdo con sus responsabilidades estatutarias asignadas.\nLa información contenida en esta publicación, incluidos conceptos y metodologías, puede ser utilizada por los organismos federales incluso antes de la finalización de dichas publicaciones complementarias. Por lo tanto, hasta que se finalice cada publicación, los requisitos, directrices y procedimientos actuales, cuando existan, seguirán siendo operativos. A efectos de planificación y transición, los organismos federales pueden seguir de cerca el desarrollo de estas nuevas publicaciones del NIST. Se anima a las organizaciones a revisar todos los borradores de publicaciones durante los periodos de comentarios públicos y proporcionar retroalimentación al NIST. Muchas publicaciones sobre ciberseguridad del NIST, aparte de las mencionadas anteriormente, están disponibles en https://csrc.nist.gov/publications. ## Los comentarios sobre esta publicación pueden enviarse a\n\nInstituto Nacional de Estándares y Tecnología A la atención de: Advanced Network Technologies Division, Information Technology Laboratory\n\n100 Bureau Drive (Mail Stop 8920) Gaithersburg, MD 20899-8920\n\nCorreo electrónico: zerotrust-arch@nist.gov\n\nTodos los comentarios están sujetos a la Ley de Libertad de Información (FOIA). ## Informes sobre tecnología de sistemas informáticos\n\nEl Laboratorio de Tecnología de la Información (ITL, por su nombre en inglés, Information Technology Laboratory) del Instituto Nacional de Estándares y Tecnología (NIST) promueve la economía y el bienestar público de Estados Unidos a través de su liderazgo técnico en la infraestructura de medición y normalización del país."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n|\n| Federal Vulnerability Disclosure Coordination Body ....................................................\n| 6 | |\n| Preparation................................................................................................................. | 7 | |\n| 2.1.1. Create Source Vulnerability | Report Receipt Capability............................................. 7 | |\n| 2.1.2. Determine Scope and Obtain Contacts .................................................................... | 8 | |\n| 2.1.3. Develop Technical Analysis Capability ....................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\n## Access Control on NoSQL Databases\n\n## Access Control on NoSQL Databases\n\nHu VC (2024) Access Control on NoSQL Databases. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8504. https://doi.org/10.6028/NIST.IR.8504"}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 2)"}, {"role": "assistant", "content": "cies; conducts physical and chemical research; develops, produces, and distributes Standard Reference Materials; provides calibration services; and manages the National Standard Reference Data System.\nThe Laboratory consists of the following centers:\n\n## The National Engineering Laboratory\n\nProvides technology and technical services to the public and private sectors to address national needs and to solve national problems; conducts research in engineering and applied science in support of these efforts; builds and maintains competence in the necessary disciplines required to carry out this research and technical service; develops engineering data and measurement capabilities; provides engineering measurement traceability services; develops test methods and proposes engineering standards and code changes; develops and proposes new engineering practices; and develops and improves mechanisms to transfer results of its research to the ultimate user. The Laboratory consists of the following centers:\n\n## The Institute for Computer Sciences and Technology\n\nConducts research and provides scientific and technical services to aid Federal agencies in the selection, acquisition, application, and use of computer technology to improve effectiveness and economy in Government operations in accordance with Public Law 89-306 (40 U.S.C. 759), relevant Executive Orders, and other directives; carries out this mission by managing the Federal Information Processing Standards Program, developing Federal ADP standards guidelines, cind managing Federal participation in ADP voluntary standardization activities; provides scientific and technological advisory services and assistance to Federal agencies; and provides the technical foundation for computer-related policies of the Federal Government."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines provide? (Part 6)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . . . . . 2. Digital Identity Model\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n. . . . . . 2.2. Identity Proofing and Enrollment\n\n. . . . . . . . . . . . . . . . . . . . . 2.2.1. Subscriber Accounts . . . . . . . . . . . . . . . . . . . . . . . . 2.3. Authentication and Authenticator Management\n\n. . . . . . . . . . . . . 2.3.1. Authenticators . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.2. Authentication Process\n\n. . . . . . . . . . . . . . . . . . . . . . 2.4. 2.5. Federation and Assertions . . . . . . . . . . . . . . . . . . . . . . . . . Examples of Digital Identity Models . . . . . . . . . . . . . . . . . . . . 2.5.1. Non-Federated Digital Identity Model . . . . . . . . . . . . . . . 2.5.2. Federated Digital Identity Model With General-Purpose IdP . . . 1\n\n2\n\n3\n\n4\n\n4\n\n5\n\n6\n\n8\n\n8\n\n9\n\n9\n\n10\n\n10\n\n10\n\n11\n\n12\n\n13\n\n15\n\n15\n\n17\n\n2.5.3. Federated Digital Identity Model with Subscriber-Controlled Wallet 18\n\n3. Digital Identity Risk Management\n\n. . . . . . . . . . . . . . . . . . . . . . . . 3.1. Define the Online Service . . . . . . . . . . . . . . . . . . . . . . . . . 3.2. Conduct Initial Impact Assessment\n\n. . . . . . . . . . . . . . . . . . . . 3.2.1. Identify Impact Categories and Potential Harms\n\n. . . . . . . . . 3.2.2. Identify Potential Impact Levels . . . . . . . . . . . . . . . . . . 3.2.3. Impact Analysis\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.4. Determine the Combined Impact Level for Each User Group . . . 3.3. Select Initial Assurance Levels and Baseline Controls . . . . . . . . . . . 21\n\n24\n\n27\n\n27\n\n29\n\n31\n\n32\n\n33\n\niii\n\n\fNIST SP 800-63-4\nJuly 2025\n\nDigital Identity Guidelines\n\n3.3.1. Assurance Levels . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2. Assurance Level Descriptions\n\n. . . . . . . . . . . . . . . . . . . 3.3.3. Initial Assurance Level Selection . . . . . . . . . . . . . . . . . . 3.3.4."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 8)"}, {"role": "assistant", "content": "I and for dual-use foundation models.' This document is that companion resource. The software development and use of AI models and AI systems inherit much of the same risk as any other digital system.\nA unique challenge for this community is the blurring of traditional boundaries between system code and system data, as well as the use of plain human language as the means of interaction with the systems. AI models and systems, their configuration parameters (e.g., model weights), and the data they interact with (e.g., training data, user queries, etc.) can form closed loops that can be manipulated for unintended functionality. AI model and system development is still much more of an art than an exact science, requiring developers to interact with model code, training data, and other parameters over multiple iterations. Training datasets may be acquired from unknown, untrusted sources. Model weights and other training parameters can be susceptible to malicious tampering. Some models may be complex to the point that they cannot easily be thoroughly inspected, potentially allowing for undetectable execution of arbitrary code. User queries can be crafted to produce undesirable or objectionable output and - if not sanitized properly - can be leveraged for injection-style attacks. The goal of this document is to identify the practices and tasks needed to address these novel risks. ## Purpose\n\nThe SSDF provides a common language for describing secure software development practices throughout the software development life cycle. This document augments the practices and tasks defined in SSDF version 1.1 by adding recommendations, considerations, notes, and informative references that are specific to generative AI and dual-use foundation model development. These additions are documented in the form of an SSDF Community Profile ('Profile'), which is a baseline of SSDF practices and tasks that have been enhanced to address a particular use case."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 7)"}, {"role": "assistant", "content": "ation's role, this baseline is intended to give all organizations a starting point for IoT device cybersecurity risk management, but the implementation of all capabilities is not considered mandatory.\nThe individual capabilities in the baseline may be implemented in\n\n1 The usage of the term 'baseline' in this publication should not be confused with the low-, moderate-, and high-impact system control baselines set forth in NIST Special Publication (SP) 800-53 [1] to help federal agencies meet their obligations under the Federal Information Security Modernization Act (FISMA) and other federal policies. In that context, the low-, moderate-, and high-impact control baselines apply to an information system, which may include multiple components, including devices. In this publication, 'baseline' is used in the generic sense to refer to a set of foundational requirements or recommendations, and the core baseline described is meant to apply to individual IoT devices. full, in part, or not at all. It is left to the implementing organization to understand the unique risk context in which it operates and what is appropriate for its given circumstance. For more information on how to conduct a risk assessment, see NIST Special Publication 800-30, Guide for Conducting Risk Assessments [3]. Furthermore, this baseline is not the only set of capabilities that exist. This baseline represents a coordinated effort to produce a definition of common capabilities, not an exhaustive list. Therefore, an implementing organization may define capabilities that better suit their organization. Using these additional capabilities to support IoT device cybersecurity risk management is encouraged. For more information on IoT device security and privacy considerations, see NISTIR 8228, Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks [4]."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 9)"}, {"role": "assistant", "content": "ve significant differences. An HPC system is designed to maximize performance, so its architecture, hardware components, software stacks, and working environment are very different from enterprise IT.\nAdditionally, most HPC systems serve multiple projects and user communities, leading to more complex security concerns than those encountered in enterprise systems. As such, security solutions must be tailored to the HPC system's requirements. Furthermore, HPC systems are often different from one another due to the evolution of their system designs, the applications they run, and the missions they support. An HPC system frequently has its own unique method of applying security requirements and may follow different security guidance, which can impede the sharing of security solutions and knowledge. This NIST Special Publication aims to standardize and facilitate the sharing of HPC security information and knowledge through the development of an HPC system reference architecture and key components, which are introduced as the basics of the HPC system lexicon. The reference architecture divides an HPC system into four function zones. A zone-based HPC reference architecture captures the most common features across the majority of HPC systems and segues into HPC system threat analysis. Key HPC security characteristics and use requirements are laid out alongside the major threats faced by the system and individual function zones. HPC security postures, challenges, recommendations, and some currently recognized variants are also included. This publication is intended to be a conceptual guide, not a checklist of requirements. Finally, emerging technologies - such as novel networking technology, data storage solutions, hardware acceleration technology, and others - have the potential to influence the HPC reference architecture and security posture. Consequently, this document will be updated as needed. ## 2."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n## Guidelines on Mobile Device Forensics\n\n## Guidelines on Mobile Device Forensics\n\nMobile device forensics is the science of recovering digital evidence from a mobile device under forensically sound conditions using accepted methods. Mobile device forensics is an evolving specialty in the field of digital forensics. This guide attempts to bridge the gap by providing an indepth look into mobile devices and explaining technologies involved and their relationship to forensic procedures. This document covers mobile devices with features beyond simple voice communication and text messaging capabilities. This guide also discusses procedures for the validation, preservation, acquisition, examination, analysis, and reporting of digital information."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nIntroduction\nSetting PA Objectives .\nGathering Information\nPerforming PA Analyses and Evaluations\nDesigning and Performing PA Test Procedures „\n3.5.1\n3.5o2\n\n3.5.3\n3.5.4\n\nguarantee that only authorized recipients may be\nsent personal information via automated installa-\ntions (authentication)"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.1.1. 3.1.1. 3.1.1)\n- Agencies will benefit if their MFA solutions support multiple authenticator types and methods."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\ntion's IT hosts and information. Accordingly, awareness programs should include guidance to users on malware incident prevention, which can help reduce the frequency and severity of malware incidents.\nAll users should be made aware of the ways in which malware enters and infects hosts; the risks that malware poses; the inability of technical controls to prevent all incidents; and the importance of users in preventing incidents, with an emphasis on avoiding social engineering attacks (as discussed below). In addition, the organization's awareness program should cover the malware incident prevention considerations in the organization's policies and procedures, as described in Section 3.1, as well as generally recommended practices for avoiding malware incidents. Examples of such practices are as follows:"}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n1 - Identify Failed Network Traffic Due to Expired TLS PKI Certificates (Layer 4) ......................................................................................................................\n| 51 |\n| | F.5.2 | Scenario 1.2 - Identify and Log Protocol- Specific Distinct Characteristics of Layer 5, and 7-type Service Utilization and Consumption Information ................................... | 6, 51 |\n| | F.5.3 | Scenario 1.3 - Identify, Collect, and Report on Protocol -Specific Error Status Codes for Services (Layer 5, 6, and 7 -type status codes) ...................................................... | 51 |\n| | F.5.4 | Scenario 2.1 - Identify, Collect, and Report on Protocol -Specific Error Status Codes for Services.................................................................................................................. | 52 |\n| | F.5.5 | Scenario 2.2 - Identify the Propagation of Performance Issues Throughout a System by Correlating Error Status Codes Across Component Services ................................. | 52 |\n| | F.5.6 | Scenario 2.3 - Develop Baselines for Traffic Performance Characteristics for Each Server .........................................................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\naft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nMalware, also known as malicious code, refers to a program that is covertly inserted into another program with the intent to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Malware is the most common external threat to most hosts, causing widespread damage and disruption and necessitating extensive recovery efforts within most organizations. This publication provides recommendations for improving an organization's malware incident prevention measures. It also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. Prior industry surveys and research studies have revealed that organizational cybersecurity awareness (hereafter shortened to 'security awareness') programs may face a number of challenges, including lack of: leadership support; resources; and staff with sufficient background and skills to implement an effective and engaging program. However, no prior research has explored security awareness programs specifically in the United States (U.S.) government (federal) sector."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nhey can be remediated more quickly in accordance with risk, reducing the window of opportunity for attackers. | and third-party components that the software uses, and investigate all credible reports.\n| | R2: Make the users of AI models aware of mechanisms for reporting potential security and performance issues. N1: In this context, 'users' refers to AI system producers and acquirers who are using an AI model. R3: Monitor vulnerability and incident databases for information on AI-related concerns, including the machine learning frameworks and libraries used to build AI models. | Measure 1.2, 2.4, 2.5, 2.7, 3.1, 3.2, 3.3; Manage 4.1 OWASP: LLM03-7a, LLM09, LLM10 |\n| that they can be remediated more quickly in accordance with risk, reducing the window of opportunity for attackers. | RV.1.2: Review, analyze, and/or test the software's code to identify or confirm the presence of previously undetected vulnerabilities. | Medium | R1: Scan and test AI models frequently to identify previously undetected vulnerabilities. R2: Rely mainly on automation for ongoing scanning and testing, and involve a human-in- the-loop as needed. R3: Conduct periodic audits of AI models. | AI RMF: Govern 4.3; Measure 1.3, 2.4, 2.7, 3.1; Manage 4.1 OWASP: LLM03-7b, LLM03-7d |\n| that they can be remediated more quickly in accordance with risk, reducing the window of opportunity for attackers. | RV.1.3: Have a policy that addresses vulnerability disclosure and remediation, and implement the roles, responsibilities, and processes needed to support that policy. | Medium | R1: Include AI model vulnerabilities in organization vulnerability disclosure and remediation policies. R2: Make users of AI models aware of their inherent limitations and how to report any cybersecurity problems that they encounter."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\novide required technical support. - Insider threats: Insider threats come from people within the organization who have internal information and may have the privileges needed to access the HPC system.\nInsider threats can be classified into accidental/unintentional threats and malicious/intentional threats. Unintentional threats come from the unintended side effects of normal actions and activity. In contrast, a malicious insider may intentionally upload malicious code into the HPC system."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.2.2, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 7)"}, {"role": "assistant", "content": "nd sensitive data are loaded into the manufactured IC. Standard data are generic and mostly available open source, but the sensitive data are anything whose disclosure would compromise IP or security.\nFor example, keys of crypto modules or logic locking keys are sensitive data. 7. Deployment and Use: This stage includes delivering the IC to customers and using the IC. Many hardware vulnerabilities are exploited at this stage. 8. End of Life: End-of-life for an IC is the stage where the manufacturer no longer sells or manufactures IC [8]. This is often because of technological advancements when new ICs exhibiting better performance have been launched. When a chip reaches its end-of-life, the deployed chips are gradually replaced and discarded. These discarded chips are\n\noften reused or recycled into new hardware compromising their quality and performance. ## 3. Framework for Supply Chain Threat Analysis\n\nThis work proposes a framework for analyzing different threats and how collusion among adversaries can affect the severity of threats. This analysis is divided into five distinct stages that discuss adversaries' intent, access, and resources, and how their collusion affects the severity of different threats. The framework is shown in Fig. 2. The framework incorporates threats across all stages of supply chain including insider threats. Fig. 2. Methodology for supply chain threat analysis\n\n\n\n## 3.1. Identify the Intent of the Adversary\n\nSupply chain security analysis begins with identifying the adversary's objectives. For example, an adversary may wish to disrupt a hardware's functionality or steal a designer's intellectual property (IP). This analysis describes the potential attacker, the resources that must be protected, and the semiconductor supply chain stage at which mitigation is best applied. ## 3.2. Identify Hardware Threats\n\nThe second step is identifying the threats associated with the adversary's intent."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 4)"}, {"role": "assistant", "content": "related integrators and technical support firms serving the consumer and business sectors, and testing and certification bodies interested in establishing baselines of IoT cybersecurity capabilities.\n## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nn Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562.\nhttps://doi.org/10.6028/NIST.IR.8562\n\n## Author ORCID iDs\n\nKaterina Megas: 0000-0002-2815-5448 Michael Fagan: 0000-0002-1861-2609 Barbara Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Abstract\n\nThis report summarizes the feedback received by the NIST Cybersecurity for the Internet of Things (IoT) program at the in-person and hybrid workshop on \"Updating Manufacturer Guidance for Securable Connected Product Development\" held in December 2024. The purpose of this workshop was to consider how to update Foundational Cybersecurity Activities for IoT Device Manufacturers (NIST Internal Report (IR) 8259) based on concepts in risk management, operational technology concerns, product end of life concerns and recent trends in IoT cybersecurity and privacy. Over time, the NIST volume of work has built upon the concepts introduced in NIST IR 8259,to add technical (NIST IR 8259A) and nontechnical (NIST IR 8259B) concepts to help manufacturers and customers consider the cybersecurity of IoT devices. The NIST IR 8259 series has been used to inform and develop subsequent publications that elaborate on IoT cybersecurity across sectors and use cases (e.g., federal agency uses cases reflected in NIST SP 800-213 and consumer use cases reflected in NIST IR 8425 and the U.S. Cyber Trust Mark). ## Keywords\n\ncybersecurity baseline; Internet of Things (IoT); IoT products; manufacturing; privacy; risk management; securable products; security requirements; software development; threat modelling. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.1 (NIST 3.6.1)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.6.1 Secure Host Operating System | 3. 3.6.1 Secure Host Operating System; If one wishes to implement an unprivileged data management system atop an existing secure operating system which supports general usage it is important to note that the implementation cannot provide either more nor less security than that provided by the operating system's security policy."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.6.1", "cmmc_practice_id": "IR.L2-3.6.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\n- Policy Engine (PE): The 'brain' of a ZTA implementation and the components that ultimately evaluate resource access requests. The PE relies on information from the various data sources (access logs, threat intelligence, endpoint health, and network ID authentication, etc.)\n- Policy Administrator (PA): The executor function of the PE. The PA's role is to establish, maintain and ultimately terminate sessions 1 in the data plane between the subject and the resource. The PA, PE and PEP communicate on a logically (or physically) separate set of channels called the control plane. The control plane is used to establish and configure the data plane channels used to send application traffic.\n- Policy Enforcement Point (PEP): The component that applications, endpoints, etc. will interact with to be granted access permission to a resource. The PEP is responsible for gathering information for the PE and following the instructions issued by the PA to establish and terminate communication sessions. All data plane communications between enterprise resources must be managed by a PEP.\n- Information feeds (left and right ): Sometimes called policy information points (PIPs). These are not 'core' functional ZTA components themselves but used to support the PE. These feeds include the set of codified policies, identity and endpoint attributes, environmental factors and historical data used by the PE to generate resource access decisions."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Personnel Security?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| | Documentation ( continued ) | 4."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nThe primary audience for this publication is chief information officers, chief information security officers, cybersecurity directors and managers, and others who are responsible for managing organizational risk related to the use of software. Others with an interest in the topic, including business and mission owners, security engineers and architects, system administrators, and security operations personnel, may find portions of the publication to be informative.\n\n- Security and technology management and leadership at all levels of the organization will gain a new understanding of the role of patching in enterprise risk management.\n- The security/technology and business/mission sides of the organization will be able to communicate with each other more effectively regarding patch management and reach consensus on planning.\n- Personnel from the security/technology and business/mission sides of the organization will be prepared to revamp their enterprise patching strategy throughout the entire patch management life cycle.\n\nEnterprise patch management has been a contentious issue for decades, with personnel from the security and business/mission sides of organizations often having conflicting opinions. For example, many organizations have struggled with balancing the trade-offs between earlier deployment and more testing. Deploying patches more quickly reduces the window of opportunity for attackers but increases the risk of operational disruption because of the lack of testing. Conversely, testing patches before deployment decreases the risk of operational disruption but increases the window of opportunity for attackers. Testing can also consume considerable staff resources, and it still might miss problems."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The National Institute of Standards and Technology (NIST) hosted an in-person, all-day workshop on February 27, 2024, to discuss existing and emerging cybersecurity threats and mitigation techniques for semiconductors throughout their life cycle. The workshop obtained valuable feedback from industry, academia, and government to inform NIST's development of cybersecurity and supply chain standards, guidance, and recommended practices. The discussion focused on semiconductor development and highlighted cybersecurity measurements and metrics that utilize reference data sets to facilitate the testing, attestation, certification, verification, and validation of semiconductor components. It also emphasized the use of automated cybersecurity tools and techniques to secure manufacturing environments throughout the development life cycle. This report summarizes the content that was presented and discussed at the workshop. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the US economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.4.3 Other Considerations\n\nAnother defense that can partially prevent this use case is detection of the email as spam."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n[FISMA2014] | CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes | |---------------|-----------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ID.RA-01 | Vulnerabilities in assets are identified, validated, and recorded | Medium | on cybersecurity risk assessment."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 3)"}, {"role": "assistant", "content": "cation History\n\nApproved by the NIST Editorial Review Board on 2022-11-10\n\n## How to Cite this NIST Technical Series Publication:\n\nChandramouli R (2022) Guide to a Secure Enterprise Network Landscape.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-215. https://doi.org/10.6028/NIST.SP.800-215\n\n## Author ORCID iDs\n\nRamaswamy Chandramouli: 0000-0002-7387-5858\n\n## Contact Information\n\nsp800-215-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nAccess to multiple cloud services, the geographic spread of enterprise Information Technology (IT) resources (including multiple data centers), and the emergence of microservices-based applications (as opposed to monolithic ones) have significantly altered the enterprise network landscape. This document is meant to provide guidance to this new enterprise network landscape from a secure operations perspective. Hence, it starts by examining the security limitations of current network access solutions to the enterprise network. It then considers security feature enhancements to traditional network appliances in the form of point security solutions, network configurations for various security functions (e.g., application/services security, cloud services access security, device or endpoint security), security frameworks that integrate these individual network configurations (e.g., zero trust network access [ZTNA]), and the evolving wide area network (WAN) infrastructure to provide a comprehensive set of security services for the modern enterprise network landscape (e.g., secure access service edge [SASE])."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.3.1. 3.3.1) to\nidentify the corresponding set of baseline digital identity controls from the requirements\nand guidelines in the companion volumes [SP800-63A], [SP800-63B], and [SP800-63C]. 3.3.1."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n| Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | |\n|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ...................................................................................................................... | 1. Introduction ...................................................................................................................... | 1. Introduction ......................................................................................................................"}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n.................................................................. 1\n1.1 PURPOSE AND APPLICABILITY ...................................................................................................\n2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 5)"}, {"role": "assistant", "content": "cal access control systems (PACS). Information in this document is also useful to government contractors and physical security vendors that provide HSPD-12 systems, products, and integration services.\nIt is expected that readers have a general knowledge of PIV standards, including [FIPS 201-2], [SP800-73], and [SP800-78]. ## Executive Summary\n\nHomeland Security Presidential Directive-12 [HSPD-12] sets a clear goal to improve federal facility access through the use of government-wide identity standards. These goals are reflected in the Office of Management and Budget (OMB) Circular A-130, which references SP 800-116 to ensure continued deployment and use of the identity credentials accessing Federal facilities. 1\n\nFederal Information Processing Standard 201 [FIPS201] defines characteristics of the identity credential that can be interoperable government-wide. In the context of [HSPD-12], the term interoperability means the ability to use any Personal Identity Verification (PIV) Card with any application performing one or more PIV authentication mechanisms. [FIPS201] also defines authentication mechanisms at four assurance levels (LITTLE or NO, SOME, HIGH, and VERY HIGH). These levels provide for the risk based approach as directed in HSPD-12 to ' include graduated criteria, from least secure to most secure, to ensure flexibility in selecting the appropriate level of security for each application.'\n\nThe risk-based approach for facility access is stipulated via the designation of 'Controlled, Limited, Exclusion' areas (see Section 4.3). Specifically, this document recommends PIV authentication mechanisms for 'Controlled, Limited, Exclusion' in terms of authentication factors as shown in Table ES-1. Some agencies may have different names for their security areas, however each agency should establish their criteria to implement authentication consistent with this document."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.5 (NIST 3.3.5)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.3.5\n\nRemote Computing\n\nSecurity controls in a remote computing or inter-\n\nactive environment are important because physical locks\nand keys alone may not provide for adequate accountability\nThe minimum controls to be\nor deter unauthorized access."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.3.5", "cmmc_practice_id": "AU.L2-3.3.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n- Patch management\n- Dependency management\n- Authentication and authorization\n- Malware protection\n- Secure SDLC\n- Data protection\n- Physical security\n- Audit and monitoring\n- Adherence to applicable security standards (e.g., regulatory requirements)\n\nOrganizations can implement various controls to mitigate risks to their SDLC environment, including regular patch management, robust authentication, granular authorization, malware protection, secure SDLC practices, data protection measures, physical security controls, and auditing and monitoring tools. They should regularly assess their security posture, identify potential weaknesses and vulnerabilities, and implement appropriate defensive measures to address them. Organizational network policies that account for and actively block maliciously known content-serving domains can reduce the use of software from non-curated or undesired locations. Another integral part of SSC security involves capturing the dependencies (e.g., package name, version) of the artifacts in a central repository. Organizations should also ensure that their SDLC environment remains compliant with various security and other relevant standards, such as the Open Worldwide Application Security Project (OWASP) Top Ten, SP 80053, Health Insurance Portability and Accountability Act ( HIPAA), and Payment Card Industry Data Security Standard ( PCI DSS). - The security team should establish a policy for trusted sources of OSS (e.g., allow lists) that includes reviewing minimum coding requirements, reputational standards, and distributing source code in a digitally signed package. - The security team should approve the merging of unverified sources of OSS. - Developers should download OSS as source code rather than pre-compiled libraries or binaries, when available."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 5)"}, {"role": "assistant", "content": "ion technology - Security techniques - Security requirements for cryptographic modules , and ISO/IEC 24759, Information technology - Security techniques - Test requirements for cryptographic modules .\n## Table of Contents\n\n| | Introduction ...................................................................................................................... 1 |\n|------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|\n| | Scope......................................................................................................................... 1 |\n| | Normative References................................................................................................ 1 |\n| | Document Organization................................................................................................... 2 |\n| | General......................................................................................................................."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.1.1 Security Awareness Roles and Percentage of Time... 3.1.1 Security Awareness Roles and Percentage of Time... 3.1.1 Security Awareness Roles and Percentage of Time..."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 5)"}, {"role": "assistant", "content": "................................................................................. 1\n\nSymbols and abbreviated terms......................................................................................\n1\n\nDocument organization .................................................................................................... 1\n\nGeneral....................................................................................................................... 1\n\nModification ................................................................................................................ 2\n\nCMVP-approved security function requirements ........................................................... 2\n\nPurpose ...................................................................................................................... 2\n\nApproved security functions ........................................................................................ 2\n\nAppendix A. Document Revisions ....................................................................................... 3\n\n## Scope\n\nThis document specifies the Cryptographic Module Validation Program (CMVP)-approved security functions and supersedes those specified in International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 19790 Annex C and ISO/IEC 24759 paragraph 6.15. This document also supersedes SP 800-140Cr1. ## Normative references\n\nThis section identifies the normative references cited as ISO/IEC 19790 and ISO/IEC 24759. The specific editions to be used are ISO/IEC 19790:2012 and ISO/IEC 24759:2017. Please note that the version 19790:2012 referenced here includes the corrections made in 2015. National Institute of Standards and Technology (2019) Security Requirements for Cryptographic Modules . (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 140-3."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\nNIST is in the process of evaluating public-key digital signature algorithms for potential\nstandardization to protect sensitive information into the foreseeable future, including after\nthe advent of quantum computers. Any signature scheme that is eventually selected would\naugment FIPS 204, Module-Lattice-Based Digital Signature Standard; FIPS 205, Stateless\nHash-Based Digital Signature Standard; FIPS 186-5, Digital Signature Standard (DSS); and\nSP 800-208, Recommendation for Stateful Hash-Based Signature Schemes. This report de-\nscribes the evaluation criteria and selection process of the First Round of the Additional\nDigital Signatures for the NIST Post-Quantum Cryptography (PQC) Standardization Process.\nBased on public feedback and internal reviews of the first-round candidates, NIST selected\n14 candidate algorithms to move forward to the second round of evaluation: CROSS, FAEST,\nHAWK, LESS, MAYO, Mirath (merger of MIRA/MiRitH), MQOM, PERK, QR-UOV, RYDE, SDitH,\nSNOVA, SQIsign, and UOV.\n\n2. Evaluation Criteria and the Selection Process . . . . . . . . . . . . . . . . . . . . . .\n\nEvaluation Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.1.2. 3.1.2), and destroy (see Sec. 3.1.2) or destroy (see Sec."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 10)"}, {"role": "assistant", "content": ".................................................................... | Nonce............................................................................................................................\n| 21 |\n| 5.5 | Domain Parameters........................................................................................................ | Domain Parameters........................................................................................................ | 23 |\n| | 5.5.1 | Domain-Parameter Selection/Generation .......................................................... | 23 |\n| | | 5.5.1.1 FFC Domain Parameter Selection/Generation...................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Configuration Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\n2 | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology..........................................................................................................\n2 |\n| Study | Study | 2 |\n| 3.2. Data Collection............................................................................................................ | 3.2. Data Collection............................................................................................................ | ................................................................................................................. 3 |\n| 3.3. Data Analysis | 3.3. Data Analysis | .............................................................................................................. 3 |\n| | Participant and Organization Demographics..............................................................."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\nThis implies that threat analysis must consider both the type of threat and the various phases of the supply chain in which the threat is most effective. Moreover, one or more adversaries from different stages of supply chain can collaborate to compromise a hardware, which increases the severity of threats. Such insider threats are called collusion threats [6]. This work proposes a framework for analyzing different threats and how collusion among adversaries can affect the severity of threats. This analysis is divided into five distinct stages that discuss adversaries' intent, access, and resources, and how their collusion affects the severity of different threats. The framework is shown in Fig. 2. The framework incorporates threats across all stages of supply chain including insider threats. - [1] DARPA (2020) DARPA Selects Teams to Increase Security of Semiconductor Supply Chain. Available at https://www.darpa.mil/news/2020/semiconductor-supply-chainsecurity\n- [2] DARPA (2021) Expanding Domestic Manufacturing of Secure, Custom Chips for Defense Needs. Available at https://www.darpa.mil/news-events/2021-03-18\n- [3] NSWC Crane Corporate Communications (2019) NSWC Crane leverages OTA to ensure that the U.S. Government has access to secure state-of-the-art design, assembly, packaging and test for state-of-the-art microelectronics. Available at https://www.navsea.navy.mil/Media/News/Article/2005099/nswc-crane-leverages-otato-ensure-that-the-us-government-has-access-to-secure/\n- [4] Institute for Systems Research (2020) AFRL-Northrop Grumman: Locked Electronics for Assured Design (LEAD): Delay Locking ASIC IP Blocks to Protect Functionality. Available at https://isr.umd.edu/research-funding/afrl-northrop-grumman-locked-electronicsassured-design-lead-delay-locking-asic-ip\n- [5] Wolfe F (2020) Aether Spy Next-Generation Multi-Function Radar to Advance, Northrop Grumman Says. Defense Daily ."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 7)"}, {"role": "assistant", "content": "| 1 | | 1.1 | | Purpose and Scope...................................................................................................1 | | | | 1.2 | Audience ...................................................................................................................1 | | | | 1.3 | Document Structure | ..................................................................................................1 | | 2."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nHPC file systems in the data storage zone provide superior data access speed and much larger storage capacity compared to average enterprise file systems. Hard disk failure is a threat due to the large number of disks deployed in the data storage zone. Incident response and contingency planning controls may not be easy to implement, and file backup, recovery, and forensic imaging may become infeasible. The security measures that can be implemented on the enterprise file systems may take an unacceptably long time and degrade HPC file system performance in an unacceptable way."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.4.4. 3.4.4). 3.4.4)\nwith a defined and implementable set of assurance levels and a final set of\ncontrols for the online service."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.4.4", "cmmc_practice_id": "CM.L2-3.4.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide? (Part 5)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 2. Preliminaries.......................................................................... | 3 |\n| 2.1. Auxiliary Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 7 |\n| 3. Ascon Permutations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.1. Internal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.2. Constant-Addition Layer 𝑝 𝐶 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.3. Substitution Layer 𝑝 𝑆 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 9 |\n| 3.4. Linear Diffusion Layer 𝑝 𝐿 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 4."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| 2.1 | BACKGROUND | BACKGROUND | BACKGROUND | 16 | |-------|------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|------| | | 2.1.1 | PCIE - EDP Systems Review and Security Work Group | PCIE - EDP Systems Review and Security Work Group | 16 | | | 2.1.2 | System Development Life Cycle | System Development Life Cycle | 16 | | 2.2 | OPERATING ENVIRONMENT | OPERATING ENVIRONMENT | OPERATING ENVIRONMENT | 17 | | | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 17 | | | 2.2.1.1 IRM Planning | 2.2.1.1 IRM Planning | 2.2.1.1 IRM Planning | 17 | | | 2.2.1.2 Using Policy/Procedures/Standards | 2.2.1.2 Using Policy/Procedures/Standards | 2.2.1.2 Using Policy/Procedures/Standards | 18 | | | 2.2.1.2.1 | 2.2.1.2.1 | References Used by the Life Cycle Matrix | 19 | | | 2.2.1.2.2 | 2.2.1.2.2 | Major GSA References | 21 | | | 2.2.2 AIS Development Methodologies | 2.2.2 AIS Development Methodologies | 2.2.2 AIS Development Methodologies | 21 | | | 2.2.3 Project Administration and Control | 2.2.3 Project Administration and Control | 2.2.3 Project Administration and Control | 23 |"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nl enterprise resources is granted on a per -session basis. In an ideal zero trust architecture, every unique operation would undergo authentication and authorization before the operation is performed.\nFor example, a delete operation following a read operation to a database should trigger an additional authentication and authorization check. This level of granularity may not always possible and other mitigating solutions such as logging and backups, may be needed to detect and recover from unauthorized operations. Enterprise administrators will need to plan how to enforce fine grain access policies on individual resources. If the security tools used by"}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nthat plans are made for controls against theft and error, appropriate\naudit trails, conformity with management objectives and with the law,\nsufficient documentation, appropriate design approval mechanisms, and\ngeneral efficiency and economy.\ndit would check that the application conforms to standards and the la-\ntest design specifications, and that the internal controls and reliabil\nity of data are sound.\narea, audit would verify that the organization structure, the physical\nfacilities, the personnel management, the back-up capability, and the\nsoftware/hardware controls all help meet management's objectives.\n\n4. Management controls to ensure that security objectives are\nachieved fit into three categories— policies that are formulated\nat the top, procedures for administrative, physical, and technical\nsecurity measures, and practices for the standard management ac-\ntivities .\n5. ADP security controls should include a) administrative safe-\nguards in the form of contingency plans, security documentation,\nauthorization control lists, program access controls, personnel\nrules; b) physical security safeguards such as area restrictions,\ndisaster back-up, storage libraries, disposal procedures; and c)\ntechnical security in the form of a security system to handle data\nand files, program libraries, operating system(s), teleprocessing,\nand encryption.\n6. Training is needed for systems people as well as users.\n\nAdministrative Services at the American In-\nstitute of Certified Public Accountants, with\nresponsibility for internal applications of\nthe computer as well as development of its\nuse in the accounting and auditing practices\nHis administrative responsibil-\nof members.\nities include Personnel, Purchasing, Office\nManagement, Printing and Shipping.\nmember of AICPA, he has served on a number of\nits committees in the computer area, in-\ncluding the chairmanship of the EDP Auditing\nHe is a former member of the\nCommittee.\nComputer Committee of the New York State\nSociety of CPA's."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Incident Response?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| | Documentation ( continued ) | 4."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n| 5.2.1 | Scenario 1: Protect Host from Malware Infection via USB..................................... | 37 |\n|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| 5.2.2 | Scenario 2: Protect Host from Malware Infection via Network Vector.................. | 37 |\n| 5.2.3 | Scenario 3: Protect Host from Malware via Remote Access Connections ............. | 39 |\n| 5.2.4 | Scenario 4: Protect Host from Unauthorized Application Installation ................... | 40 |\n| 5.2.5 | Scenario 5: Protect from Unauthorized Addition of a Device ................................ | 42 |\n| 5.2.6 | Scenario 6: Detect Unauthorized Device-to-Device Communications................... | 43 |\n| 5.2.7 | Scenario 7: Protect from Unauthorized Deletion of Files....................................... | 43 |\n| 5.2.8 | Scenario 8: Detect Unauthorized Modification of PLC Logic.................................. | 45 |\n| 5.2.9 | Scenario 9: Protect from Modification of Historian Data....................................... | 46 |\n| 5.3.1 | PR.AC-1: Identities and Credentials are Issued, Managed, Verified, Revoked, and Audited for Authorized Devices, Users, and Processes........................ | 50 |\n| 5.3.2 | PR.AC-3: Remote Access is Managed ..................................................................... | 50 |\n| 5.3.3 | PR.AC-4: Access Permissions and Authorizations are Managed, Incorporating the Principles of Least Privilege and Separation of Duties ........................."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n2.3.2. Authenticator and Verifier Requirements . . . . . . . . . . . . .\n\n3.2. General Authenticator Requirements . . . . . . . . . . . . . . . . . . .\n\n3.2.1. Physical Authenticators"}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 8)"}, {"role": "assistant", "content": "hed in 2009. Since this initial version, there have been three SCAP v1 revisions. The current revision, SCAP 1.3, was released in February 2018 as NIST Special Publication (SP) 800-126 Revision 3 [2].\nOver its lifetime, a few critical gaps have been identified in SCAP v1 that need to be addressed to provide a more robust solution:\n\nLimited Coverage of Endpoint Types: Maintaining an adequate level of security for enterprise managed endpoints requires up-to-date knowledge of the posture of those devices. SCAP v1 has focused largely on desktops, laptops, and servers, leaving network (i.e., routers, switches, firewalls), mobile, and Internet of Things (IoT) devices lacking in support or not supported. In today's network, these under-supported devices are an increasing area of security risk that must be managed and protected. Stale Security Posture Information: Many SCAP v1 implementations use a periodic scanning approach when collecting and evaluating endpoint posture. Relying on periodic scanning allows critical security-relevant events to go unnoticed for lengthy periods of time. Even worse, attackers can clean up after themselves between collections, preventing detection. This reduces visibility of security-relevant changes and can create a false sense of security for enterprises. No Component-level Interoperability: SCAP v1 products that support different use cases often require similar information, such as software inventory and configuration information. While SCAP v1 supports data interoperability, control of collected posture information and evaluation remains with each tool. The lack of standardized interfaces between tools prevents transport layer interoperability, forces redundant posture information collection and evaluation that adds to system and network load, reduces modularity of solutions, and increases integration costs."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n☐ Include C-SCRM responsibilities and performance requirements in personnel descriptions to ensure clarity and improve accountability."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n## Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography\n\n## Establishment Schemes Using Discrete Logarithm Cryptography\n\nDiffie-Hellman; elliptic curve cryptography; finite field cryptography; key agreement; key confirmation; key derivation; key establishment; MQV."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nlearly defined and\n- o The interactions of the logical object of the software or firmware module with the operating system and other supporting applications resident within the cryptographic boundary.\n- o Tested Operational Environment's Physical Perimeter (TOEPP) - The location of the cryptographic module with respect to the TOEPP that is part of the module's tested configuration but may be outside of the module's cryptographic boundary so that all of the logical and physical layers between the cryptographic module and the TOEPP are clearly defined. This also includes a description and components list of the TOEPP. - Precise definition of the module's physical TOEPP and cryptographic boundariesy"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n..................................9 |\n| 3.1.4. Attack Targets (Assets).................................................................................................................9 |\n| 3.1.5.\nTypes of Exploits.........................................................................................................................10 |\n| 3.2.1. Baseline Security ........................................................................................................................11 |\n| 3.2.2. Controls for Interacting With SCM Systems...............................................................................12 |\n| 4. CI/CD Pipelines -Background, Security Goals, and Entities to be Trusted .....................................13 |\n| 5. Integrating SSC Security Into CI/CD Pipelines.................................................................................15 |\n| 5.1.1. Secure Build................................................................................................................................16 |\n| 5.1.2. Secure Pull-Push Operations on Repositories............................................................................17 |\n| 5.1.3. Integrity of Evidence Generation During Software Updates......................................................18 |\n| 5.1.4. Secure Code Commits ................................................................................................................19 |"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.5.1. 3.5.1."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nteristics. In other environments, especially those in which users have full control over their hosts and network management is not centralized, it might be challenging to link a machine to a location.\nFor example, an administrator might know that the host at address 10.3.1.70 appears to be infected but not have any idea where that machine resides or who uses it. Administrators might need to track down an infected host through network devices. For example, a switch port mapper can poll switches for a particular IP address and identify the switch port number and host name associated with that IP address. If the infected host is several switches away, it can take hours to track down a single machine; if the infected host is not directly switched, the administrator might still need to manually trace connectivity through various wiring closets and network devices. An alternative is to pull the network cable or shut down the switch port for an apparently infected host and wait for a user to report an outage. This approach can inadvertently cause a loss of connectivity for small numbers of uninfected hosts, but if performed carefully as a last-resort identification and containment method, it can be quite effective."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 4)"}, {"role": "assistant", "content": "ederal systems and organizations is important to federal agencies and can directly impact the ability of the Federal Government to successfully carry out its assigned missions and business operations.\nThis publication provides federal agencies and nonfederal organizations with assessment procedures that can be used to carry out assessments of the requirements in NIST Special Publication 800172, Enhanced Security Requirements for Protecting Controlled Unclassified Information: A Supplement to NIST Special Publication 800-171 . The assessment procedures are flexible and can be tailored to the needs of organizations and assessors. Assessments can be conducted as 1) self-assessments; 2) independent, third-party assessments; or 3) government-sponsored assessments. The assessments can be conducted with varying degrees of rigor based on customer-defined depth and coverage attributes. The findings and evidence produced during the assessments can be used to facilitate risk-based decisions by organizations related to the CUI enhanced security requirements. ## Keywords\n\nassessment; assessment method; assessment object; assessment procedure; assurance; enhanced security requirement; enhanced security requirement assessment; Controlled Unclassified Information; coverage; CUI Registry; depth; Executive Order 13556; FISMA; NIST Special Publication 800-53; NIST Special Publication 800-53A; NIST Special Publication 800-171; NIST Special Publication 800-172; NIST Special Publication 800-172A; nonfederal organization; nonfederal system; security assessment; security control."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nactivities. In addition to federal personnel, RBT applies to contractors providing services to federal organizations. 'Training for a 'new in role' and 'refresher training' needs are quite different.\n'New in role' training needs to establish foundations for success not just a lecture on responsibilities. 'Refresher training' needs to focus on recent changes (e.g., in guidance, threat categories) and how to remain effective in the role. Nothing loses the audience faster than providing 'new in role' training to people that have been doing this for years.' (Q23)"}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Incident Response?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nDocument maintenance requirements for the IoT device, such as: a. Cybersecurity maintenance expectations and associated instructions or procedures for the customer (e.g., account management, local and/or remote maintenance activities, and vulnerability/patch management plan) b. When maintenance will be performed by supporting parties that will need access (remote or onsite) to customer's IoT devices and their information security contract requirements c. Cybersecurity considerations of the maintenance process (e.g., how does customer data unrelated to the maintenance process remain confidential even to maintainers) | • Documentation of cybersecurity information enables better understanding of the potential risks related to the IoT device, which can inform customers and others in the IoT device ecosystem and guide on- going risk mitigation support. • Documentation helps personnel with the responsibility of securing IoT devices within the system understand the implementation and operation of controls and prevent misuse and compromise by unauthorized entities. • Documentation may be used to supply information about and support the management of supply chain risk, incident response, and other critical cybersecurity functions. | ( see above) |"}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 6)"}, {"role": "assistant", "content": "e of Standards and Technology (2019) Security Requirements for Cryptographic Modules . (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 140-3.\nhttps://doi.org/10.6028/NIST.FIPS.140-3\n\n## Terms and definitions\n\nThe following terms and definitions supersede or are in addition to ISO/IEC 19790. None at this time\n\n## Symbols and abbreviated terms\n\nThe following symbols and abbreviated terms supersede or are in addition to ISO/IEC 19790 and ISO/IEC 24759 throughout this document:\n\n## CMVP\n\nCryptographic Module Validation Program\n\n## FIPS\n\nFederal Information Processing Standard\n\n## ISO/IEC\n\nInternational Organization for Standardization/International Electrotechnical Commission\n\n## Document organization\n\n## General\n\nSection 6 of this document replaces the approved security functions of ISO/IEC 19790 Annex C and ISO/IEC 24759 paragraph 6.15. This document also supersedes SP 800-140Cr1. ## Modification\n\nThis publication is a complete replacement of the approved security functions of ISO/IEC 19790 Annex C and ISO/IEC 24759 paragraph 6.15. There are no other modifications, additions, or deletions. ## CMVP-approved security function requirements\n\n## Purpose\n\nThis document identifies CMVP-approved security functions. It precludes the use of all other security functions. ## Approved security functions\n\nFor the current list of CMVP-approved security functions, see https://csrc.nist.gov/projects/cmvp/sp800-140c. ## Appendix A."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes assist with maintaining cross-references | |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ID.RA-09 | The authenticity and integrity of hardware and software are assessed prior to acquisition and use | Medium | N1: See the notes for ID.RA."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Risk Assessment?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Device Identification : The IoT device can be uniquely identified logically and physically."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nlishment schemes. | Additional input | Information known by two parties that is cryptographically bound to the secret keying material being protected using the encryption operation.\n|\n|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Algorithm | A clearly specified mathematical process for computation; a set of rules that, if followed, will give a prescribed result. |\n| Approved | FIPS- approved or NIST-Recommended. An algorithm or technique that is either 1) specified in a FIPS or NIST Recommendation, or 2) adopted in a FIPS or NIST Recommendation and specified either (a) in an appendix to the FIPS or NIST Recommendation, or (b) in a document referenced by the FIPS or NIST Recommendation. |\n| Assumption | Used to indicate the conditions that are required to be true when an approved key-establishment scheme is executed in accordance with this Recommendation. |\n| Assurance of private key possession | Confidence that an entity possesses a private key associated with a given public key. |\n| Assurance of validity | Confidence that an RSA key pair is arithmetically correct."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "e of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management.\nFigure 1: Risk Management 3-Tiered Approach\n\n\n\nThe 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. The security controls in SP 800-53 Rev. 4 support Step Two of the RMF, and a detailed catalog of these controls is provided in Appendix F. For ease of use in the security control selection and specification process, controls are organized into eighteen families, each containing security controls related to the general security topic of the family. Security controls involve aspects of policy, oversight, supervision, manual processes, individual actions, or automated mechanisms implemented by information systems/devices. The security control structure consists of the\n\nfollowing components: (i) a control section; (ii) a supplemental guidance section; (iii) a control enhancements section; (iv) a references section; and (v) a priority and baseline allocation section."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 10)"}, {"role": "assistant", "content": "ty. These standards can be found in formal documents from organizations such as the Internet Engineering Task Force (IETF) [8], International Organization for Standardization (ISO) [9], and NIST [10].\nLikely due to the U.S. locations of most of the study organizations, the participants most often mentioned cryptographic requirements issued by NIST. As perhaps the best known government standard, the Federal Information Processing Standards Publication (FIPS) 140-2 'specifies the security requirements that will be satisfied by a cryptographic module utilized within a security system protecting sensitive but unclassified information\" [7]. These requirements are mandatory for cryptographic products purchased by the U.S. Government, but also are used voluntarily outside the government. There are two testing and validation programs associated with FIPS 140-2. The NIST Cryptographic Algorithm Validation Program (CAVP) provides guidelines that support conformance testing of FIPS-approved and other NIST-recommended cryptographic algorithms specified in special publications (SPs) [11]. CAVP is a prerequisite of the Cryptographic Module Validation Program (CMVP) which provides the validation of cryptographic modules [12]. Under these programs, vendors may submit algorithm and module implementations to any testing laboratory accredited under the National Voluntary Laboratory Accreditation Program (NVLAP) [13]. Labs perform certification testing, and NIST validates lab results. ## Study Methodology\n\nThe research team conducted in-depth interviews of individuals working in organizations that develop products that use cryptography. The study was approved by the NIST institutional review board. Prior to the interviews, participants were informed of the purpose of the study and how their data would be used and protected. Interview data were collected and recorded without personal identifiers and not linked back to the participants or organizations."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 10)"}, {"role": "assistant", "content": "materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately.\nSuch identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. Domain name and IP addresses shown in this guide represent an example domain and network environment to demonstrate the NCCoE project use case scenarios and the security capabilities. National Institute of Standards and Technology Special Publication 1800-10B, Natl. Inst. Stand. Technol. Spec. Publ. 1800-10B, 149 pages, March 2022, CODEN: NSPUE2\n\n## FEEDBACK\n\nAs a private-public partnership, we are always seeking feedback on our practice guides. We are particularly interested in seeing how businesses apply NCCoE reference designs in the real world. If you have implemented the reference design, or have questions about applying it in your environment, please email us at manufacturing\\_nccoe@nist.gov. All comments are subject to release under the Freedom of Information Act (FOIA). National Cybersecurity Center of Excellence National Institute of Standards and Technology 100 Bureau Drive Mailstop 2002 Gaithersburg, MD 20899\n\nEmail: nccoe@nist.gov\n\n## NATIONAL CYBERSECURITY CENTER OF EXCELLENCE\n\nThe National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity issues. This public-private partnership enables the creation of practical cybersecurity solutions for specific industries, as well as for broad, cross-sector technology challenges."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 3)"}, {"role": "assistant", "content": "h to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. Submit comments on this publication to:\n\ncyberhygiene@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nEnterprise patch management is the process of identifying, prioritizing, acquiring, installing, and verifying the installation of patches, updates, and upgrades throughout an organization. Patching is more important than ever because of the increasing reliance on technology, but there is often a divide between business/mission owners and security/technology management about the value of patching."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.5.2 | A Simple Scoring Approach | A Simple Scoring Approach | 60 |\n| | 3. 3.5.2 | Systems Initiation Phase Audit Tests Program | 86 |\n| | 4. 3.5.2 A Simple Scoring Approach\n\nThe simple approach assigns a weight and a risk level to each dimension, based on a qualitative judgement with respect to the characteristics associated with each dimension."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 9)"}, {"role": "assistant", "content": "organization\n\n## General\n\nSection 6 of this document replaces the approved sensitive security parameter generation and establishment methods of ISO/IEC 19790 Annex D and ISO/IEC 24759 paragraph 6.16.\nThis document also supersedes SP 800-140Dr1. ## Modification\n\nThis publication is a complete replacement of the CMVP-approved sensitive security parameter generation and establishment methods of ISO/IEC 19790 Annex C and ISO/IEC 24759 paragraph 6.16. There are no other modifications, additions, or deletions. ## CMVP-approved sensitive security parameter generation and establishment requirements\n\n## Purpose\n\nThis document identifies CMVP-approved sensitive security parameter generation and establishment methods. These are considered CMVP-approved security functions. It precludes the use of all other sensitive security parameter generation and establishment methods. ## Sensitive security parameter generation and establishment methods\n\nFor the current list of CMVP-approved sensitive security parameter generation and establishment methods, see https://csrc.nist.gov/projects/cmvp/sp800-140d. ## Appendix A."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Planning?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.3.1 Scenario\n\nThe following scenario was simulated to test the architecture's defense against data integrity events that occur on virtual machines."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe scope of the assessments conducted using the procedures described in this publication is guided and informed by the system security plans for the organizational systems processing, storing, or transmitting CUI. The assessments focus on the overall effectiveness of the security safeguards intended to satisfy the enhanced security requirements defined in [SP 800-172].\n\nAssessments can be conducted by system developers, system integrators, system owners, evaluators, auditors, or the security staff of organizations. The assessors or assessment teams begin by obtaining and reviewing the results from individual component product or compliance assessments. The assessors then determine the additional system-level assessments required to achieve the needed assurance using the procedures and methods contained in this publication and based on the specific implementation information provided by nonfederal organizations in their system security plans. Assessments can be used to compile and evaluate the evidence needed by organizations to determine the effectiveness of the safeguards implemented to protect CUI, the actions needed to mitigate security-related risks, and compliance to the enhanced security requirements."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Access Control\n\n## Getting Started with Access Control"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Maintenance?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |-----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Software Update : The IoT device's software can be updated by authorized entities only using a secure and configurable mechanism."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\narchitecture; configuration; endpoint; endpoint security; SCAP; security automation; security content automation; Security Content Automation Protocol; software identification; SWID; vulnerability\n\n| 1 | Introduction ............................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| 2 Gaps in SCAP | v1....................................................................................................2 |\n| 3 SCAP | v2..................................................................................................................3 |\n| 3.1 Design Goals for SCAP v2.............................................................................. | 3 |\n| 3.2 The SCAP v2 | Architecture.............................................................................. 4 |\n| 3.3 Adoption of International Standards | in SCAP v2 ............................................"}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nThe importance of privacy engineering and incorporating technical design requirements was also emphasized. Participants asked for clear, robust examples and informative references within documents to support best practices. Participants also highlighted the need for using an established taxonomy and terminology for consistency and clarity when discussing privacy. Participants also pointed out that a comprehensive understanding of the data processing ecosystem's complexity and interconnectedness is vital for integrating privacy objectives. This includes maintaining confidentiality, integrity, and availability in IoT, and proactively managing privacy risks."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT).\nITL’s responsibilities include the development\nof management, administrative, technical, and physical standards and guidelines for the cost-\neffective security of other than national security-related information in federal information\nsystems. The Special Publication 800-series reports on ITL’s research, guidelines, and outreach\nefforts in information systems security and privacy and its collaborative activities with industry,\ngovernment, and academic organizations. Abstract\n\nThis publication provides a catalog of security and privacy controls for information systems and\norganizations to protect organizational operations and assets, individuals, other organizations,\nand the Nation from a diverse set of threats and risks, including hostile attacks, human errors,\nnatural disasters, structural failures, foreign intelligence entities, and privacy risks. The controls\nare flexible and customizable and implemented as part of an organization-wide process to\nmanage risk. The controls address diverse requirements derived from mission and business\nneeds, laws, executive orders, directives, regulations, policies, standards, and guidelines. Finally,\nthe consolidated control catalog addresses security and privacy from a functionality perspective\n(i.e., the strength of functions and mechanisms provided by the controls) and from an assurance\nperspective (i.e., the measure of confidence in the security or privacy capability provided by the\ncontrols). Addressing functionality and assurance helps to ensure that information technology\nproducts and the systems that rely on those products are sufficiently trustworthy."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.2.1 Job Classifications... 3.2.1 Job Classifications... 3.2.1 Job Classifications..."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 2)"}, {"role": "assistant", "content": "systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 2)"}, {"role": "assistant", "content": "ory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nNon-technical supporting capabilities are actions a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\nMany U.S. Government Information Technology (IT) systems need to employ wellestablished cryptographic schemes to protect the integrity and confidentiality of the data that they process. Algorithms such as the Advanced Encryption Standard (AES) as defined in Federal Information Processing Standard (FIPS) 197, 1 and the Keyed-Hash Message Authentication Code (HMAC) as defined in FIPS 198 2 make attractive choices for the provision of these services. These algorithms have been standardized to facilitate interoperability between systems. However, the use of these algorithms requires the establishment of keying material between the participating entities in advance. Trusted couriers may manually distribute this secret keying material. However, as the number of entities using a system grows, the work involved in the distribution of the secret keying material could grow rapidly. Therefore, it is essential to support the cryptographic algorithms used in modern U.S. Government applications with automated key-establishment schemes. | Algorithm | A clearly specified mathematical process for computation; a set of rules that, if followed, will give a prescribed result."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\ner software or systems. A patch could even be compromised. - Unpatchable assets. This is the implementation of isolation or other methods to mitigate the risk of systems that cannot be easily patched.\nThis is typically required if routine patching is not able to accommodate these systems within a reasonable time frame. Examples of why an asset may be unpatchable include the vendor not providing patches (e.g., asset is at end-of-life, asset does not support updates) or an asset needing to run uninterrupted for an extended period of time because it provides mission-critical functions. Unpatchable assets need to be included in risk response planning because a new vulnerability in an asset might necessitate a change in the methods needed to mitigate its risk."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.4. General Customer Experience Requirements . . . . . . . . . . . . . . .\n\n4.3.4. Evidence Validation . . . . . . . . . . . . . . . . . . . . . . . .\n\n16. CSPs MAY implement fraud mitigation measures as compensating controls.\nWhen this is done, these SHALL be documented as deviations from the\nnormative guidance of these guidelines and SHALL be conveyed to all RPs\nthrough a Digital Identity Acceptance Statement (DIAS) prior to integration. See\nSec. 3.4.4 of [SP800-63] for more information about the DIAS."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\ning security and privacy risk that includes information security categorization; control selection, implementation, and assessment; system and common control authorizations; and continuous monitoring.\nThe RMF includes activities to prepare organizations to execute the framework at appropriate risk management levels. The RMF also promotes near real-time risk management and ongoing information system and common control authorization through the implementation of continuous monitoring processes; provides senior leaders and executives with the necessary information to make efficient, cost-effective, risk management decisions about the systems supporting their missions and business functions; and incorporates security and privacy into the system development life cycle. Executing the RMF tasks links essential risk management processes at the system level to risk management processes at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Contingency Planning Guide for Federal Information Systems provide? (Part 3)"}, {"role": "assistant", "content": "et (OMB) Circular A-130, Section 8b(3), 'Securing Agency Information Systems,' as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III.\nThis guideline has been prepared for use by federal agencies. It may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright. Attribution would be appreciated by NIST. Nothing in this document should be taken to contradict standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. NIST Special Publication 800-34, Revision 1, 150 pages\n\n(May 2010)\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Compliance with NIST Standards and Guidelines\n\nNIST develops and issues standards, guidelines, and other publications to assist federal agencies in implementing the Federal Information Security Management Act (FISMA) of 2002 and in managing costeffective programs to protect their information and information systems. - Federal Information Processing Standards (FIPS) are developed by NIST in accordance with FISMA. FIPS are approved by the Secretary of Commerce and are compulsory and binding for federal agencies. Since FISMA requires that federal agencies comply with these standards, agencies may not waive their use. - Guidance documents and recommendations are issued in the NIST Special Publication (SP) 800series."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\nMean for Your Hardware? Available at https://evernex.com/industry-guide/eol-meaning/\n- [9] Vincent J (2018) Chinese spies reportedly inserted microchips into servers used by Apple, Amazon, and others.\nAvailable at https://www.theverge.com/2018/10/4/17935868/-chinese-spies-microchip-hackservers-apple-amazon-supermicro\n- [10] Yu S, Liu W, O'Neill M (2019) An improved automatic hardware Trojan generation platform. IEEE Computer Society Annual Symposium on VLSI (ISVLSI) (IEEE, Miami, Florida), pp 302-307. https://doi.org/10.1109/ISVLSI.2019.00062\n- [11] Cruz J, Huang Y, Mishra P, Bhunia S (2018) An automated configurable Trojan insertion framework for dynamic trust benchmarks. Design, Automation & Test in Europe Conference & Exhibition (IEEE, Dresden, Germany) pp 1598-1603. https://doi.org/10.23919/DATE.2018.8342270\n- [12] Perez TD, Pagliarini S (2023) Hardware Trojan insertion in finalized layouts: From methodology to a silicon demonstration. IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems (IEEE) 42(7): 2094-2107. https://doi.org/10.1109/TCAD.2022.3223846"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 3)"}, {"role": "assistant", "content": "ion in federal information systems. ## Abstract\n\nNon-technical supporting capabilities are actions a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device.\nThis publication defines an Internet of Things (IoT) device manufacturers' non-technical supporting capability core baseline , which is a set of non-technical supporting capabilities generally needed from manufacturers or other third parties to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems. The purpose of this publication is to provide organizations a starting point to use in identifying the non-technical supporting capabilities needed in relation to IoT devices they will manufacture, integrate, or acquire. This publication is intended to be used in conjunction with NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers and NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline. ## Keywords\n\ncybersecurity baseline; Internet of Things (IoT); securable computing devices. ## Acknowledgments\n\nThe authors wish to thank all contributors to this publication, including the participants in workshops and other interactive sessions; the individuals and organizations from the public and private sectors, including manufacturers from various sectors as well as several manufacturer trade organizations, who provided feedback on the preliminary public content, and colleagues at NIST who offered invaluable inputs and feedback. Special thanks to Cybersecurity for IoT team members Brad Hoehn and David Lemire and the NIST FISMA (Federal Information Security Modernization Act) Implementation Project team for their extensive help. ## Audience\n\nThe main audience for this publication is IoT device manufacturers, especially with the emerging role of product security officers. This publication may also help IoT device customers or integrators."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 9)"}, {"role": "assistant", "content": "ework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53].\nThe security control mappings can be useful to organizations that wish to demonstrate compliance to the security requirements in the context of their established information security programs when such programs have been built using the NIST security controls. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\nA Proposed Metric for Vulnerability Exploitation Probability\n\nMell P, Spring J (2025) Likely Exploited Vulnerabilities: A Proposed Metric for Vulnerability Exploitation Probability. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 41. https://doi.org/10.6028/NIST.CSWP.41\n\nThis work presents a proposed security metric to determine the likelihood that a vulnerability has been observed to be exploited. Only a small fraction of the tens of thousands of software and hardware vulnerabilities that are published every year will be exploited. Predicting which ones is important for the efficiency and cost effectiveness of enterprise vulnerability remediation efforts. Currently, such remediation efforts rely on the Exploit Prediction Scoring System (EPSS), which has known inaccurate values, and Known Exploited Vulnerability (KEV) lists, which may not be comprehensive. The proposed likelihood metric may augment EPSS remediation (correcting some inaccuracies) and KEV lists (enabling measurements of comprehensiveness). However, collaboration with industry is necessary to provide necessary performance measurements."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n(e.g., draft -ietf-netconf-overtls13). | Analytics | The discipline that applies logic and mathematics to data to provide insights for event recognition and for making response decisions.\nIn this project, the function is executed by a set of tools for examining unencrypted payloads to identify undesired char acteristics. |\n|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Bounded-Lifetime Key | A key variable that is used within the enterprise for decryption in real time or is stored for a period established by an explicit enterprise policy to enable decryption for post- facto security analytics/forensics purposes and is then destroyed in accordan ce with the policy. |\n| Break and Inspect | A function that taps, decrypts, terminates, and re- encrypts/reinitiates network traffic. |\n| Certificate | A set of data that uniquely identifies a public key (which has a corresponding private key) and an owner that is authorized to use the key pair. The certificate contains the owner's public key and possibly other information and is digitally signed by a certificate authority (i.e., a trusted party), thereby binding the public key to the owner. |\n| Certificate Authority | An authorized entity that stores, signs, and issues digital cryptographic key certificates. It acts to validate identities and bind them to cryptographic key pairs with digital certificates."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide? (Part 10)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . . . . . . . . . . . | 30 |\n| Figure 9. Mapping between state words, bytes, and bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 35 |\n| Figure 10.\nRepresentation of the Ascon state as 64-bit unsigned integers, byte se- quences, and bitstrings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 37 |\n\n## Acknowledgments\n\nThe authors of the standard express their gratitude to the Ascon designers -Christoph Dobraunig, Maria Eichlseder, Florian Mendel, and Martin Schläffer -for their valuable comments and suggestions during the standardization process. The authors also acknowledge and appreciate contributions from their colleagues at NIST during the selection process, including Lawrence Bassham, Çağdaş Çalık, Deukjo Hong, and Noah Waller. The authors also thank Elaine Barker, Luís T. A. N. Brandão, Lily Chen, Andrew Regenscheid, Noah Ross, Sara Kerman, Yu Long Chen, and Yu Sasaki for their technical and administrative support. ## 1. Introduction\n\nThis standard specifies the Ascon family of algorithms to provide Authenticated Encryption with Associated Data (AEAD), a hash function, and two eXtendable Output Functions (XOFs). The Ascon family is designed to be efficient in constrained environments. The algorithms included in this standard are as follows:\n\n1. Ascon-AEAD128 is a nonce-based AEAD scheme, offering 128-bit security strength in the single-key setting. 2. Ascon-Hash256 is a cryptographic hash function that produces a 256-bit hash of the input messages, offering a security strength of 128 bits. 3. Ascon-XOF128 is a XOF, where the output size of the hash of the message can be selected by the user, and the supported security strength is up to 128 bits. 4. Ascon-CXOF128 is a customized XOF that allows users to specify a customization string and choose the output size of the message hash. It supports a security strength of up to 128 bits."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Access Control on NoSQL Databases provide? (Part 7)"}, {"role": "assistant", "content": "..........................................................................................3 |\n| Fig. 2.\nWide-column database model..................................................................................................4 |\n| Fig. 3. Document database model.......................................................................................................5 |\n| Fig. 4. Graph database model.............................................................................................................5 |\n| Fig. 5. Hierarchical structure relationships of the key-value, wide-column, and document models .......8 |\n| Fig. 6. Directed graph relationship structure of the graph model .........................................................9 |\n| Fig. 7. Example of defining subject and object attributes for the key-value model..............................10 |\n| Fig. 8. Example of defining subject and object attributes for wide-column and document models......11 |\n| Fig. 9."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” support CMMC certification?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\n\n\n## NIST Interagency Report NIST IR 8562\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nKaterina N. Megas Michael Fagan Barbara Cuthill Brad Hoehn Evie Petrella\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8562\n\n\n\n## NIST Interagency Report NIST IR 8562\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nKaterina N. Megas Michael Fagan Barbara Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nBrad Hoehn HII\n\nEvie Petrella Electrosoft Services, Inc. This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8562\n\nApril 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nNational Institute of Standards and Technology\n\nCraig S. Burkhardt, Acting NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-03-21\n\n## How to Cite this NIST Technical Series Publication\n\nMegas K, Fagan M, Cuthill B, Hoehn N, and Petrella E (2025) Summary Report for 'Workshop on Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| ^ | 3.2.2 | Size of Review Task | Size of Review Task | 49 | |-----------|------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------|-----------| | 3.3 | BACKGROUND ON THE METHODOLOGY | BACKGROUND ON THE METHODOLOGY | BACKGROUND ON THE METHODOLOGY | 49 | | | 3.3.1 | The Invitational Workshop | The Invitational Workshop | 49 | | | 3.3.2 | Workshop Points of Agreement | Workshop Points of Agreement | 49 | | 3.4 | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | 50 | | | 3.4.1 | Assumptions and Caveats | Assumptions and Caveats | 50 | | | 3.4.2 | Audit Planning/Prioritization Process | Audit Planning/Prioritization Process | 51 | | | 3.4.3 | Non-Discretionary Audits | Non-Discretionary Audits | 51 | | | 3.4.4 | Risk Evaluation Levels and Dimensions | Risk Evaluation Levels and Dimensions | 53 | | | 3.4.5 | Two Level Work Priority Dimensions/Characteristics | Two Level Work Priority Dimensions/Characteristics | 54 | | | 3.4.5.1 Level I: | 3.4.5.1 Level I: | 3.4.5.1 Level I: | .....55 | | | 3.4.5.1.1 Mission Impact/Strategic Value/Organization | 3.4.5.1.1 Mission Impact/Strategic Value/Organization"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nThe VDPO should also notify the FCB if a vulnerability is found in an information system, product, or service used by others (e.g., other agencies, organizations, or the general public). Remediating such vulnerabilities typically requires the involvement of the product or service owner (e.g., vendor, supplier, provider) to produce and distribute a patch or update. VDPOs may also notify the product or service owner directly through existing support channels. In turn, the product or service owner should assist stakeholders in dealing with vulnerabilities until a product has reached the end of service. If the product or service owner chooses not to remediate all supported versions, a reasonable upgrade path to a version that has remediations should be provided. | | Part 1: Overview and Concepts (ISO, Geneva, Switzerland). Available at https://www.iso.org/standard/44378.html |\n|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [ISOIEC_27035] | International Organization for Standardization/International Electrotechnical Commission (2016) ISO/IEC 27035-1:2016 - Information technology - Security Techniques - Information security incident management - Part 1: Principles of incident management (ISO, Geneva, Switzerland)."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\nThe scores are created using a machine learning model trained with several thousand inputs. Training data is provided by a small number of enterprise security monitoring companies, each of which has a large, deployed sensor net to observe exploitation activity for their enterprise customers.\n\n## 3.2. Measurement of the Comprehensiveness of KEV Lists\n\nThis is not a mistake or flaw in the EPSS design; the documentation states that this is necessary to create a predictive machine learning model. The EPSS maintainers do use the knowledge of when vulnerabilities are observed to be exploited in training the EPSS model. However, they do not provide such knowledge as input to the model. That data is just used to train the probability output [1]."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 6)"}, {"role": "assistant", "content": "ents in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract.\n|\n|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| How do I know if I have CUI? | It is the responsibility of the federal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'? | The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\n## NIST Special Publication (SP) 1288GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> FEDERAL CYBERSECURITY ROLE-BASEDGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> TRAINING APPROACHES, SUCCESSES,GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> AND CHALLENGESGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold>\n\n## NIST Special Publication (SP) 1288GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> FEDERAL CYBERSECURITY ROLE-BASEDGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> TRAINING APPROACHES, SUCCESSES,GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> AND CHALLENGESGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold>\n\nHaney, JM, Jacobs, JL, Furman, SM (2023) Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges (National Institute of Standards and Technology Gaithers b urg, MD) NIST Special Publication (SP) 1288. https://doi.org/10.6028/NIST.SP.1288"}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- Packet filters and network address translation: Packet filtering and Network address translation (NAT) are used to monitor and control packets moving across a network interface, apply predetermined security rules, and obscure the internal network from the public internet. - Stateful inspection: Stateful firewalling, also known as dynamic packet filtering, monitors the state of connections and makes determinations as to what types of data packets belong to a known active connection and can be allowed to pass through the firewall. - Deep packet inspection (DPI): This feature, also known as packet sniffing, examines the content of packets (both the header and the payload, unlike the stateful inspection that inspects only the packet header). In addition to the capability provided by stateful inspection, this has capabilities related to finding hidden threats within the data stream, such as attempts at data exfiltration, violations of content policies, malware, and more. - Threat detection and response: Modern firewalls can gather and analyze enough data across multiple packets and sessions to detect threats and security incidents targeted at a particular system or a family of systems. These data from multiple firewalls can also be directed toward security information and event management (SIEM) and correlated with data from other security tools and IT systems to detect enterprise-wide attacks that span multiple systems and network layers. In addition, these data can be used to understand evolving threats and define new access rules, attack patterns, and defensive strategies [6]. - Logging and auditing capabilities: Logging and auditing capabilities result in the construction of network events that can be used to identify patterns of performance and security issues. - Access control functions: Access control functions enforce granular sophisticated access control policies."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\ntitle that reflects their duties, and they may lack sufficient professional skills (e.g., communications, relationship-building) that are viewed as essential in security awareness roles [SANS][WOELK].\nIn addition, the lack of understanding that security awareness is a unique discipline may lead to ill-prepared awareness professionals [BADA]. However, it is unclear if these challenges also apply to security awareness professionals in the United States (U.S.) government."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Profile of the IoT Core Baseline for Consumer IoT Products support CMMC certification?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\n\n\n## NIST Internal Report NIST IR 8425\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nMichael Fagan Katerina Megas Paul Watrobski Jeffery Marron Barbara Cuthill\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8425\n\n\n\n## NIST Internal Report NIST IR 8425\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nMichael Fagan Katerina N. Megas Paul Watrobski Jeffrey Marron Barbara B. Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8425\n\nSeptember 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n| Notation | Definition | |---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| | 𝐾 | 128-bit secret key | | 𝑁 | 128-bit nonce | | 𝐴 | Associated data | | 𝐴 𝑖 | 𝑖 th block of associated data 𝐴 | | 𝑃 | Plaintext | | 𝑃 𝑖 | 𝑖 th block of plaintext 𝑃 | | 𝐶 | Ciphertext | | 𝐶 𝑖 | 𝑖 th block of ciphertext 𝐶 | | 𝑍 | Customization string | | 𝑍 𝑖 | 𝑖 th block of customization string 𝑍 | | 𝑇 | 128-bit authentication tag | | 𝐼𝑉 | 64-bit constant initial value | | fail | Error message to indicate that the verification of authenticated cipher- text failed | | 𝑀 | Message | | 𝑀 𝑖 | 𝑖 th block of message 𝑀 | | 𝐻 | Hash value 𝐻 | | 𝐻 𝑖 | 𝑖 th block of hash value 𝐻 | | S | 320-bit internal state of the underlying permutation | | 𝑆 0 ,…,𝑆 4 | The five 64-bit words of the internal state S , where S = 𝑆 0 ‖ 𝑆 1 ‖ … ‖ 𝑆 4 | | 𝑠 (𝑖,𝑗) | 𝑗 th"}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\nCryptography is an essential component of modern computing. Unfortunately, implementing cryptography correctly is a non-trivial undertaking. Past research studies have supported this observation by revealing a multitude of errors and pitfalls in the cryptographic implementations of software products. However, the emphasis of these studies was on the practices of less-experienced, individual developers. Therefore, there is little understanding of the cryptographic development practices of organizations, including the benefits and challenges of using cryptographic resources such as standards specifications and libraries. To address this gap, a research team led by the National Institute of Standards and Technology (NIST) Information Technology Laboratory Visualization and Usability Group conducted a qualitative investigation into the processes and resources that organizations employ in the development and testing of cryptographic products. The study involved 21 in-depth interviews of 29 participants representing organizations that develop either a security product that uses cryptography or a non-security product that heavily relies on cryptography. This report categorizes and enumerates a subset of findings that document participant comments specific to NIST cryptographic publications and testing/validation programs, with a goal of informing future decisions of NIST and other standards bodies working in this space. cryptography; development; standards; testing; validation\n\nCryptography is an essential component of modern computing. Unfortunately, implementing cryptography correctly is a non-trivial undertaking. Past research studies have supported this observation by revealing a multitude of errors and developer pitfalls in the cryptographic implementations of software products [1-5]. However, these studies focused on the practices of less-experienced, individual developers."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 2)"}, {"role": "assistant", "content": "Laboratory Visualization and Usability Group conducted a qualitative investigation into the processes and resources that organizations employ in the development and testing of cryptographic products.\nThe study involved 21 in-depth interviews of 29 participants representing organizations that develop either a security product that uses cryptography or a non-security product that heavily relies on cryptography. This report categorizes and enumerates a subset of findings that document participant comments specific to NIST cryptographic publications and testing/validation programs, with a goal of informing future decisions of NIST and other standards bodies working in this space. ## Key words\n\ncryptography; development; standards; testing; validation\n\n## Table of Contents\n\n| | Introduction ..................................................................................................................... | Introduction ..................................................................................................................... |\n|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Background: NIST Cryptographic Standards and Testing/Validation Programs ..."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST 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.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 8)"}, {"role": "assistant", "content": "ht that security was a priority for the organization, that security was understood by leadership and employees as important, and that leadership and employees supported the security awareness program.\nHowever, only 35% of survey participants thought the program had been provided adequate funding and staff. Study results can inform federal security awareness professionals, organizational decision makers, policy makers, and guidance developers in their efforts to improve and advocate for federal security awareness programs. The results may also be valuable to security awareness professionals outside of the government who face similar challenges. Additionally, although this study refers to security awareness programs, its focus is not only relevant to awareness but also to security training issues as well. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| EXECUTIVE SUMMARY......................................................................................................... iii | EXECUTIVE SUMMARY......................................................................................................... iii | EXECUTIVE SUMMARY........................................................................................................."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\ne not met by IoT product components and why (e.g., the capability is not needed based on risk assessment). - d. Product design and support considerations related to the IoT product, for example :\n- i.\nAll hardware and software components, from all sources (e.g., open source, propriety third-party, internally developed) used to"}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n| EXECUTIVE SUMMARY........................................................................................................III | EXECUTIVE SUMMARY........................................................................................................III | EXECUTIVE SUMMARY........................................................................................................III |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 INTRODUCTION................................................................................................................. 1 | 1 INTRODUCTION................................................................................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 10)"}, {"role": "assistant", "content": "onally, materials should meet accessibility 1 standards and guidance (e.g., Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act of 1973) to support users with disabilities.\nSince many users may not fully understand cybersecurity risks to their IoT products, education materials should clearly communicate the relevance of product cybersecurity features (what the features do and why these are of importance) and what actions are expected of the users (e.g., changing settings or physically safeguarding the product). Instructions for setting cybersecurity preferences should be clear, simple, and achievable for those without cybersecurity expertise. To support diverse users with different cybersecurity and technical needs, skills, and interests, a layered approach for education materials may also be helpful; first present basic information, then provide links to more detail for those who need or want it. 1\n\nIn this report the term 'accessibility' is used in the context of limiting or removing barriers for individuals with disabilities to use technology, access information and services, and participate in society generally. ## 3. Report from the Design-A-Thon\n\nA 'Design-A-Thon' is an interactive event where individuals or teams are given a design task to work on within a given timeframe (generally several consecutive hours). It is closely related to the concept and approach of a Hack-A-Thon but isn't as focused on technical solutions or coding. As such, Design-A-Thons can be a useful tool to bring inter-disciplinary thinking with the aim of novel solutions to problems. NIST researchers planned the Design-A-Thon to target cybersecurity education and awareness for digital products."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nTemoshok D, Fenton JL, Choong YY, Lefkovitz N, Regenscheid A, Galluzzo R, Richer JP\n(2025) Digital Identity Guidelines: Authentication and Authenticator Management.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special\nPublication (SP) NIST SP 800-63B-4. https://doi.org/10.6028/NIST.SP.800-63B-4"}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nof assets and software. A realistic goal is to maintain a close-to-comprehensive inventory by relying on automation to constantly discover new assets and collect up-to-date information on all assets.\nSome vendors might also provide machineconsumable data on their assets' software composition, such as a software bill of materials (SBOM), which could be used to augment organization inventories."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.5.3. 3.5.3."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ordered t-way Combinations for Testing State-based Systems provide? (Part 3)"}, {"role": "assistant", "content": "same input. That is, the response of the process to a particular set of input values may depend on its current state, such as whether a communication protocol is in a listen or connection-open state.\nThe current state depends on the order of input values that were contained in previously received packets. The same sort of statedependent behavior occurs in many other types of systems as well. Ensuring that inputs and system states in testing are sufficiently representative of what will be encountered in practice is critical to any form of effective software testing. The common practice for evaluating how thoroughly software has been tested is by using some sort of structural coverage metrics, such as statement coverage, branch coverage, or MC/DC coverage [13] . Test cases selected using only structural coverage criteria are often not very effective as they are not designed to include corner cases with specific combinations of input values that may cause a failure. Looking beyond these commonly used metrics, it is often difficult to determine if the code has been adequately tested and even more difficult to ensure that a sufficient diversity of inputs has been achieved. This is particularly true of assertion-based testing or runtime verification, where program states and properties are monitored to verify correct processing. For runtime assertions to discover bugs, the software needs to be exercised with a set of values in a particular order that leads to the failure. Consequently, for strong software assurance, measures are needed to verify that combinations of input values and combinations of input orders in a test suite are sufficient. Combinatorial coverage measures provide an effective method for quantifying the thoroughness of test input values [26] . A number of measures have been defined for the coverage of (static) input value combinations."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n☐ Include C-SCRM responsibilities and performance requirements in personnel descriptions to ensure clarity and improve accountability.\n\n☐ Document performance goals for personnel with C-SCRM responsibilities, and periodically measure them to demonstrate and improve performance.\n\n☐ vet their employees and guard against insider threats"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nlity to deploy load balancing, Layer 7 application firewalls, SSO (for Active Directory [AD] ) , Azure AD, Lightweight Directory Access Protocol (LDAP), and enterprise -level virtual private networks.\nF5's BIG -IP is available as a hardware product and a virtual machine (BIG -IP Virtual Edition) that is cloud-agnostic and can be deployed on-premises in a public and/or hybrid cloud environment."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does IoT Non-Technical Supporting Capability Core Baseline support CMMC certification?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nNon-technical supporting capabilities are actions a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\nC-SCRM practitioners identify, assess, and mitigate cybersecurity risks throughout the supply chain at all levels of their organizations associated with information and communications technology (ICT) products and services. Potential risks include malicious functionality, counterfeit devices, or vulnerabilities derived from poor manufacturing and development practices within the supply chain.\n\n- Risk Assessment: The authenticity and integrity of hardware and software are assessed prior to acquisition and use [ID.RA-09]; Critical suppliers are assessed prior to acquisition [ID.RA-10]\n- Improvement: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties [ID.IM-02]"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 6)"}, {"role": "assistant", "content": ".................14 |\n\n## 1 Introduction\n\nInternet of Things (IoT) devices often lack built-in device cybersecurity capabilities, as well as non-technical support relevant to cybersecurity.\nCustomers can use this type of information to help mitigate cybersecurity risks related to the IoT devices and their use. The wide range of connectivity possible for IoT devices, and the ability for these devices to interact with the physical world, means securing these devices often becomes a priority; but it is a challenge for customers when they are not adequately supported. This publication should be used and understood within the context of NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers [1] and NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline [2]. NISTIR 8259 discusses considerations for manufacturers to help guide them in choosing and implementing the device cybersecurity capabilities their IoT devices will provide. 8259A discusses device technical cybersecurity capabilities, which are cybersecurity features or functions that devices provide through their own technical means (i.e., device hardware and software), and establishes a core baseline of device cybersecurity capabilities IoT device customers commonly need. To complement the core baseline from NISTIR 8259A, the IoT non-technical supporting capability core baseline is a set of actions performed by manufacturers and/or designated supporting third parties (called supporting parties ). These actions will help others (e.g., customers, end-users) use the cybersecurity capabilities of IoT devices, and support the on-going cybersecurity of the IoT device and the system and networks the device connects to (the digital ecosystem)."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "..........30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5.\nC-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |\n\n| 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls..............................................................................................."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\nTHE NATIONAL MEASUREMENT LABORATORY provides the national system of physical and chemical and materials measurement; coordinates the system with measurement systems of other nations and furnishes essential services leading to accurate and uniform physical and chemical measurement throughout the Nation's scientific community, industry, and commerce; conducts materials research leading to improved methods of measurement, standards, and data on the properties of materials needed by industry, commerce, educational institutions, and Government; provides advisory and research services to other Government agencies; develops, produces, and distributes Standard Reference Materials; and provides calibration services. The Laboratory consists of the following centers:\n\n| 3. | POLICY | AND CONTROL STANDARDS | 3-6 |\n|------|----------------|-------------------------------------------------------------------------------------------------------|-----------|\n| | 3.1 | General | 3-6 |\n| | 3.2 | Assessing Security Safeguards | 3-6 |\n| | 3.3 | Establishing Control Standards | 3-6 |\n| | 3.4 | Require a Plan to Implement Controls | 3-7 |\n| | 3.5 | Establish Personnel Security Policies | 3-7 |\n| 4."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.5 (NIST 3.4.5)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.4.5 | Cost Considerations ... 3.4.5 Cost Considerations\n\nThe ISCP Coordinator should ensure that the strategy chosen can be implemented effectively with available personnel and financial resources."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.4.5", "cmmc_practice_id": "CM.L2-3.4.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n## Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines\n\n## Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines\n\nChandramouli R, Kautz F, Torres-Arias S (2024) Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-204D. https://doi.org/10.6028/NIST.SP.800-204D"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.9 (NIST 3.2.9)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.9. 3.2.9. 3.2.9, NIST may adjust the restricted status of out-of-band\nauthentication using the PSTN based on the evolution of the threat\nlandscape and the technical operation of the PSTN."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.9", "cmmc_practice_id": "AT.L2-3.2.9", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body ...................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n| 1. Introduction.............................................................................................................. 1 | 1. Introduction.............................................................................................................. 1 | 1. Introduction.............................................................................................................. 1 | 1. Introduction.............................................................................................................. 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 2. Scope and Purpose ................................................................................................. | 2. Scope and Purpose ................................................................................................. | 2. Scope and Purpose ................................................................................................. | 1 |\n| 3. Definitions, Symbols and Abbreviations ............................................................... | 3. Definitions, Symbols and Abbreviations ............................................................... | 3. Definitions, Symbols and Abbreviations ..............................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.2.3 eyeSight\n\nForescout eyeSight is an appliance hosted on a 1U Dell R640 that is installed within a standard datacenter rack and connected to the network as described in the previous section."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide? (Part 6)"}, {"role": "assistant", "content": "Baseline (NIST IR 8259A) and nontechnical, IoT Non-Technical Supporting Capability Core Baseline (NIST IR 8259B) concepts to help manufacturers and customers consider the cybersecurity of IoT devices.\nThe NIST IR 8259 series has been used to inform and develop subsequent publications that elaborate on IoT cybersecurity across sectors and use cases (e.g., federal agency uses cases reflected in IoT Device Cybersecurity Guidance for the Federal Government: Establishing IoT Device Cybersecurity Requirements (NIST SP 800-213) and consumer use cases reflected in Profile of the IoT Core Baseline for Consumer IoT Products (NIST IR 8425) and the U.S. Cyber Trust Mark). NIST IR 8259 serves as a foundational document for these publications -providing these a conceptual and contextual basis. But in the extension of the documents over time, these subsequent publications introduced new concepts which would benefit the broader community in the foundational NIST IR 8259 series. ## About the Workshop\n\nThe purpose of this workshop was to consider how to better align NIST IR 8259 with concepts introduced in later publications. For example, NIST IR 8425 explicitly discusses IoT products and the relationship among product components. NIST IR 8259 needs to align with these concepts. Additionally, some topics have consistently come up in discussions with the community that NIST considers as potential areas to add to a revision of NIST IR 8259, including:\n\n- Broaden the discussions from a focus on the IoT system device component to considerations of entire IoT products (and connected products) to better reflect the wide variety of applications and use cases that exist. - Develop the relationship between risk assessment and threat modeling activities. - Address the different cybersecurity considerations among Information Technology (IT), Internet of Things (IoT), Operational Technology (OT), and Industrial Internet of Things (IIoT)\n- Identify insights, considerations, approaches, etc."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 3)"}, {"role": "assistant", "content": "h to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Email: SP800-56a\\_comments@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThis Recommendation specifies key-establishment schemes based on the discrete logarithm problem over finite fields and elliptic curves, including several variations of Diffie-Hellman and Menezes-Qu-Vanstone (MQV) key establishment schemes."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8.\nContingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 7)"}, {"role": "assistant", "content": "t claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1.\nIntroduction...................................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Using the SSDF Community Profile..................................................................................................4 |\n| 3. SSDF Community Profile for AI Model Development .......................................................................6 |\n| References.......................................................................................................................................20 |\n| Appendix A. Glossary .......................................................................................................................22 |\n| List of Tables |\n| Table 1. SSDF Community Profile for AI Model Development ..............................................................8 |\n\n## 1. Introduction\n\nSection 4.1.a of Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and Use of Artificial Intelligence [1], tasked NIST with 'developing a companion resource to the Secure Software Development Framework to incorporate secure development practices for generative AI and for dual-use foundation models.' This document is that companion resource. The software development and use of AI models and AI systems inherit much of the same risk as any other digital system."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.3 (NIST 3.7.3)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.7.3 Other Considerations\n\nThe use of the event detection capability to detect largely assumes that the update has been reported as vulnerable, either through a well-known history of being vulnerable or through intelligence-sharing channels."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.7.3", "cmmc_practice_id": "MA.L2-3.7.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 5)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\nThis document is intended to aid agencies in their MFA implementations; it does not guarantee that their implementation will meet CJIS Security Policy requirements or will pass a CJIS audit. All questions about how a specific MFA implementation can meet the CJIS Security Policy should be directed to the CJIS Information Security Officer (ISO) team at iso@fbi.gov.\n\n## 3.3. Phased MFA Deployment\n\nstate message switch, as described in Sec. 3.1.3. Instead, identity information (which might be needed downstream for auditing and logging) could be passed to the message switch using identity federation protocols such as SAML or OpenID Connect."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Contingency Planning Guide for Federal Information Systems provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-34 Rev. 1\n\n## Contingency Planning Guide for Federal Information Systems\n\nMarianne Swanson Pauline Bowen Amy Wohl Phillips Dean Gallup David Lynes\n\n\n\n## NIST Special Publication 800-34 Rev. 1\n\n## Contingency Planning Guide for Federal Information Systems\n\nMarianne Swanson Pauline Bowen Amy Wohl Phillips Dean Gallup David Lynes\n\nMay 2010\n\n\n\nU.S. Department of Commerce Gary Locke, Secretary\n\nNational Institute of Standards and Technology Patrick D. Gallagher, Director\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There are references in this publication to documents currently under development by NIST in accordance with responsibilities assigned to NIST under the Federal Information Security Management Act of 2002. The methodologies in this document may be used even before the completion of such companion documents. Thus, until such time as each document is completed, current requirements, guidelines, and procedures (where they exist) remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new documents by NIST. Individuals are also encouraged to review the public draft documents and offer their comments to NIST. All NIST documents mentioned in this publication, other than the ones noted above, are available at http://csrc.nist.gov/publications. National Institute of Standards and Technology Special Publication 800-34 Natl. Inst. Stand. Technol. Spec. Publ."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nCybersecurity education and awareness can provide critical support for the cybersecurity of digital products. Notably, the capability can inform and educate users about other cybersecurity capabilities, particularly technical capabilities. For example, cybersecurity education and awareness can guide users on creating strong access control credentials and permissions for products where such features are supported. Other information can be delivered using this capability as well, such as expectations for use of the product and other cybersecurity expectations, which can reduce the possibility of a risk being missed or otherwise unaddressed when the product is deployed."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nSome of the threats to wireless IMDs include device reprogramming, data extraction, data tampering, repeated access attempts and data flooding. Vulnerabilities include unsecured communication channels, inadequate authentication and access control, weak audit mechanisms and meager storage. The resulting risks include patient safety compromise resulting from firmware malfunction or therapy misconfiguration, device unavailability due to battery power depletion, patient privacy loss due to data leakage to unauthorized parties, and inappropriate medical follow-up due to tampering of patient readings. While some cyber threats may be unintentional, various motivations exist for deliberate cyber attacks, such as patient information gathering, negative impact to patient health status, ego satisfaction of the attacker, as well as gaining competitive advantage over another vendor through negative press. ## C. Authentication and Access Control Mechanisms\n\nFor each type of data identified, the authentication and access control mechanisms applicable for extracting or updating the data type need to be reviewed to determine adequacy of the protection mechanisms while balancing the needs of patient safety in emergency situations and the utility of the IMD within a patient's environment. This is a non-trivial exercise since the security and privacy requirements for IMDs frequently conflict with the requirements stemming from emergency access to patient data and device utility in hospital and home settings. Creative approaches may be devised to decouple data essential for patient safety in emergency conditions from patient personally identifiable information/data to allow different authentication and access control mechanisms to apply to each group of data."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Security and Privacy Controls for Information Systems and Organizations provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-53\nRevision 5\n\nSecurity and Privacy Controls for\nInformation Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53r5\n\n\fNIST Special Publication 800-53\nRevision 5\n\n Security and Privacy Controls for\n\nInformation Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53r5\n\nSeptember 2020\nINCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XVII\n\nNational Institute of Standards and Technology\n Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nU.S. Department of Commerce\nWilbur L. Ross, Jr., Secretary\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nAuthority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the\nFederal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq., Public Law\n(P.L.) 113-283. NIST is responsible for developing information security standards and guidelines,\nincluding minimum requirements for federal information systems. Such information security\nstandards and guidelines shall not apply to national security systems without the express\napproval of the appropriate federal officials exercising policy authority over such systems. This\nguideline is consistent with the requirements of the Office of Management and Budget (OMB)\nCircular A-130."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.4.3. 3.4.3), or both. 3.4.3."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 4)"}, {"role": "assistant", "content": "grams face a number of challenges, including lack of resources, difficulty measuring the impact of the program, and perceptions among the workforce that training is a boring, 'check-the-box' activity.\nHowever, it is unclear if these challenges also apply to security awareness programs in the United States (U.S.) government. To better understand the needs, challenges, practices, and necessary competencies of federal security awareness teams and programs, we conducted a 'mixed methods' research study that leveraged both qualitative and quantitative methodologies. We first conducted eight focus groups of federal employees who had security awareness duties or were managers or executives who oversaw the programs within their organizations. The focus groups then informed an online survey completed by 96 federal employees with security awareness responsibilities. The research background and methodologies for these two phases are described in detail in NISTIR 8420 'Federal Cybersecurity Awareness Programs: A Mixed Methods Research Study.' This companion document reports on a subset of results focused on the approaches and challenges of federal security awareness programs. The following is a high-level overview of these results, with cited statistics from the survey. ## Required Annual Security Awareness Training\n\n- Two-thirds of survey participants said they develop at least some required security awareness training content in-house, with 80% updating content at least once a year. Focus group participants expressed frustration that each organization had to acquire or create their own training. Instead, they desired standardized government training and guidance that allow customization for the unique needs of each organization. - Automation was viewed as essential for efficient tracking of employees' completion of training."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.1.4. 3.1.4. 3.1.4)\n- When an agency is choosing its approach to MFA implementation, it should do the following (from Sec."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 6)"}, {"role": "assistant", "content": "ents in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract.\n|\n|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| How do I know if I have CUI? | It is the responsibility of the federal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'? | The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nCollaborators participating in this project submitted their capabilities in response to an open call in the Federal Register for all sources of relevant security capabilities from academia and industry (vendors and integrators). Those respondents with relevant capabilities or product components signed a Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to build this example solution. The National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity issues. This public-private partnership enables the creation of practical cybersecurity solutions for specific industries, as well as for broad, cross-sector technology challenges. Through consortia under Cooperative Research and Development Agreements (CRADAs), including technology partners-from Fortune 50 market leaders to smaller companies specializing in information technology security-the NCCoE applies standards and best practices to develop modular, easily adaptable example cybersecurity solutions using commercially available technology. The NCCoE documents these example solutions in the NIST Special Publication 1800 series, which maps capabilities to the NIST Cybersecurity Framework (CSF) and details the steps needed for another entity to re-create the example solution. The NCCoE was established in 2012 by NIST in partnership with the State of Maryland and Montgomery County, Maryland. The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.1.2 Policies and Procedures in Functional Areas | 4-10 |\n| | | Particular 3. 3.1.2 3. 3.1.2 System Extensibility | 3."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Maintenance?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nCybersecurity utility: The ability to identify IoT products and their components is necessary to support such activities as asset management for updates, data protection, and digital forensics capabilities for incident response. 1. Each IoT product component can receive, verify, and apply verified software updates. 2. The IoT product implements measures to keep software on IoT product components up to date (i.e., automatic application of updates or consistent customer notification of available updates via the IoT product). 1. Throughout the development lifecycle, the IoT product developer creates or gathers and stores information relevant to the cybersecurity of the IoT product and its product components, including :\n- a. Assumptions made during the development process and other expectations related to the IoT product, including :\n- i. Expected customers and use cases. - ii. Physical use and characteristics, including security of the location of the IoT product and its product components (e.g., a camera for use inside the home that has an off switch on the device vs. a security camera for use outside the home that does not have an off switch on the device). - iii. Network access and requirements (e.g., bandwidth requirements). - iv. Data created and handled by the IoT product. - v. Any expected data inputs and outputs (including error codes, frequency, type/form, range of acceptable values, etc.). - vi. The IoT product developer's assumed cybersecurity requirements for the IoT product. - vii. Any laws and regulations with which the IoT product and related support activities comply. - viii. Expected lifespan and anticipated cybersecurity costs related to the IoT product (e.g., price of maintenance) and length and terms of support. - b. All IoT components, including but not limited to the IoT device, that are part of the IoT product. - c."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nification of compensating controls; and (iii) the specification of agency-defined parameters in the security controls, where allowed. The system security plan should document all tailoring activities.\n- -Security controls that uniquely support the confidentiality, integrity, or availability security objectives can be downgraded to the corresponding control in a lower baseline (or appropriately modified or eliminated if not defined in a lower baseline) if, and only if, the downgrading action: (i) is consistent with the FIPS 199 security categorization for the corresponding security objectives of confidentiality, integrity, or availability before moving to the high watermark; 14 (ii) is supported by an agency's assessment of risk; and (iii) does not affect the security-relevant information within the information system. 15"}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Zero Trust Architecture provide?"}, {"role": "assistant", "content": "## NIST Publicación especial 800-207\n\n## Arquitectura de confianza cero\n\nScott Rose Oliver Borchert Stu Mitchell Sean Connelly\n\nEsta publicación se encuentra disponible en inglés de forma gratuita en https://doi.org/10.6028/NIST.SP.800-207\n\n## S E G U R I D A D I N F O R M Á T I C A\n\n## NIST\n\nNational Institute of Standards and Technologies U. S. Department of Commerce\n\n## NIST Publicación especial 800-207\n\n## Arquitectura de confianza cero\n\nScott Rose Oliver Borchert\n\nDivisión de Tecnologías Avanzadas de Red Laboratorio de Tecnologías de la Información\n\nStu Mitchell Stu2Labs Stafford, VA\n\nSean Connelly\n\nAgencia de Ciberseguridad y Seguridad de las Infraestructuras Departamento de Seguridad Nacional\n\nEsta publicación se encuentra disponible en inglés de forma gratuita en: https://doi.org/10.6028/NIST.SP.800-207\n\nTraducción al español Dreamlab Technologies Chile Yanina Ángela Bettati (2023)\n\nTraducido con permiso por cortesía del Instituto Nacional de Estándares y Tecnología (NIST). No es una traducción oficial del Gobierno de los Estados Unidos. Todos los derechos reservados. Secretaría de Comercio de EE. UU. Departamento de Comercio de EE. UU. Wilbur L. Ross, Jr., Secretario\n\nInstituto Nacional de Normas y Tecnología Walter Copan, Director del NIST y Subsecretario de Comercio para Normas y Tecnología\n\n## Autoridad\n\nEsta publicación ha sido desarrollada por NIST de conformidad con sus responsabilidades estatutarias en virtud de la Ley Federal de Modernización de la Seguridad de la Información (FISMA) de 2014, 44 U.S.C. § 3551 y siguientes, Ley Pública (P.L.) 113-283. NIST es responsable de desarrollar normas y directrices de seguridad de la información, incluidos los requisitos mínimos para los sistemas de información federales, pero dichas normas y directrices no se aplicarán a los sistemas de seguridad nacional sin la aprobación expresa de los funcionarios federales apropiados que ejercen la autoridad política sobre dichos sistemas."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nource code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications.\n| CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nMost United States federal government organizations are required to conduct cybersecurity role-based training for federal government personnel and supporting contractors who are assigned roles having security and privacy responsibilities. Despite the training mandate, there has been little prior effort to look broadly across federal organizations to see how they are implementing these training activities and what issues they are experiencing. This lack of understanding may be hindering the development of improvements and resources for training activities. To address this gap, the Usable Cybersecurity team at the National Institute of Standards and Technology conducted a research study consisting of focus groups and a survey to gain insights into the approaches of and challenges faced by federal organizations when implementing role-based training activities. This paper reports the results of the study and suggests actions that organizations can take to improve federal role-based training activities. Despite the training mandate, there has been little prior effort to look broadly across federal organizations to see how they are implementing RBT activities and what issues they are experiencing. This lack of understanding may be hindering the development of improvements and resources for federal RBT activities. To address this gap, we - the Usable Cybersecurity team at the National Institute of Standards and Technology (NIST) conducted a research study to gain insights into the approaches of and challenges faced by organizations when implementing RBT activities. We conducted a prior study that explored federal security awareness programs through focus groups and a survey [IR8420][IR8420A] [IR8420B]. In the focus groups, we found that security awareness professionals were often also assigned responsibilities for role-based training activities, for which they identified significant challenges."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n## NISTIR 8259B\n\n## IoT Non-Technical Supporting Capability Core Baseline\n\nMichael Fagan Jeffrey Marron Kevin G. Brady, Jr. Barbara B. Cuthill Katerina N. Megas Rebecca Herold\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8259B\n\n\n\n## NISTIR 8259B\n\n## Internet of Things Non-Technical Supporting Capability Core Baseline\n\nMichael Fagan Jeffrey Marron Kevin G. Brady, Jr. Barbara B. Cuthill Katerina N. Megas\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nRebecca Herold\n\nThe Privacy Professor\n\nDes Moines, IA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259B\n\nAugust 2021\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259B 21 pages (August 2021)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259B\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n3.3.1 C(0e, 2s) Scheme with Unilateral Key Confirmation Provided by Party |\n| | 6. 3.3.1 C(0e, 2s) Scheme with Unilateral Key Confirmation Provided by Party U to Party V\n\nFigure\\_15 depicts a typical flow for a C(0e, 2s) scheme with unilateral key confirmation from party U to party V. 3.3.1."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n| 5.6.1.2.2 Key Pair Generation by Testing Candidates........................\n| 31 |\n| 5.6.2 Required Assurances.......................................................................................... | 5.6.2 Required Assurances.......................................................................................... | 32 |\n| 5.6.2.1 | Assurances Required by the Key Pair Owner..................................... | 33 |\n| | 5.6.2.1.1 Owner Assurance of Correct Generation............................. | 35 |\n| | 5.6.2.1.2 Owner Assurance of Private-Key Validity .......................... | 35 |\n| | 5.6.2.1.3 Owner Assurance of Public-Key Validity ........................... | 36 |\n| | 5.6.2.1.4 Owner Assurance of Pair-wise Consistency........................ | 36 |\n| | 5.6.2.1.5 Owner Assurance of Possession of the Private Key............ | 37 |\n| 5.6.2.2 | Assurances Required by a Public Key Recipient................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice PL.L2-3.15.1 (NIST 3.15.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.15.1. 3.15.1. 3.15.1."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.15.1", "cmmc_practice_id": "PL.L2-3.15.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide?"}, {"role": "assistant", "content": "## NIST Cybersecurity White Paper NIST CSWP 46\n\n## Analyzing Collusion Threats in the Semiconductor Supply Chain\n\nSanjay (Jay) Rekhi Kostas Amberiadis Computer Security Information Technology Laboratory\n\nAbir Ahsan Akib Ankur Srivastava Electrical and Computer Engineering University of Maryland, College Park\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.CSWP.46\n\nJune 30, 2025\n\n\n\n\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements\n\nNIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-01-30\n\n## How to Cite this NIST Technical Series Publication:\n\nRekhi S, Amberiadis K, Akib AA, Srivastava A (2025) Analyzing Collusion Threats in the Semiconductor Supply Chain. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 46. https://doi.org/10.6028/NIST.CSWP.46\n\n## Author ORCID iDs\n\nSanjay (Jay) Rekhi: 0009-0008-8711-4030\n\nKostas Amberiadis: 0009-0000-7771-5002\n\nAbir Ahsan Akib: 0000-0002-1455-6662\n\nAnkur Srivastava: 0000-0002-5445-904X\n\n## Contact Information\n\nhwsec@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/publications/cswp, including related content, potential updates, and document history."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.1. CROSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.1. CROSS"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n1 While agencies are required to follow NIST guidance in accordance with OMB policy, there is flexibility within NIST's guidance in how agencies apply the guidance. Unless otherwise specified by OMB, the 800-series guidance documents published by NIST generally allow agencies some latitude in the application. Consequently, the application of NIST guidance by agencies can result in different security solutions that are equally acceptable, compliant with the guidance, and meet the OMB definition of adequate security for federal information systems. When assessing federal agency compliance with NIST guidance, auditors, evaluators, and assessors should consider the intent of the security concepts and principles articulated within the particular guidance document and how the agency applied the guidance in the context of its specific mission responsibilities, operational environments, and unique organizational conditions.\n\nProvide system functionality testing and/or validation procedures to ensure that the system is operating correctly. This section may be combined with the Data Testing section if procedures test both the functionality and data validity. Teams or persons responsible for each procedure should be identified. An example of a functional test for a low-impact system may be logging into the system and running a report or performing a transaction to see if the system is operating correctly. Detailed functionality test procedures may be provided in Appendix E, System Validation Test Plan.\n\n- ƒ Keystroke-level recovery steps;\n- ƒ System installation instructions from tape, CD, or other media;\n- ƒ Required configuration settings or changes;\n- ƒ Recovery of data from tape and audit logs; and\n- ƒ Other system recovery procedures, as appropriate."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nFew software development life cycle (SDLC) models explicitly address software security in detail, so secure software development practices usually need to be added to each SDLC model to ensure that the software being developed is well-secured. This document recommends the Secure Software Development Framework (SSDF) - a core set of high-level secure software development practices that can be integrated into each SDLC implementation. Following such practices should help software producers reduce the number of vulnerabilities in released software, reduce the potential impact of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of vulnerabilities to prevent future recurrences. Because the framework provides a common vocabulary for secure software development, software acquirers can also use it to foster communications with suppliers in acquisition processes and other management activities. This document provides a common language to describe fundamental secure software development practices. This is similar to the approach taken by the Framework for Improving Critical Infrastructure Cybersecurity , also known as the NIST Cybersecurity Framework [NISTCSF]. 2 Expertise in secure software development is not required to understand the practices."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide? (Part 3)"}, {"role": "assistant", "content": "Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-07-09\n\n## How to cite this NIST Technical Series Publication:\n\nMeltem Sönmez Turan, Kerry A.\nMcKay, Donghoon Chang, Jinkeon Kang, John Kelsey (2025) Ascon-Based Lightweight Cryptography Standards for Constrained Devices. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-232. https://doi.org/10.6028/NIST.SP.800-232\n\n## Author ORCID iDs\n\nMeltem Sönmez Turan: 0000-0002-1950-7130 Kerry A. McKay: 0000-0002-5956-587X Donghoon Chang: 0000-0003-1249-2869 Jinkeon Kang: 0000-0003-2142-8236 John Kelsey: 0000-0002-3427-1744\n\n## Contact Information\n\nSP800-232-comments@list.nist.gov\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/232/final, including related content, potential updates, and document history. ## All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nIn 2023, the National Institute of Standards and Technology (NIST) announced the selection of the Ascon family of algorithms designed by Dobraunig, Eichlseder, Mendel, and Schläffer to provide efficient cryptographic solutions for resource-constrained devices. This decision emerged from a rigorous, multi-round lightweight cryptography standardization process. The Ascon family includes a suite of cryptographic primitives that provide Authenticated Encryption with Associated Data (AEAD), hash function, and eXtendable Output Function (XOF) capabilities. The Ascon family is characterized by lightweight, permutation-based primitives and provides robust security, efficiency, and flexibility, making it ideal for resourceconstrained environments, such as Internet of Things (IoT) devices, embedded systems, and low-power sensors. The family is developed to offer a viable alternative when the Advanced Encryption Standard (AES) may not perform optimally."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 10)"}, {"role": "assistant", "content": "| ..................................................................................................................\n4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS........................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nand prove they meet the enterprise policy to be granted the session. This may include meeting requirements such as client software versions, patch level, geolocation, historical request patterns, etc.\nNote that it may not be possible to perform all checks at the time of each access request, some policy check may be performed on an independent schedule (e.g., daily software versioning checks). - IV. The enterprise collects as much information as possible about the current state of assets, network infrastructure and communications and uses it to improve its security posture. Zero trust adds a dynamic response factor that was typically lacking (or not possible) in previous perimeter-based architectures. This requires the enterprise to monitor all traffic to the extent feasible and restricted (or required) by policy, regulation or legal requirement. System logs and threat intelligence are used to refine or change policy in response to new information. For example, a new vulnerability in a software component in use in the enterprise is announced. A zero trust enterprise could move quickly to quarantine the affected resources until they can be patched or modified to mitigate the newly discovered vulnerability. Administrators will need to set up and maintain a comprehensive monitoring and patching program for the enterprise and should consider how automated tools could assist in responding to newly discovered threats."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nSecurity awareness programs aim to assist employees in recognizing and responding to security issues with a goal of achieving long-term behavior changes. Security awareness professionals are individuals who are tasked with managing and executing the security awareness programs within their organizations. Prior industry surveys and research studies have identified challenges security awareness professionals face. Many members of security awareness teams perform security awareness duties on a part-time basis without a job title that reflects their duties, and they may lack sufficient professional skills (e.g., communications, relationship-building) that were viewed as essential in security awareness roles. In addition, the lack of understanding that security awareness is a unique discipline may lead to ill-prepared awareness professionals. However, it is unclear if these challenges also apply to security awareness professionals in the United States (U.S.) government. other fields, including non-IT fields such as instructional design and education, communications, and human resources. We found that 40% of participants had only ever worked in a technical field (cybersecurity, IT, or software development). Cybersecurity awareness (hereafter shortened to 'security awareness') programs aim to help employees recognize and appropriately respond to security issues, with a goal of achieving longterm behavior change [WILSON]. Security awareness professionals are individuals who are tasked with managing and executing the security awareness programs within their organizations. Prior industry surveys and research studies have identified challenges security awareness professionals face. Many professionals perform security awareness duties on a part-time basis without a job title that reflects their duties, and they may lack sufficient professional skills (e.g., communications, relationship-building) that are viewed as essential in security awareness roles [SANS][WOELK]."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 8)"}, {"role": "assistant", "content": "| Triage and Prioritize Source Vulnerability | Report........................................................\n9 | |\n| Determine the | Reported Vulnerable System..............................................................10 | |\n| Identify the Reported Vulnerable | Software.................................................................10 | |\n| Verify and Remediate | Vulnerability............................................................................10 | |\n| Determine Whether to | Publish an Advisory................................................................11 | |\n| 2.7.1."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 6)"}, {"role": "assistant", "content": "Operational Audits of Automated Information Systems (AISs) | 4 | | | 1.1.5 | Relevant Laws and Regulations | Relevant Laws and Regulations | 4 | | | 1.1.5.1 | Requirements for Audit Involvement | Requirements for Audit Involvement | 4 | | | | 1.1.5.2 | Requirements for Internal Control | 5 | | 1.2 | RISKS GENERATED BY COMPUTER TECHNOLOGY | RISKS GENERATED BY COMPUTER TECHNOLOGY | RISKS GENERATED BY COMPUTER TECHNOLOGY | 6 | | | 1.2.1 Overview of Risks | 1.2.1 Overview of Risks | 1.2.1 Overview of Risks | 6 | | | 1.2.1.1 | | Definitions | 7 | | | | 1.2.1.2 | Vulnerability/Risk Related Requirements | 7 | | | 1.2.2 | Risks in a Computerized Environment | Risks in a Computerized Environment | 8 | | | | 1.2.2.1 | Additional Risks Present in a Computerized Environment | 8 | | | | 1.2.2.2 | Assessing Vulnerabilities Through the Audit Process | 9 | | 1.3 | CONTROL OBJECTIVES AND STANDARDS IN A COMPUTER ENVIRONMENT | CONTROL OBJECTIVES AND STANDARDS IN A COMPUTER ENVIRONMENT | CONTROL OBJECTIVES AND STANDARDS IN A COMPUTER ENVIRONMENT | 10 | | | 1.3.1 | Impact"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.2.4 Machine Utilization 3. 3.2.4 Machine Uti 1 ization ."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.1.1 | Configuration... 3.1.1 Configuration\n\n-  Remote Access: Cisco VPN\n- Configured to allow authorized VPN users to access to ConsoleWorks web interface."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 10)"}, {"role": "assistant", "content": "nold Johnson, Donald Jones, Stuart Katzke, Eustace King, Mark Morrison, Sherrill Nicely, Karen Quigg, George Rogers, Cheryl Roby, Gary Stoneburner, Marianne Swanson, Glenda Turner, and Peter Williams.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Executive Summary\n\nAs we push computers to 'the edge,' building a complex world of interconnected information systems and devices, security and privacy risks (including supply chain risks) continue to be a large part of the national conversation and topics of great importance. The significant increase in the complexity of the hardware, software, firmware, and systems within the public and private sectors (including the U.S. critical infrastructure) represents a significant increase in attack surface that can be exploited by adversaries. Moreover, adversaries are using the supply chain as an attack vector and effective means of penetrating our systems, compromising the integrity of system elements, and gaining access to critical assets. The Defense Science Board Report, Resilient Military Systems and the Advanced Cyber Threat [DSB 2013], provides a sobering assessment of the vulnerabilities in the United States Government, the U.S. critical infrastructure, and the systems supporting the mission-essential operations and assets in the public and private sectors. '…The Task Force notes that the cyber threat to U.S. critical infrastructure is outpacing efforts to reduce pervasive vulnerabilities, so that for the next decade at least the United States must lean significantly on deterrence to address the cyber threat posed by the most capable U.S. adversaries. It is clear that a more proactive and systematic approach to U.S."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 2)"}, {"role": "assistant", "content": "ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 6)"}, {"role": "assistant", "content": "chnology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## HOW TO USE THIS PUBLICATION\n\nThis publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- Based on NIST SP 800-53, Revision 5 and the NIST SP 800-53B moderate impact control baseline.\n- Applies updated tailoring criteria addressing stakeholder feedback (adding new, consolidating, and withdrawing requirements).\n- Includes increased specificity in security requirements.\n- Introduces organization-defined parameters (ODP) to increase flexibility to better manage organizationspecific risks.\n\nControl Baseline: A set of controls you can implement to meet strategic, legal, regulatory, or contractual security and privacy requirements and manage risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The NIST Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, implementations, proofs of concept, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. The purpose of this publication is to describe procedures for assessing the enhanced security requirements in [SP 800-172]. 3 Compliance with the security requirements is addressed in CUI guidance and the CUI Federal Acquisition Regulation (FAR) or as supplemented by federal agencies (e.g., Department of Defense Federal Acquisition Regulation). Organizations can use the assessment procedures to generate evidence to support the assertion that the enhanced security requirements have been satisfied."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Software Supply Chain (SSC) -Definition and Model .....................................................................4 |\n| 2.4.1. Software Supply Chain Defects ....................................................................................................6 |\n| 2.4.2. Software Supply Chain Attacks.....................................................................................................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1. Developer Environment ...............................................................................................................8 |\n| 3.1.2. Threat Actors................................................................................................................................8 |\n| 3.1.3. Attack Vectors ..............................................................................................................................9 |\n| 3.1.4. Attack Targets (Assets).................................................................................................................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide?"}, {"role": "assistant", "content": "Ol\n\n\n\nA11105 7flT13T\n\nNes PUBLICATIONS\n\n## Computer Science and Technology\n\nNBS Special Publication 500-153\n\nGuide to Auditing for Controls and Security: A System Development Life Cycle Approach\n\n\n\nm T he National Bureau of Standards' was established by an act of Congress on 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 to assure international competitiveness and leadership of U.S. industry, science arid technology. NBS work involves development and transfer of measurements, standards and related science and technology, in support of continually improving U.S. productivity, product quality and reliability, innovation and underlying science and engineering. The Bureau's technical work is performed by the National Measurement Laboratory, the National Engineering Laboratory, the Institute for Computer Sciences and Technology, and the Institute for Materials Science and Engineering. ## The National Measurement Laboratory\n\nProvides the national system of physical and chemical measurement; coordinates the system with measurement systems of other nations and furnishes essential services leading to accurate and uniform physical and chemical measurement throughout the Nation's scientific community, industry, and commerce; provides advisory and research services to other Government agencies; conducts physical and chemical research; develops, produces, and distributes Standard Reference Materials; provides calibration services; and manages the National Standard Reference Data System."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nthe development of standards underpinning the nation's Smart Grid. In October 2011, Dr. Arnold added an additional role as Director of Cyber Physical Systems within NIST's Engineering Laboratory (EL).\nAnticipating and meeting the measurement science and standards needs for technology-intensive manufacturing construction, and cyber-physical systems in ways that enhance economic prosperity and improve the quality of life , EL promotes U.S. innovation and industrial competitiveness in areas of critical national priority."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n|\n| Federal Vulnerability Disclosure Coordination Body ....................................................\n| 6 | |\n| Preparation................................................................................................................. | 7 | |\n| 2.1.1. Create Source Vulnerability | Report Receipt Capability............................................. 7 | |\n| 2.1.2. Determine Scope and Obtain Contacts .................................................................... | 8 | |\n| 2.1.3. Develop Technical Analysis Capability ....................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 3-7 |\n| | 3.5 | Establish Personnel Security Policies | 3-7 |\n| 4.\n| ALLOCATE | RESOURCES | 3-7 |\n| | 4.1 | General | 3-7 3-8 |\n| 5. | REPORT | ON SECURITY | |\n| | 5.1 | General | 3-8 |\n| Fig. | 1 | Responsibilities and Duties to Provide Security for Data Processing System .. | 3-5 |\n| PART | | SESSION 2 ~ MANAGERIAL AND ORGANIZATIONAL VULNERABILITIES AND CONTROLS ~ LINE LEVEL - DATA PROCESSING | |\n| | IV: | | 4-1 |\n| | | | 4-2 |\n| 1. | EDITOR'S | NOTE INTRODUCTION 4-3 | 4-3 4-3 |\n| | 1.1 1.2 1.3 | The Charge Intent of Paper | 4-3 4-3 |\n| 2. | 1.4 | Elements of Discussion Comments | 4-4 |\n| | DATA | PROCESSING \"."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n3.3.3 | C(0e, 2s) Scheme with Bilateral Key Confirmation ... 3.3.3 C(0e, 2s) Scheme with Bilateral Key Confirmation\n\nFigure\\_17 depicts a typical flow for a C(0e, 2s) scheme with bilateral key confirmation."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n3.2.6 FINALIZE ASSESSMENT PLAN AND OBTAIN APPROVAL TO EXECUTE PLAN\n\nAfter selecting the assessment procedures (including developing necessary procedures not\ncontained in the SP 800-53A catalog of procedures), tailoring the procedures for\nsystem/platform-specific and organization-specific conditions, optimizing the procedures for\nefficiency, and addressing the potential for unexpected events that may impact the assessment,\nthe assessment plan is finalized and the schedule is established, including key milestones for the\nassessment process."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.6", "cmmc_practice_id": "AT.L2-3.2.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n'Since we have a lot of our personnel in remote areas, we've been doing it through our learning management system primarily for the annual security awareness training.' (D05)\n\n'For our main enterprise network, it's computer-based training that's taken annually…But for those who don't have access to the enterprise network often for certain other networks that we might maintain,…those are physical briefings done by the ISSOs [information system security officers] to those personnel. And then they sign an acknowledgment form.' (D03)\n\n'You've got IT security, physical security, personnel security, etc. And they have their own training requirements…It's inefficient.' (S11)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nvia mutual Transport Layer Security (mTLS) when a service makes an initial connection establishment as part of its inter-service call. This authentication is not performed again in subsequent calls.\nHowever, the security of this operation is ensured by not allowing the connections to be very long (usually as long as the time to live [TTL] of the service's identity certificate or as short as 15-30 minutes, depending on the configuration)."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.7 (NIST 3.1.7)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.1.7. 3.1.7): Proof of possession\n\nand control via an authentication protocol of a cryptographic key held by the\nsubscriber that requires activation by a second authentication factor\n\n2. 3.1.7)\n\nWhen a combination of two single-factor authenticators is used, the combination SHALL\ninclude one physical authenticator (i."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.1.7", "cmmc_practice_id": "AC.L2-3.1.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nerprise to follow guidelines, such as the Center for Internet Security's (CIS) benchmarks for public cloud services, thus improving the overall security profile of the enterprise for cloud access [4].\nNetwork security automation tools automate the life cycle processes involved in deployment, observability/monitoring, threat intelligence gathering/reporting (e.g., generating alerts of security violations for security personnel to take timely action), and - in some instances automatic remediation. These automated tools are an indispensable part of the current enterprise network landscape, especially those that consist of highly distributed on-premises and cloudbased IT resources."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide?"}, {"role": "assistant", "content": "\n\n## NIST Internal Report NIST IR 8532\n\n## Workshop on Enhancing Security of Devices and Components Across the Supply Chain\n\nSanjay (Jay) Rekhi D. Richard Kuhn Kim Schaffer Murugiah Souppaya A.J. Stein Noah Waller Nelson Hastings Michael Ogata\n\nWilliam C. Barker\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8532\n\n\n\n## NIST Internal Report NIST IR 8532\n\n## Workshop on Enhancing Security of Devices and Components Across the Supply Chain\n\nSanjay (Jay) Rekhi D. Richard Kuhn Kim Schaffer* Murugiah Souppaya A.J. Stein* Noah Waller\n\nComputer Security Division Information Technology Laboratory\n\nNelson Hastings Michael Ogata Applied Cybersecurity Division Information Technology Laboratory\n\nWilliam C. Barker Dakota Consulting\n\n*Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8532\n\nFebruary 2025\n\n\n\nU.S. Department of Commerce Jeremy Pelter, Acting Secretary of Commerce\n\nNational Institute of Standards and Technology Craig Burkhardt, Acting Under Secretary of Commerce for Standards and Technology and Acting NIST Director\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on YYYY-MM-DD [Will be added to final publication.]\n\n## How to Cite this NIST Technical Series Publication\n\nFisher W, Ajmo J, Umarji S, Dog S, Russell M, Scarfone K (2025) Multi-Factor Authentication for Criminal Justice Information Systems: Implementation Considerations for Protecting Criminal Justice Information. (National Institute of Standards and Technology, Gaithersburg, MD), NIST internal Report (IR) NIST IR 8523. https://doi.org/10.6028/NIST.IR.8523\n\n## Author ORCID iDs\n\nWilliam Fisher: 0009-0004-7569-5668\n\nJason Ajmo: 0009-0007-4046-6146\n\nSudhi Umarji: 0000-0001-6842-8167\n\nSpike Dog: 0009-0000-0201-6776\n\nMark Russell: 0009-0004-1273-392X\n\nKaren Scarfone: 0000-0001-6334-9486\n\n## Contact Information\n\npsfr-nccoe@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory\n\n100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8523/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA)."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 3)"}, {"role": "assistant", "content": "| help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n## Audience\n\n\n\n\n\nPages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality\n\n\n\nConfidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 \"Controlled Unclassified Information.\"\n\n## A Suite of Guidance\n\nNIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . \n\n\n\n\n\nNIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n\nIn the context of this document, the term 'vulnerability' refers to a security vulnerability in an information system. It does not refer to other kinds of vulnerabilities that may pertain to, for example, physical security, economic security, or foreign policy issues.\n\nThe terms 'should' and 'should not' indicate that - among several possibilities - one is recommended as particularly suitable without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. The terms 'may' and 'need not' indicate a course of action permissible within the limits of the publication. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical, or causal."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.4.1 | Assumptions and Caveats | Assumptions and Caveats | 50 |\n| | 3. 3.4.1 Review Documents | 81 |\n| | 4. 3.4.1 | SDLC Methodology Audit Considerations | 83 |\n| | 4."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nAudit and Evaluation\nof Computer Security ^\n\nThe auditing and evaluating of computer systems for adequate secu-\n\nrity has been a natural outgrowth of this widening interest in this\narea.\nthe financial and internal auditors and has been made a subject of spe-\ncial consideration by organizations such as the Institute of Internal\nAuditors, the American Institute of Certified Public Accountants, and\nthe EDP Auditors Associtation."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 4)"}, {"role": "assistant", "content": "at https://csrc.nist.gov/pubs/\nsp/800/63/B/4/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA).\nNIST SP 800-63B-4\nJuly 2025\n\nAbstract\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nThis guideline focuses on the authentication of subjects who interact with government\ninformation systems over networks to establish that a given claimant is a subscriber\nwho has been previously authenticated. The result of the authentication process may\nbe used locally by the system performing the authentication or asserted elsewhere in a\nfederated identity system. This document defines technical requirements for each of the\nthree authentication assurance levels. The guidelines are not intended to constrain the\ndevelopment or use of standards outside of this purpose. This publication supersedes\nNIST Special Publication (SP) 800-63B. Keywords\n\nauthentication; authentication assurance; credential service provider; digital\nauthentication; passwords. Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\n- Develops the system security plan in coordination with information owners, the system administrator, the information system security officer, the senior agency information security officer, and functional \"end users,\"\n- Maintains the system security plan and ensures that the system is deployed and operated according to the agreed-upon security requirements,\n- Ensures that system users and support personnel receive the requisite security training (e.g., instruction in rules of behavior),\n- Updates the system security plan whenever a significant change occurs, and\n- Assists in the identification, implementation, and assessment of the common security controls. - Carries out the CIO's responsibilities for system security planning,\n- Coordinates the development, review, and acceptance of system security plans with information system owners, information system security officers, and the authorizing official,\n- Coordinates the identification, implementation, and assessment of the common security controls, and\n- Possesses professional qualifications, including training and experience, required to develop and review system security plans. Many of the management and operational controls (e.g., contingency planning controls, incident response controls, security awareness and training controls, personnel security controls, and physical security controls) needed to protect an information system may be excellent candidates for common security control status. The objective is to reduce security costs by centrally managing the development, implementation, and assessment of the common security controls designated by the agency-and subsequently, sharing assessment results with the owners of information systems where those common security controls are applied. Security controls not designated as common controls are considered system-specific controls and are the responsibility of the information system owner."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Blockchain for Access Control Systems provide? (Part 3)"}, {"role": "assistant", "content": ". This document presents general information for blockchain access control systems from the views of blockchain system properties, components, functions, and supports for access control policy models.\nConsiderations for implementing blockchain access control systems are also included. ## Keywords\n\naccess control; blockchain; authorization; ABAC; policy. ## Acknowledgments\n\nThe author, Vincent C. Hu of the National Institute of Standards and Technology (NIST), wishes to thank Dylan Yaga, David Ferraiolo, Isabel Van Wyk, Jim Foti (NIST), and Antonios Gouglidis (Lancaster University, UK) who reviewed drafts of this document. The author also gratefully acknowledges and appreciates the comments and contributions made by government agencies, private organizations, and individuals in providing direction and assistance in the development of this document. ## Audience\n\nThis document assumes that readers are access control system experts who also have basic network and blockchain expertise. Because of the constantly changing nature of the information technology (IT) industry, readers are strongly encouraged to take advantage of other resources (including those referred in this document) for more current and detailed information. ## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. Following the ITL call for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, notice of one or more such claims has been received."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 9)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . 4.3. Identity Assurance Level 3 . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1. Proofing Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2.\nEvidence Collection . . . . . . . . . . . . . . . . . . . . . . . . 4.3.3. Attribute Requirements . . . . . . . . . . . . . . . . . . . . . . 4.3.4. Evidence Validation . . . . . . . . . . . . . . . . . . . . . . . . 4.3.5. Attribute Validation . . . . . . . . . . . . . . . . . . . . . . . . 4.3.6. Verification Requirements . . . . . . . . . . . . . . . . . . . . . 4.3.7. On-Site Attended Requirements — Colocated Agent\n\n. . . . . . . 4.3.8. On-Site Attended Requirements — Kiosk-Based . . . . . . . . . 4.3.9. Notification of Proofing . . . . . . . . . . . . . . . . . . . . . . 4.3.10. Initial Authenticator Binding . . . . . . . . . . . . . . . . . . . . 4.4. Summary of Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 5. Subscriber Accounts\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1. 5.2. 5.3. 5.4. Subscriber Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber Account Access . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber Account Maintenance and Updates . . . . . . . . . . . . . . Subscriber Account Suspension or Termination . . . . . . . . . . . . . . 44\n\n45\n\n45\n\n45\n\n45\n\n46\n\n46\n\n49\n\n49\n\n50\n\n51\n\n51\n\n51\n\n52\n\n52\n\n52\n\n52\n\n53\n\n53\n\n53\n\n54\n\n55\n\n55\n\n56\n\n56\n\n58\n\n58\n\n59\n\n59\n\n59\n\nv\n\n\fNIST SP 800-63A-4\nJuly 2025\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\n5.5. Data Breach Notification . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6. Multiple Subscriber Account Scenarios\n\n. . . . . . . . . . . . . . . . . . 6. Threats and Security Considerations . . . . . . . . . . . . . . . . . . . . . . . 6.1. 6.2. Threat Mitigation Strategies . . . . . . . . . . . . . . . . . . . . . . . . Collaboration With Adjacent Programs\n\n. . . . . . . . . . . . . . . . . . 7. Privacy Considerations . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nTHE INSTITUTE FOR MATERIALS RESEARCH conducts materials research leading to improved methods of measure-\nment, standards, and data on the properties of well-characterized materials needed by industry, commerce, educational insti-\ntutions, and Government: provides advisory and research services to other Government agencies; and develops, produces, and\ndistributes standard reference materials. The Institute consists of the Office of Standard Reference Materials, the Office of Air\nand Water Measurement, and the following divisions:\n\nThe National Bureau of Standards, with the support of the U.S. Gen-\neral Accounting Office, sponsored an invitational workshop on \"Audit and\nEvaluation of Computer Security,\" held in Miami Beach, Florida on March\n22-24, 1977.\narea and define appropriate subjects for future research.\nperts in the audit and computer communities were invited to discuss the\nsubject in one of ten sessions, each of which considered a different as-\npect.\nthese reports form the body of these Proceedings.\nThe ten topics re-\nported on are: Internal Audit Standards, Qualifications and Training,\nSecurity Administration, Audit Considerations in Various System Environ-\nments, Administrative and Physical Controls, Program Integrity, Data In-\ntegrity, Communications, Post-Processing Audit Tools and Techniques, and\nInteractive Audit Tools and Techniques.\n\nKEYWORDS:\ntraining, communications security, computer controls, computer\nsecurity, data integrity, interactive audit, internal audit, post-\nprocessing audit, program integrity."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n3.5.4 Maintenance Plans for Scenario 4, Unpatchable Assets... 3.5.4 Maintenance Plans for Scenario 4, Unpatchable Assets\n\nOrganizations should plan to implement multiple types of long-term risk mitigation methods besides patching to protect vulnerable assets."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "nist_control": "3.5.4", "cmmc_practice_id": "IA.L2-3.5.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Machine Learning for Access Control Policy Verification:\n\nrexample generation of found faults. It would be more efficient if the policy model error can be verified without composing security requirements to discover faults that already exist in the model. 2.\nVerification for policy with numerical attributes -Some context-aware access control policies, such as Policy Based Access Control (PBAC) [PBAC] or situation-awarded access control systems, have attributes as numerical variables. These non-binary attributes measure values such as numbers, volumes, and other measurable counts to make access decisions for policy rules, such as ' if the current security level is greater than 3, then the user has subject attribute X and is allowed to access resource with object attribute Y ,' or ' if the total amount of spending is higher than $50, then the discount is accessible to customers but not accessible to employees. ' These policies cannot be verified by traditional verification methods, including an infinite number of attribute values in test cases/oracle. The RFC verification method for these policies is especially useful because an RFC algorithm is fundamentally equipped for the evaluation of regression values. Its branch factors for subtree nodes test the limitations of attribute values, as shown in Figure 7, where the time and the temperature attribute values can vary to an unlimited real number depending on the resolutions of the variables."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.5.3 | Browser Separation... 3.5.3 Browser Separation\n\nMultiple brands of Web browsers (e."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nntific data formatting library with only seven dependencies, while Data Mining Classification and Regression Methods (rminer) [21] - an R-based data mining application - has 150 software dependencies.\nThe full software stack can be split into three general categories that differ based on the maintainer: user software, facility software, and vendor software."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\nlls to implement an effective and engaging program. However, no prior research has explored security awareness programs specifically in the United States (U.S.) government (federal) sector.\nTo address this gap, NIST conducted a two-phase, mixed methods research study to understand the needs, challenges, and practices of federal security awareness programs. This report describes the research background and methodology, along with the characteristics of the participants, organizations, and programs represented in the study. Research results can serve as a resource for federal security awareness professionals, managers, and organizational decision makers to improve and advocate for their organizations' security awareness programs. Results can also inform the development of federal security awareness guidance, policies, sharing forums, and initiatives meant to aid programs in becoming more effective. While focused on the U.S. government, findings may also have implications for organizational security awareness programs in other sectors."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 6)"}, {"role": "assistant", "content": "It identifies a set of issues to address from the previous versions of SCAP, presents a draft SCAP v2 architecture, and outlines an iterative development process for SCAP v2. This document is intended to drive consensus around a vision for SCAP v2, and to identify how the security automation community can collaborate in a public-private partnership to achieve this vision. Some work on the underlying specifications that support SCAP v2 has started; however, much of the work on defining SCAP v2 still needs to be accomplished. This document outlines an approach for SCAP v2 to support a broad range of cyber defense capabilities and requests community input to improve this approach. Knowing the state of your network is at the heart of all cyber defense capabilities-to know what endpoints are connected to it, if those endpoints are authorized to be on the network, what software is installed on each endpoint, and how that software is configured. In today's networks, endpoints encompass a wide range of connected devices including servers, workstations, network, mobile, and Internet of Things (IoT) devices. Understanding endpoint posture provides the information needed to automate management decisions that support proper network hygiene. Network hygiene practices, as identified by the NIST Framework for Improving Critical Infrastructure Cybersecurity Version 1.1 [1], are important foundational aspects of any enterprise strategy to identify, protect, detect, respond to, and recover from network attacks. SCAP is a suite of specifications for expressing, exchanging, and processing security automation content. SCAP content describes what endpoint posture information to collect and how to compare this information against a desired state using implementation-neutral, standardized formats. SCAP tools use these formats to drive the collection and evaluation of posture information to determine if software vulnerabilities and misconfigurations exist on a specific managed endpoint."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nThe term security will be used as a shorthand for 'cybersecurity' or 'information security.' Reference to physical security or personnel security is different and will be labeled as such."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| | | PO.3.3: Configure tools to generate artifacts of their support of secure software development practices as defined by the organization."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Control Baselines for Information Systems and Organizations provide?"}, {"role": "assistant", "content": "## Control Baselines for Information Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-53B\n\n\n\n## NIST Special Publication 800-53B\n\n## Control Baselines for Information Systems and Organizations\n\n## JOINT TASK FORCE\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B\n\n## October 2020\n\nINCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XI\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems. Such information security standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n- Prioritize the patch. A patch may be a higher priority to deploy than others because its deployment would reduce cybersecurity risk more than other patches would. Another patch may be a lower priority because it addresses a low-risk vulnerability on a small number of low-importance assets. - Schedule patch deployment. Many organizations schedule patch deployments as part of their enterprise change management activities. - Acquire the patch. Patches may be downloaded from the internet, built internally by developers or system administrators, or provided through removable media. - Validate the patch. A patch's authenticity and integrity should be confirmed, preferably by automated means, before the patch is tested or installed. The patch could have been acquired from a rogue source or tampered with in transit or after acquisition. - Test the patch. A patch may be tested before deployment. This is intended to reduce operational risk by identifying problems with a patch before placing it into production. Testing may be performed manually or through automated methods. - Distribute the patch. Distributing the patch to the assets that need to have it installed can be organization-controlled (and occur automatically, manually, or as scheduled) or vendor-controlled, such as delivered from the cloud. - Validate the patch. As discussed in Section 2.3.1, a patch's authenticity and integrity should be confirmed before installation, preferably through automated means. - Install the patch. Installation can occur in numerous ways, including automatically; manually when directed to do so by a user, administrator, vendor, or tool; as a result of other software being installed or updated; and through the replacement of removable media used by an asset. Some installations require administrator privileges, such as installing firmware patches for a system basic input/output system (BIOS). 3 Some patch installations require user participation or cooperation."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 9)"}, {"role": "assistant", "content": "facturer may have detailed design knowledge, while an end user typically has limited access and little insight into a system's internal functions. As a result, their capabilities differ significantly.\nThus, collusion between adversaries from different stages of the life cycle can make threats considerably more severe, which is why this stage is crucial in the context of security analysis. At this point in the analysis, we apply a linear scale to determine the severity of threats when adversaries from different stages of the supply chain collude. This scale ranges from 0 to 10 and represents the relative threat level of a group of colluding adversaries. Fig. 3 is an example of the scale developed in the context of the threat of hardware trojan insertion. The scale begins at 10, representing the highest threat severity level. This scenario assumes that all relevant adversaries are collaborating. From this point, we progressively remove one adversary at a time from the collusion and assess the resulting threat severity for each possible combination of remaining adversaries. As adversaries are removed, the threat severity decreases, depending on the number of adversaries and their specific roles. For instance, as shown in Fig. 3, if the manufacturer is removed from the collusion, the threat severity level drops to 8. However, if the designer is removed, the threat severity level decreases to 6. This suggests that a malicious designer poses a higher risk of hardware Trojan insertion compared to a malicious manufacturer. Fig. 3. Threat severity levels for colluding adversaries in the context of hardware Trojan insertion\n\n\n\nThis scale is relative, meaning it provides a context on the severity of the threat posed by different adversaries in a collusion but does not quantify the exact difference in severity. For example, Fig."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.3.3 Industry-recognized Certifications\n\n## Focus Groups\n\nIn an open-ended question, participants were asked what, if any, industry-recognized certifications they held (Figure 16). 3.3.3)."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide? (Part 4)"}, {"role": "assistant", "content": "Internet of Things (IoT) devices, embedded systems, and low-power sensors. The family is developed to offer a viable alternative when the Advanced Encryption Standard (AES) may not perform optimally.\nThis standard outlines the technical specifications and security properties of Ascon-AEAD128 , Ascon-Hash256 , Ascon-XOF128 , and Ascon-CXOF128 . ## Keywords\n\nAscon; authenticated encryption; constrained devices; eXtendable Output Function (XOF); hash function; lightweight cryptography; permutation-based cryptography; standardization. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.1.1. 3.1.1), purge (see Sec. 3.1.1."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nExternal attackers may include foreign adversaries, criminal organizations, and cyber-activists who target an SSC for various reasons, such as espionage or sabotage. Internal attackers pose a significant risk, as they may have insider access to sensitive information - often using legitimate access rights - that allow them to launch attacks or steal confidential information. Additionally, both categories of threat actors may use a variety of techniques to compromise the SDLC environment and steal or manipulate software, such as phishing, malware, social engineering, and physical access. Therefore, companies should be aware of these risks and take appropriate measures (see Sec. 3.2) to secure their SSC.\n\n- Malware\n- Code reuse or the ingest of libraries and dependencies\n- Social engineering\n- Network-based attacks\n- Physical attacks\n\nAttack vectors can originate from various sources, including malware attacks on developer workstations, social engineering attacks on developers, network-based attacks on the development environment, and physical attacks on the hardware or networks used by developers. These different attack vectors require distinct countermeasures, including endpoint protection software, network security controls, access control policies, and physical security measures. Companies should identify potential risks and vulnerabilities, assess their security posture, and implement appropriate defensive measures to mitigate threats to their SDLC environment."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Security Assessment?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| 1. Document assumptions made during the development process and other expectations related to the IoT device, such as: a. Expected customers and use cases b. Physical use and characteristics c. Network access and requirements (e.g., bandwidth requirements) d. Data created and handled by the device e. Expected data inputs and outputs (including error codes, frequency, type/form, range of acceptable values, etc.) f. Assumed cybersecurity requirements for the IoT device g. Laws and regulations with which the IoT device and related support activities comply h. Expected lifespan, anticipated cybersecurity costs related to the IoT device (e.g., price of maintenance), and term of support 2. Document the device cybersecurity capabilities , such as those detailed within NISTIR 8259A, that are implemented within the IoT device and how to configure and use them. 3. Document device design and support considerations related to the IoT device, such as: 4 a. IoT platform 5 used in the development and operation of the IoT device and related documentation b. Protection of software and hardware components of the IoT device (e.g., secure boot, hardware root of trust, and secure enclave) c. Consideration of the known risks related to the IoT device and known potential misuses d. Secure software development and supply chain practices used e. Accreditation, certification, and/or evaluation results for cybersecurity-related practices | • This capability supports Information Dissemination and Education and Awareness. • Manufacturers and/or supporting entities should consider documentation throughout their development lifecycle in order to capture cybersecurity-relevant information when it is available so as to ensure access to this information when it is needed. Documentation will begin as internal resources for a manufacturer and/or supporting entity that can be used in various ways."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nTim Grance and Murugiah Souppaya of NIST and Lucinda Gagliano, Thomas Goff, and Pius Uzamere of Booz Allen Hamilton for their keen and insightful assistance throughout the development of the document.\nThe authors would also like to express their thanks to security experts Mike Danseglio (Microsoft), Kurt Dillard (Microsoft), Michael Gerdes (Getronics RedSiren Security Solutions), Peter Szor (Symantec), Miles Tracy (U.S. Federal Reserve System), and Lenny Zeltser (Gemini Systems LLC), as well as representatives from the General Accounting Office, and for their particularly valuable comments and suggestions."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n| Table 1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 3 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| Table 2. Terms and definitions........................................................... | 3 |\n| Table 3. Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 5 |\n| Table 4. Basic operations and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 6 |\n| Table 5. The constants const 𝑖 to derive round constants of the Ascon permutations. | 9 |\n| Table 6. Lookup table representation of SBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| Table 7. Security strength of Ascon-AEAD128 with 𝜆 -bit tag in the 𝑢 -key setting, where ( 𝑁 , 𝐴 ) pairs are distinct for encryption per key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 21 |\n| Table 8. Integrity security strength of Ascon-AEAD128 with 𝑢 keys in the nonce- misuse setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 22 |\n| Table 9. Security strengths of Ascon-Hash256 , Ascon-XOF128 , and Ascon-CXOF128 algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 31 |\n| Table 10. Address for each byte of Ascon state word 𝑆 𝑖 in memory on little-endian and big-endian machines, where the word 𝑆 𝑖 begins at memory address 𝑎 . . . . . . . . . . | 36 |\n| Table 11."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.7 (NIST 3.2.7)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.2.7. 3.2.7."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.2.7", "cmmc_practice_id": "AT.L2-3.2.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nributing and installing a patch, purchasing cybersecurity insurance, deploying additional security controls, and changing asset configurations and state (e.g., software reset,\n\n- Distribute the patch.\nDistributing the patch to the assets that need to have it installed can be organization-controlled (and occur automatically, manually, or as scheduled) or vendor-controlled, such as delivered from the cloud. - Validate the patch. As discussed in Section 2.3.1, a patch's authenticity and integrity should be confirmed before installation, preferably through automated means. - Install the patch. Installation can occur in numerous ways, including automatically; manually when directed to do so by a user, administrator, vendor, or tool; as a result of other software being installed or updated; and through the replacement of removable media used by an asset. Some installations require administrator privileges, such as installing firmware patches for a system basic input/output system (BIOS). 3 Some patch installations require user participation or cooperation. - Change software configuration and state. In some cases, making a patch take effect necessitates implementing changes. Examples include restarting patched software, rebooting the operating system or platform on which the patched software runs, redeploying the applications, or altering software configuration settings. In other cases, no such changes are needed. - Resolve any issues. Installing a patch may cause side effects to occur, like inadvertently altering existing security configuration settings or adding new settings, and these side effects can inadvertently create a new security problem while fixing the original one. Patch installation can also cause operational issues that may necessitate uninstalling the patch, reverting to the previous version of the software, or restoring the software or asset from backups."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n3.2.2 SELECT PROCEDURES TO ASSESS THE SECURITY AND PRIVACY CONTROLS\n\nSP 800-53A provides assessment procedures for each security and privacy control and control\nenhancement in [SP 800-53]."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Software Supply Chain (SSC) -Definition and Model .....................................................................4 |\n| 2.4.1. Software Supply Chain Defects ....................................................................................................6 |\n| 2.4.2. Software Supply Chain Attacks.....................................................................................................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1. Developer Environment ...............................................................................................................8 |\n| 3.1.2. Threat Actors................................................................................................................................8 |\n| 3.1.3. Attack Vectors ..............................................................................................................................9 |\n| 3.1.4. Attack Targets (Assets).................................................................................................................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ordered t-way Combinations for Testing State-based Systems provide? (Part 5)"}, {"role": "assistant", "content": "h possible interleaving. Note that the event sequence array has sequences of events in each row . Event sequences are made up of a value in a column followed by values in columns to the right. Fig. 1.\nEvent sequence\n\n| Test | p0 | p1 | p2 | p3 |\n|--------|------|------|------|------|\n| 1 | a | d | b | c |\n| 2 | b | a | c | d |\n| 3 | b | d | c | a |\n| 4 | c | a | b | d |\n| 5 | c | d | b | a |\n| 6 | d | a | c | b |\n\nCombinatorial testing with constraints on the order in which values and combinations are applied in tests was analyzed extensively in [5] . Extended covering arrays that consider the sequence of values in each test were defined in [6] . Combination sequences were studied in [20] , combining configuration and the order of combinations while also considering constraints. Another structure defined as a sequence covering array of t -way combinations has been termed a multi-valued sequence covering array, introduced in [25] . ## 3 Ordered Combination Covering\n\nA combination order is different from an event sequence. As noted in the previous section, an event sequence is a possibly interleaved sequence of symbols in a single row of a test array. A combination order, as defined below, is across multiple rows, given in the order in which tests will be executed. A t -way permutation of symbols is referred to as a t-way order , which will be called a t -order for brevity. The t events in the order may be interleaved with others (i.e., the order a → b → c covers three 2-event orders: a followed by b and b followed by c , and a followed by c ). Denoting event a eventually followed by event b , possibly with other events interleaved, is written as a *→ b ."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 8)"}, {"role": "assistant", "content": "disagreed that they have adequate staff for conducting RBT activities. - Measuring RBT effectiveness: Just over half of survey participants rated their RBT activities as moderately or very successful.\nHowever, there is great variation in how organizations determine success, with most relying on compliance metrics, such as training completion rates, that do not necessarily measure impact on employee learning or behaviors. Close to 60% of survey participants rated measuring RBT success as challenging. These results suggest the need to provide more guidance and baseline standards for federal RBT activities. An upcoming NIST update to NIST SP 800-50 Building a Cybersecurity and Privacy Learning Program , which our research has informed, may address many of the suggestions for supporting organizations through guidance. Additionally, federal organizations may benefit from standard, government-wide RBT content that could then be tailored to unique mission needs. ## STUDYGLYPH<c=2,font=/GAAAAA+HKGrotesk-Bold> BACKGROUNDGLYPH<c=2,font=/GAAAAA+HKGrotesk-Bold> ANDGLYPH<c=2,font=/GAAAAA+HKGrotesk-Bold> PURPOSEGLYPH<c=2,font=/GAAAAA+HKGrotesk-Bold>\n\n\n\n## What is cybersecurity role-based training (RBT)? Cybersecurity role-based training (RBT) includes specialized training on policies, procedures, tools, and methods for individuals who are assigned management, operational, and technical roles having security and privacy responsibilities [SP800-53]. RBT is tailored to specific roles within an organization and differs from the general cybersecurity awareness training targeted at all personnel within an organization. ## U.S. Federal Government organizations are required to conduct RBT. NIST Special Publication (SP) 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations , provides guidance for organizations in protecting their operations, assets, and personnel from security threats and risks [SP800-53]."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 6)"}, {"role": "assistant", "content": "|\n| LIST OFTABLES....................................................................................................................\n| LIST OFTABLES.................................................................................................................... | VIII |\n| EXECUTIVE SUMMARY........................................................................................................... | EXECUTIVE SUMMARY........................................................................................................... | 1 |\n| 1. INTRODUCTION.................................................................................................................. | 1. INTRODUCTION.................................................................................................................. | 1 |\n| 1.1 | PURPOSEAND SCOPE ......................................................................................................... | 1 |\n| 1.2 | AUDIENCEAND ASSUMPTIONS .........................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\n## 5.1.2.3.Updates\n\nParticipants were asked how updates to standards impacted their product lifecycle. Sometimes, updates to standards specifications can be disruptive:\n\nTwo participants commented on interdependencies of standards, and that problems with updates to all applicable documents aren't always closely coordinated:"}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nAssurance; availability; computer security; confidentiality; control; cybersecurity; FISMA;\ninformation security; information system; integrity; personally identifiable information; Privacy\nAct; privacy controls; privacy functions; privacy requirements; Risk Management Framework;\nsecurity controls; security functions; security requirements; system; system security. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ........................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n- NIST Framework for Improving Critical Infrastructure Cybersecurity (commonly known as the NIST Cybersecurity Framework [1]\n- NIST Interagency or Internal Report (NISTIR) 8050: Executive Technical Workshop on Improving Cybersecurity and Consumer Privacy [2]\n- NIST Special Publication (SP) 800-30 Rev. 1: Guide for Conducting Risk Assessments [3]\n- NIST SP 800-37 Rev. 1: Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach [4]\n- NIST SP 800-39: Managing Information Security Risk [5]\n- NIST SP 800-40 Rev. 3: Guide to Enterprise Patch Management Technologies [6]\n- NIST SP 800-53 Rev. 4: Security and Privacy Controls for Federal Information Systems and Organizations [7]\n- Federal Information Processing Standard 140-2: Security Requirements for Cryptographic Modules [8]\n- NIST SP 800-86: Guide to Integrating Forensic Techniques into Incident Response [9]\n- NIST SP 800-92: Guide to Computer Security Log Management [10]\n- NIST SP 800-100: Information Security Handbook: A Guide for Managers [11]\n- NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems [12]\n- Office of Management and Budget, Circular Number A-130: Managing Information as a Strategic Resource [13]\n- NIST SP 800-61 Rev. 2: Computer Security Incident Handling Guide [14]\n- NIST SP 800-83 Rev."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U:\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nCalis A (2023) Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods: CMVP Validation Authority Updates to ISO/IEC 24759. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-140Dr2. https://doi.org/10.6028/NIST.SP.800-140Dr2"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.14. SQIsign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.14. SQIsign"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 4)"}, {"role": "assistant", "content": "pment of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems.\nThe Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThe protection of Controlled Unclassified Information (CUI) resident in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides federal agencies with recommended enhanced security requirements for protecting the confidentiality of CUI: (1) when the information is resident in nonfederal systems and organizations; (2) when the nonfederal organization is not collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency; and (3) where there are no specific safeguarding requirements for protecting the confidentiality of CUI prescribed by the authorizing law, regulation, or government-wide policy for the CUI category listed in the CUI Registry. The enhanced requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide security protection for such components when the designated CUI is associated with a critical program or high value asset. The enhanced requirements supplement the basic and derived security requirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Planning?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "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.\nParameters 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n8 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products).\nSince many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nSince many users may not fully understand cybersecurity risks to their IoT products, education materials should clearly communicate the relevance of product cybersecurity features (what the features do and why these are of importance) and what actions are expected of the users (e.g., changing settings or physically safeguarding the product). Instructions for setting cybersecurity preferences should be clear, simple, and achievable for those without cybersecurity expertise. To support diverse users with different cybersecurity and technical needs, skills, and interests, a layered approach for education materials may also be helpful; first present basic information, then provide links to more detail for those who need or want it.\n\nThe team identified that firmware updates are critical to the cybersecurity of a smart teddy bear. Team participants also noted that privacy was also noted as a critical concern. The team envisioned utilizing videos and physical manuals to communicate with customers and users. They developed two manuals: one for parents and another for children, allowing for a more targeted audience approach. The adult manual was detailed and focused on salient tips and direct, easy access to resources. The child manual was designed around the idea that the child could help drive cybersecurity and that the product could help teach good cyber hygiene. For example, the eyes of the bear can glow red when an update is needed, prompting the child to seek help, as the team describes in their mock-up of the story book in Fig. 2."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n|\n| Federal Vulnerability Disclosure Coordination Body ....................................................\n| 6 | |\n| Preparation................................................................................................................. | 7 | |\n| 2.1.1. Create Source Vulnerability | Report Receipt Capability............................................. 7 | |\n| 2.1.2. Determine Scope and Obtain Contacts .................................................................... | 8 | |\n| 2.1.3. Develop Technical Analysis Capability ....................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nework. The assessment procedures, executed at various phases of the system\ndevelopment life cycle, are consistent with the security and privacy controls in NIST Special\nPublication 800-53, Revision 5.\nThe procedures are customizable and can be easily tailored to\nprovide organizations with the needed flexibility to conduct security and privacy control\nassessments that support organizational risk management processes and are aligned with the\nstated risk tolerance of the organization. Information on building effective security and privacy\nassessment plans is also provided with guidance on analyzing assessment results."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 10)"}, {"role": "assistant", "content": "s scale is relative, meaning it provides a context on the severity of the threat posed by different adversaries in a collusion but does not quantify the exact difference in severity. For example, Fig.\n3 illustrates that a collusion between an integrator and a designer presents a more severe threat than one involving a manufacturer and a designer, but the scale does not specify how much more severe the threat is. This relative approach is intentional, as different stakeholders may prioritize different metrics for evaluating threat severity. One analyst might prioritize attack completion time, while another may focus on the likelihood of attack success. This flexibility allows analysts to develop their own customized, non-linear scales based on the metrics they deem most important. These scales can provide a more detailed understanding,\n\nsuch as quantitatively comparing the severity of a designer's threat versus that of a manufacturer. ## 3.5. Identify Security-Critical Stages for the Respective Threat\n\nThe final step involves determining the type and severity of each threat in relation to where it is located on the semiconductor supply chain. The choice of which stage in the semiconductor supply chain may and should be secured must be made at this step, taking into account all threat matrices. This inevitably comes down to weighing the cost-security trade-off. ## 4. Case Study\n\nThis framework for supply chain threat analysis is meant to adapt to different threat types. The following example scenarios consider IP theft and hardware infiltration. ## 4.1. Hardware Infiltration\n\n- Step 1: A security analysis identifies an adversary's intent to infiltrate a chip. To that end, the adversary might take steps that make the hardware unusable, transmit sensitive information from the chip [9], or receive signals that can make the chip operate abnormally. - Step 2: One method of infiltrating hardware is through the insertion of hardware Trojans."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 7)"}, {"role": "assistant", "content": "ach that could be used to support cybersecurity education and awareness.................................................................................. 12 |\n| Fig. 10.\nMock-up of how answers to the guided questions will impact what customers see and how the content will be gamified..........................................................................................................13 |\n\n## Acknowledgments\n\nNIST thanks all the organizers of USENIX SOUPS and the Tutorials and Workshops Co-Chairs, specifically, for the opportunity to bring our idea for a Design-A-Thon to the symposium. We also thank everyone who participated in the Design-A-Thon, giving their time and bringing the great ideas documented in this report. ## 1. Introduction\n\nOn August 11, 2024, National Institute of Standards and Technology (NIST) researchers facilitated a Design-A-Thon titled Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness which was hosted at the 2024 USENIX Symposium on Usable Privacy and Security (SOUPS). The Design-A-Thon was organized by Michael Fagan, Daniel Eliot, Barbara Cuthill, and Julie Haney with support from Kristina Rigopoulos, all members of the NIST Information Technology Lab (ITL). Background on the foundations for this project is provided in Section 2, while details about the planning and execution of the Design-A-Thon are discussed in Section 3. In total, eight conference attendees participated in the event, forming three teams. Each team selected a mock product based on a selection of five Product Data Cards developed by the NIST team. The Product Data Cards developed for the Design-A-Thon can be seen in Appendix B. Participants used the information on the Product Data Cards to develop a strategy for cybersecurity education and awareness for the product. The team's designs and ideas are documented in Section 4."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| | | | | R4: Permit indirect access only to model weights."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nuse that device in DDOS and other attacks. | Mirai Malware Variants Attacks - Use of weak authentication to enable the loading of malware onto the device and use that device in DDOS and other attacks.\n|\n| Unauthorized access to the IoT device | Asset Identification Interface Access Control Information Dissemination Education and Awareness |\n| Malicious code can be loaded on the IoT device | Software Update Cybersecurity State Awareness Education and Awareness |"}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide to a Secure Enterprise Network Landscape provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication NIST SP 800-215\n\n## Guide to a Secure Enterprise Network Landscape\n\nRamaswamy Chandramouli\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-215\n\n\n\n## NIST Special Publication NIST SP 800-215\n\n## Guide to a Secure Enterprise Network Landscape\n\nRamaswamy Chandramouli\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-215\n\nNovember 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nLaurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nderal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?\n| The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. |\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 8)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . . . . 4.1.5. Attribute Validation . . . . . . . . . . . . . . . . . . . . . . . . 4.1.6. Verification Requirements . . . . . . . . . . . . . . . . . . . . . 4.1.7.\nRemote Unattended Requirements . . . . . . . . . . . . . . . . 4.1.8. Remote Attended Requirements\n\n. . . . . . . . . . . . . . . . . 4.1.9. On-Site Attended Requirements . . . . . . . . . . . . . . . . . . 4.1.10. On-Site Unattended Requirements\n\n. . . . . . . . . . . . . . . . 4.1.11. Notification of Proofing . . . . . . . . . . . . . . . . . . . . . . 4.1.12. Initial Authenticator Binding . . . . . . . . . . . . . . . . . . . . iv\n\n24\n\n25\n\n26\n\n27\n\n27\n\n30\n\n31\n\n33\n\n34\n\n35\n\n36\n\n36\n\n37\n\n38\n\n38\n\n39\n\n40\n\n40\n\n40\n\n40\n\n40\n\n41\n\n41\n\n41\n\n42\n\n42\n\n43\n\n43\n\n44\n\n44\n\n\fNIST SP 800-63A-4\nJuly 2025\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\n4.2. Identity Assurance Level 2 Requirements . . . . . . . . . . . . . . . . . 4.2.1. Proofing Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2. Evidence Collection . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3. Attribute Collection . . . . . . . . . . . . . . . . . . . . . . . . 4.2.4. Evidence Validation . . . . . . . . . . . . . . . . . . . . . . . . 4.2.5. Attribute Validation . . . . . . . . . . . . . . . . . . . . . . . . 4.2.6. Verification Requirements . . . . . . . . . . . . . . . . . . . . . 4.2.7. Remote Unattended Requirements . . . . . . . . . . . . . . . . 4.2.8. Remote Attended Requirements\n\n. . . . . . . . . . . . . . . . . 4.2.9. On-Site Attended Requirements . . . . . . . . . . . . . . . . . . 4.2.10. On-Site Unattended Requirements\n\n. . . . . . . . . . . . . . . . 4.2.11. Notification of Proofing . . . . . . . . . . . . . . . . . . . . . . 4.2.12. Initial Authenticator Binding . . . . . . . . . . . . . . . . . . . . 4.3. Identity Assurance Level 3 . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1. Proofing Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide?"}, {"role": "assistant", "content": "## NIST SPECIAL PUBLICATION 1800-37\n\n## Addressing Visibility Challenges with TLS 1.3 within the Enterprise High-Level Document\n\nBill Newhouse Murugiah Souppaya David Cooper Tim Polk*\n\nNational Institute of Standards\n\nWilliam Barker\n\nStratvia LLC\n\nKaren Scarfone\n\nScarfone Cybersecurity\n\nJohn Kent Julian Sexton Michael Dimond Josh Klosterman Ryan Williams\n\nThe Mitre Corporation\n\nDavid Wells Johann Tonsing\n\nMira Security\n\nSean Turner\n\nsn3rd\n\nPatrick Kelsey\n\nNot for Radio\n\nRuss Housley\n\nVigil Security LLC\n\nTim Cahill\n\nJPMorgan Chase & Company\n\nMuralidharan Palanisamy\n\nAppViewX\n\nDung Lam\n\nF5\n\nPaul Barrett Ray Jones Sandeep Jha\n\nNetscout\n\nSteven Fenter Jake Wills\n\nUS Bank Corporation\n\nJane Gilbert D'Nan Godfrey\n\nThales TCT\n\nDean Cocklin Avesta Hojjati\n\nDigiCert\n\n*Contributed while a NIST Employee\n\nSeptember 2025\n\nFINAL\n\nThis publication is available free of charge from htps://www.nccoe.nist.gov/addressing -visibility-challenges-tls-13\n\n\n\n\n\n## NIST SPECIAL PUBLICATION 1800-37\n\n## Addressing Visibility Challenges with TLS 1.3 within the Enterprise High-Level Document\n\nBill Newhouse Murugiah Souppaya David Cooper Tim Polk* National Institute of Standards\n\nWilliam Barker Stratvia LLC\n\nKaren Scarfone Scarfone Cybersecurity\n\nJohn Kent Julian Sexton Michael Dimond Josh Klosterman Ryan Williams The Mitre Corporation\n\nJohann Tonsing Mira Security\n\nSean Turner sn3rd\n\nPatrick Kelsey Not for Radio\n\nRuss Housley Vigil Security LLC\n\nTim Cahill\n\nJPMorgan Chase & Company\n\nMuralidharan Palanisamy AppViewX\n\nDung Lam F5\n\nPaul Barrett Ray Jones Sandeep Jha Netscout\n\nSteven Fenter Jake Wills US Bank Corporation\n\nJane Gilbert D'Nan Godfrey Thales TCT\n\nDean Cocklin Avesta Hojjati DigiCert\n\n*Contributed while a NIST Employee\n\nDavid Wells\n\nFinal September 2025\n\n\n\nU.S."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\n- Securely Provision (SP): Risk Management (RSK), Software Development (DEV), Systems Requirements Planning (SRP), Test and Evaluation (TST), Systems Development (SYS)\n- Operate and Maintain (OM): Systems Analysis (ANA)\n- Oversee and Govern (OV): Training, Education, and Awareness (TEA); Cybersecurity Management (MGT); Executive Cyber Leadership (EXL); Program/Project Management (PMA) and Acquisition\n- Protect and Defend (PR): Incident Response (CIR), Vulnerability Assessment and Management (VAM)\n- Analyze (AN): Threat Analysis (TWA), Exploitation Analysis (EXP)\n\nFactors such as risk, cost, feasibility, and applicability should be considered when deciding which practices to use and how much time and resources to devote to each practice. 4 Automatability is also an important factor to consider, especially for implementing practices at scale. The practices, tasks, and implementation examples represent a starting point to consider; they are meant to be changed and customized, and they are not prioritized. Any stated frequency for performing practices is notional. The intention of the SSDF is not to create a checklist to follow, but to provide a basis for planning and implementing a risk-based approach to adopting secure software development practices."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nComplex IoT products may contain multiple physical IoT devices, contain other kinds of equipment, or connect to multiple backends or companion applications as components. Though there are possibly a large number of component combinations that may create an IoT product, it is helpful to think of three specific kinds of IoT product components (other than the IoT device itself, which is always present in an IoT product):\n\n4 'In the box' components, particularly the IoT device(s) that serves as the product end point can be considered the face of the IoT product since these are what a customer will physically handle, manage, and use. Though other components may be vital to operation of the IoT product (including cybersecurity), the IoT device(s) plays a central role to the IoT product and, in general, is the focus of the operation of the IoT product. 5 Some 'outside the box' components may be entirely remote relative to the customer, while others may be physically present in the customer's environment (e.g., inside their home), but, nonetheless, come separate from the IoT device(s)."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nVulnerabilities are discovered by a variety of sources. Developers of software may find security bugs in already deployed code. Security researchers and penetration testers may find vulnerabilities by scanning or manually testing software and accessible systems (following published rules of behavior). While identifying an issue, users of systems may stumble across a vulnerability. Malicious actors may seek out unknown or unpublished vulnerabilities and use them in malware. Evidence of these attacks may then be discovered and analyzed by security experts, resulting in an identified vulnerability being reported. Regardless of who finds these vulnerabilities, it is critical that they are reported so that the owners of vulnerable software and systems can resolve or identify ways to mitigate the reported vulnerabilities. In many cases, owners should issue advisories to notify users of any actions to be taken (e.g., patches to be installed) or of potential damage to systems (i.e., potential consequences of the vulnerability having existed)."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nIT professionals who want to implement an approach like this can make use of NIST SP 1800-34c: HowTo Guides . It provides specific product installation, configuration, and integration instructions for building the example implementation, allowing you to replicate all or parts of this project. NIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors. They are practical, user-friendly guides that facilitate the adoption of standards-based approaches to cybersecurity. They show members of the information security community how to implement example solutions that help them align with relevant standards and best practices, and provide users with the materials lists, configuration files, and other information they need to implement a similar approach."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.2.1 | Number of Additional Activities... 3.2.1 Number of Additional Activities\n\nWe asked participants how many other security awareness activities or events their organizations offered per year in addition to required annual training (see Figure 6)."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n- The global control plane can be leveraged to perform the functions of individual control planes at the enterprise level rather than at the cluster level (e.g., issuing identities to all services in the enterprise by leveraging the enterprise Public Key Infrastructure (PKI) system).\n- The global control plane can also be used to shut down a specific control plane if all cluster nodes under the jurisdiction of that control plane have been compromised.\n- The management plane provides the human-computer interfaces (e.g., user interfaces, such as command line interfaces and APIs) that enable enterprise-level systems to work by encoding organizational processes related to the usage of various tools (e.g., policy definition and evaluation tools, telemetry tools) at the lower layer.\n\n- Identity-tier policies enable the automated testing of policies. Policies that are independent of infrastructure can be tested by merely exercising the application and observing the outcomes (e.g., trace the sequence of service calls and requests or responses instead of configuring the infrastructure correctly for test runs).\n- Identity-tier policies enable 'policy as code' (PaC). With the availability of tools for the declarative specification of policies through PaC, identity-tier policies can be defined and implemented by incorporating the code into automated workflows, such as continuous integration/continuous delivery (CI/CD) pipelines.\n- Identity-tier policies enable fine-grained access control by providing visibility into application call sequences/interdependencies and data flows through request-level tracking, which enables the enforcement of security policies for application traffic that is both north-south and east-west, irrespective of the environment (e.g., corporate data center or cloud infrastructure)."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 4.2 | Access Policies | 4-12 |\n|-------------|------------------------------------------------------------------------------------------------|-----------|\n| 4.3 | Unauthorized Statistical Disclosure | 4-12 |\n| 4.4 | Transaction Trail | 4-13 |\n| | 4.4.1 Automated Journals | 4-13 |\n| 4.5 | Data Checks and Integrity | 4-13 |\n| 5. | APPLICATIONS INTERFACE | 4-14 |\n| 5.1 | General | 4-14 |\n| 5.2 | System Development Controls | 4-14 |\n| 5.3 | Project Definition | 4-14 |\n| 5.4 | System Design | 4-15 |\n| 5.5 | Detailed Design and Programming | 4-15 |\n| 5.6 | System Testing | 4-15 |\n| 5.7 6."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nous monitoring strategy/program can guide the scope of the reauthorization to focus on those environment/facility controls and any other controls which would be impacted by the reconstitution efforts.\nAssessment and authorization guidance is available in NIST SP 800-37, Rev. 1 Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.2.5 Output Handling | 4-11 |\n| | | | 4-11 |\n| | | 3. 3.2.5 Output Handling ."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.4.3 | Risk ... 3.4.3 Risk\n\nThe risk to an organization is the intersection of:\n\n-  the vulnerabilities and threats to the organization\n-  the likelihood that the vulnerability and threat event will be realized\n-  the impact to the organization should the event be realized\n\nA meaningful risk assessment must be performed in the context of the cyber-ecosystem and the impact to an organization should a loss or degradation occur."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\ndvisory services to improve the effectiveness of\ncomputer utilization in the Federal sector, and to perform appropriate research and\ndevelopment efforts as foundation for such activities and programs.\nThis publication\nseries will report these NBS efforts to the Federal computer community as well as to\ninterested specialists in the academic and private sectors. Those wishing to receive\nnotices of publications in this series should complete and return the form at the end\nof this publication."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nlar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172A Natl. Inst. Stand. Technol. Spec. Publ. 800-172A, 62 pages (March 2022)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nxample, a user network contains the nodes in the access zone and the computer nodes in the high-performance computing zone. Cryptographic mechanisms are an effective means of providing data integrity.\nHPC data storage systems typically support uniform encryption at the file level or block level. Such data encryption at the file system level protects data from unauthorized access. However, it does not provide granular access (i.e., segmenting one user from others). Granular access can be achieved using user-level or group-level encryption. Not even a system administrator can access a user's data with granular access since they do not have access to the decryption key. Additionally, file systems do not authorize users. Rather, users access the file system via the HPC access zone, which is responsible for authenticating the users and their access rights. In general, file systems should not be mounted outside of their local security boundaries unless the file system protocol appropriately authenticates users. For example, an attacker-controlled"}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\n- I. All data sources and computing services are considered resources. An enterprise relies on different resources to perform its mission: mobile devices, data stores, compute resources (including virtual), remote sensors/actuators, etc. All these components are resources and need to be considered in a ZTA. Some components (e.g., IoT sensors) may not be able to support some solutions such as configuration agents, application sandboxing, etc. so compensating technologies or alternative mitigations may be needed. If the resource lacks certain security capabilities, the enterprise may need to add a PEP component to provide that functionality. - II. The enterprise monitors and measures the integrity and security posture of all owned and associated resources. This tenet deals with the aspects of cyber hygiene for both enterprise-owned resources and those that may not be owned, but used in an enterprise workflow such as configuration, patching, application loading, etc. The state of resources should be monitored, and appropriate action taken when new information such as a new vulnerability or attack is reported or observed. The confidentiality and integrity of data on the resource should be protected. This requires enterprise admins to know how resources are configured, maintained, and monitored. - III. Access to resources is determined by dynamic policy-including the observable state of client identity, application/service, and the requesting asset-and may include other behavioral and environmental attributes. In zero trust, the default behavior for all resources is to deny all connections and only accept connections that are explicitly allowed by policy. Those authorized to access the resource must still authenticate themselves and prove they meet the enterprise policy to be granted the session. This may include meeting requirements such as client software versions, patch level, geolocation, historical request patterns, etc."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ordered t-way Combinations for Testing State-based Systems provide? (Part 10)"}, {"role": "assistant", "content": "ruction of OCCs are of interest. Example. Fig. 6 shows a test array that covers all 2way combinations of values for four parameters, as well as all 2-sequences of 2-way parameter combinations. Fig.6.\nTests for four parameters, OCC(20,2,4,2)\n\n\n\n| | p 1 | p 2 | p 3 | p 4 |\n|----|-------|-------|-------|-------|\n| 1 | 1 | 1 | 1 | 0 |\n| 2 | 0 | 0 | 0 | 0 |\n| 3 | 1 | 1 | 0 | 1 |\n| 4 | 0 | 0 | 1 | 1 |\n| 5 | 1 | 1 | 0 | 0 |\n| 6 | 1 | 1 | 1 | 1 |\n| 7 | 0 | 1 | 1 | 0 |\n| 8 | 0 | 1 | 1 | 0 |\n| 9 | 0 | 1 | 0 | 1 |\n| 10 | 1 | 1 | 1 | 1 |\n| 11 | 1 | 0 | 1 | 0 |\n| 12 | 1 | 1 | 0 | 1 |\n| 13 | 0 | 1 | 1 | 1 |\n| 14 | 0 | 0 | 0 | 0 |\n| 15 | 0 | 0 | 0 | 1 |\n| 16 | 0 | 0 | 1 | 0 |\n| 17 | 1 | 1 | 1 | 0 |\n| 18 | 0 | 1 | 0 | 1 |\n| 19 | 1 | 1 | 1 | 0 |\n| 20 | 1 | 0 | 1 | 1 |\n\nThat is, the test array includes every solution of ( pwpx = v 1 v 2 ) *→ ( pypz = v 1 v 2 ), of which there are ( 𝐶𝐶 (4,2) 𝑥𝑥 2 2 ) 2 = 576 instances. For example, each of the four possible settings of p 1 p 2 is followed by each of the four possible settings of p 3 p 4 somewhere in the table (distinguished by color). That is, ( p1p2 = 11) in line 1 is followed by ( p3p4 = 01), ( p3p4 = 01), ( p3p4 = 11), ( p3p4 = 00), ( p3p4 = 10) in lines 3, 4, 5, and 7, respectively, highlighted in yellow (also for ( p1p2 = 00)). Sequences for ( p1p2 = 01) are shown in green, plus line 14, which provides a ( p3p4 = 00) for both ( p1p2 = 01) and ( p1p2 = 10). Sequences for ( p1p2 = 10) are highlighted in blue. ## 3.1 Combination Sequence Covering Arrays in Testing\n\nAs seen in Fig."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.3.1 | KAS2 Key-Confirmation Components... 3.3.1 KAS2 Key-Confirmation Components\n\nThe components for KAS2 key agreement with key confirmation are the components in Section 8."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n..................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5.\nTraceability of CE Operations.....................................................................................................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1. Information Decisions in the System Life Cycle..........................................................................20 |\n| 4.3.2. Determination of Security Categorization..................................................................................21 |\n| 4.3.3. Reuse of Media...........................................................................................................................22 |\n| 4.3.4. Control of Media ........................................................................................................................22 |\n| 4.3.5. Data Protection Level .................................................................................................................23 |\n| 4.3.6. Sanitization and Disposal Decision.............................................................................................23 |"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\no prepare for contact from news media. Organization planning should consider facilitating close working relationships and supporting customer service to handle and respond to security vulnerabilities.\nThese capabilities may vary from a confidential means of communication with stakeholders to the escalation of questions from advisories for a coordinated response."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nThe term security will be used as a shorthand for 'cybersecurity' or 'information security.' Reference to physical security is different and will be labeled as such.\n\n□ Physical security"}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 6)"}, {"role": "assistant", "content": "s, Symbols and Abbreviations ............................................................... | 3. Definitions, Symbols and Abbreviations ...............................................................\n| 2 |\n| | 3.1 | Definitions........................................................................................................................ | 2 |\n| | 3.2 | Symbols and Abbreviations ............................................................................................. | 9 |\n| 4. Overview of Key-Establishment Schemes........................................................... | 4. Overview of Key-Establishment Schemes........................................................... | 4. Overview of Key-Establishment Schemes..........................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops tests,\ntest methods, reference data, proof of concept implementations, and technical analyses\nto advance the development and productive use of information technology. ITL’s respon-\nsibilities include the development of management, administrative, technical, and physical\nstandards and guidelines for the cost-effective security and privacy of other than national\nsecurity-related information in federal information systems.\n\n3.10. MAYO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.10. MAYO"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 6)"}, {"role": "assistant", "content": "|\n| 2.1.1. Components of the High-Performance Computing Zone.............................................................3 |\n| 2.1.2.\nComponents of the Data Storage Zone........................................................................................4 |\n| 2.1.3. Parallel File System.......................................................................................................................4 |\n| 2.1.4. Archival and Campaign Storage....................................................................................................5 |\n| 2.1.5. Burst Buffer ..................................................................................................................................5 |\n| 2.1.6. Components of the Access Zone..................................................................................................6 |\n| 2.1.7. Components of the Management Zone.......................................................................................6 |\n| 2.1.8. General Architecture and Characteristics ....................................................................................6 |\n| 2.1.9. Basic Services................................................................................................................................7 |\n| 2.1.10. Configuration Management.......................................................................................................7 |\n| 2.1.11. HPC Scheduler and Workflow Management..............................................................................7 |\n| 2.1.12. HPC Software..............................................................................................................................8 |\n| 2.1.13."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n.org/10.6028/NIST.SP.800-63-4\n- [4] Temoshok D, Fenton JL, Choong YY, Lefkovitz N, Regenscheid A, Galluzzo R, Richer JP (2025) Digital Identity Guidelines: Authentication and Authenticator Management.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63B-4. https://doi.org/10.6028/NIST.SP.800-63B-4\n- [5] Regenscheid A, Galluzzo R (2023) Phishing Resistance -Protecting the Keys to Your Kingdom. https://www.nist.gov/blogs/cybersecurity-insights/phishing-resistanceprotecting-keys-your-kingdom\n- [6] Cybersecurity and Infrastructure Security Agency (2025) List of Federal Financial Assistance Programs Funding Emergency Communications. https://www.cisa.gov/safecom/emergency-comms-grants-list\n- [7] Weston D (2024) Microsoft's guidance to help mitigate Kerberoasting. (Microsoft Corporation, Redmond, WA.) Available at https://www.microsoft.com/enus/security/blog/2024/10/11/microsofts-guidance-to-help-mitigate-kerberoasting/\n- [8] Fisher W, Russell M, Umarji S, Scarfone K (2021) Background on Identity Federation Technologies for the Public Safety Community. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Internal Report 8336. https://doi.org/10.6028/NIST.IR.8336-draft\n- [9] Grassi PA, Nadeau EM, Richer JP, Squire SK, Fenton JL, Lefkovitz NB, Danker JM, Choong Y-Y, Greene KK, Theofanos MF (2017) Digital Identity Guidelines: Federation and Assertions. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63C, Includes updates as of March 02, 2020. https://doi.org/10.6028/NIST.SP.800-63C"}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\nmultitude of errors and developer pitfalls in the cryptographic implementations of software products [1-5]. However, these studies focused on the practices of less-experienced, individual developers.\nTherefore, there was little understanding of the cryptographic development practices of organizations, including the benefits and challenges of using cryptographic resources such as standards specifications and libraries."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nn the RMF; information resources as system and system elements; authorization boundaries; security and privacy posture; and security and privacy considerations related to supply chain risk management.\n- Chapter Three describes the tasks required to implement the steps in the RMF including: organization-level and information system-level preparation; categorization of information and information systems; control selection, tailoring, and implementation; assessment of control effectiveness; information system and common control authorization; the ongoing monitoring of controls; and maintaining awareness of the security and privacy posture of information systems and the organization. - Supporting Appendices provide additional information and guidance for the application of the RMF including:\n- -References;\n- -Glossary of Terms;\n- -Acronyms;\n- -Roles and Responsibilities;\n- -Summary of RMF Tasks;\n- -System and Common Control Authorizations;\n- -Authorization Boundary Considerations; and\n- -System Life Cycle Considerations."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.10 (NIST 3.2.10)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.10. 3.2.10\n\n4. 3.2.10."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.10", "cmmc_practice_id": "AT.L2-3.2.10", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\ned package. - The security team should approve the merging of unverified sources of OSS. - Developers should download OSS as source code rather than pre-compiled libraries or binaries, when available.\n- Developers should verify digital signatures, run vulnerability scans, check for recent updates on newly downloaded OSS's source-code packages, and generate an SBOM with dependency scanning on the first commit in order to identify the risks of any upstream or downstream dependencies within the OSS. - Artifacts should be scanned in internal repositories for newly discovered or identified defects and the ability to stop their use in builds based on criticality. - CI/CD processes should be audited regularly, and automation should be introduced wherever possible to improve the performance of activities and operations. - There should be isolated CI/CD environment and elevated administrator credentials for the deployment of applications in clouds. - There should be enhanced real-time monitoring and alerting mechanisms to detect suspicious activities in CI/CD servers, especially activities that might indicate the exfiltration of sensitive data or the tampering of builds."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Machine Learning for Access Control Policy Verification:\n\nMachine learning has been used for device control, system analysis, and business forecasting. However, the use of ML for software testing is in the early stages [AWCS, CAT5]. In particular, ML applications for model proof are still elusive and have yet to be explored. ML classification allows for the generation or prediction of target classes for new input data using some sample training data produced by running the system instead of comprehensive input data. For access control policy verification, the training data is assigned attributes' values of policy rules, and the target for classification is access permissions (e.g., grant and deny) assigned to rules. The data is consumed by an ML classification algorithm to generate a classification model . Querying the accuracy of training data against the model allows for the detection of inconsistencies, indicating faults found among policy rules. In addition, to verify new or updated policy rules, they need to be contained in test data for additional accuracy analysis on test data. 1. Enhancement of existing verification method - In addition to replacing traditional access control policy verification methods, the RFC verification method can be used to enhance traditional methods by checking the correctness of the policy model itself before applying it to test new or updated cases. Most traditional model verification methods assume that the access control policy has no faults until new or updated rules are tested against. For example, Access Control Policy Tool (ACPT) [Hwang et al. 10, ACPT] uses security requirements as test cases for counterexample generation of found faults. It would be more efficient if the policy model error can be verified without composing security requirements to discover faults that already exist in the model. 2."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nence is urgently needed…'\n\nThe security and privacy controls specified in the baselines represent the state-of-the-practice protection measures for individuals, information systems, and organizations.\nThe controls comprising the baselines are periodically reviewed and revised to reflect the experience gained from using the controls; new or revised laws, executive orders, directives, regulations, policies, and standards; changing security and privacy requirements; emerging threats, vulnerabilities, attacks, and information processing methods; and the availability of new technologies. Thus, the security and privacy controls specified in the baselines are also expected to change over time as controls are withdrawn, revised, and added. In addition to the need for change, the need for stability is addressed by requiring that proposed changes to the baseline undergo a rigorous and transparent public review process to obtain public and private sector feedback and to build a consensus for baseline changes. The public review process provides a stable, flexible, and technically sound set of security and privacy control baselines."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 7)"}, {"role": "assistant", "content": "second invitational workshop on computer security audit, entitled \"Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls,\" In Miami Beach, Florida, on November 28-30, 1978.\nA cross-section of highly qualified people In the computer science and EDP audit fields was assembled to develop material that would be directly usable for a Federal Information Processing Standard (FTPS) Guideline on the subject. Tn order to cover the material in a systematic fashion, the workshop was partitioned into three management sessions and five technical sessions. The management sessions addressed Managerial and Organizational Vulnerabilities and Controls at the Staff Level (1 session) and the Line Level (2 sessions). The technical sessions addressed vulnerabilities and controls in the areas of Terminal and Remote Peripherals, Communication Components, Operating Systems, Applications and Non- Integrated Data Files, and Data Base/ Data Base Management Systems. These Proceedings are the reports developed by the eight sessions of the workshop. Keywords: Applications controls, computer vulnerabilities, data base controls, data base management systems controls, EDP audit, internal audit, operating system controls, system controls, system vulnerabilities, terminal controls. ## ACKNOWLEDGEM ENTS\n\nThe success of the workshop can be attributed to the efforts of many people. Tn addition to thanking all the participants, T would particularly like to thank my CoChairperson, Robert G. McKenzle, for his untiring efforts in making the workshop a reality; the Session Chairpersons and Recorders for their efforts in producing the fire set of reports contained in these proceedings; Richard Canning for his excellent coordination activities while the workshop sessions were in progress; Dennis K. Branstad for the photographs taken during the workshop; and Tina Faecke for her steadfast typing support. Z. G."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.1.3 | Update Frequency... 3.1.3 Update Frequency\n\nParticipants indicated how often their organization updates security awareness training content, with 80% answering that they update it at least once a year."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 2)"}, {"role": "assistant", "content": "ovides a gap analysis of SCAP v1 and an overview of how SCAP v2 will address these gaps; describes the SCAP 2.0 architecture; and provides a plan for completing the work necessary to finalize SCAP v2.\n## Keywords\n\narchitecture; configuration; endpoint; endpoint security; SCAP; security automation; security content automation; Security Content Automation Protocol; software identification; SWID; vulnerability\n\n## Disclaimer\n\nAny 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\n\nFor additional information on NIST's Cybersecurity programs, projects and publications, visit the Computer Security Resource Center, https://csrc.nist.gov. Information on other efforts at NIST and in the Information Technology Laboratory (ITL) is available at https://www.nist.gov and https://www.nist.gov/itl. More information on NIST Software Identification and SCAP can be found at https://csrc.nist.gov/projects/Software-Identification-SWID and https://csrc.nist.gov/projects/security-content-automation-protocol respectively."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nA software developer's workstation typically contains various assets, including source code, credentials, and access to sensitive information, such as personally identifiable information (PII), protected health information (PHI), intellectual property (IP), cryptographic materials (e.g., software artifact signing keys), and proprietary information. Companies should identify critical assets and implement controls to protect them from unauthorized access, such as access controls, multi-factor authentication, encryption of data at rest and in transit, and data loss prevention (DLP) measures."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 8)"}, {"role": "assistant", "content": "| MEMORY CONSIDERATIONS ..............................................................................................\n| 5 |\n| 2.3 | IDENTITY MODULE CHARACTERISTICS ............................................................................. | 7 |\n| 2.4 | CELLULAR NETWORK CHARACTERISTICS.......................................................................10 | |\n| 2.5 | OTHER COMMUNICATIONS SYSTEMS | ..............................................................................12 |\n| 3. FORENSIC TOOLS.............................................................................................................15 | 3."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.1 (NIST 3.7.1)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.7.1 Scenario\n\nThe following scenario was simulated to test the architecture's defense against compromised update servers."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.7.1", "cmmc_practice_id": "MA.L2-3.7.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Developing Security Plans for Federal Information Systems provide? (Part 5)"}, {"role": "assistant", "content": "| ...........................................................................................................\n5 |\n| 1.7.4 Senior Agency Information Security Officer (SAISO) .................................................... | 6 |\n| 1.7.5 Information System Security Officer ............................................................................... | 6 |\n| 1.7.6 Authorizing Official | .......................................................................................................... 7 |\n| 1.8 RULES OF BEHAVIOR | ................................................................................................................. 7 |\n| 1.9 SYSTEM SECURITY PLAN APPROVAL ......................................................................................... | 8 |\n| 2. SYSTEM BOUNDARY ANALYSIS AND SECURITY CONTROLS.................................... 9 | 2. SYSTEM BOUNDARY ANALYSIS AND SECURITY CONTROLS.................................... 9 |\n| 2.1 SYSTEM BOUNDARIES................................................................................................................"}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "................................3 | 2. The Fundamentals.....................................................................................................................3 |\n| 3.\nThe Security Requirements........................................................................................................6 | 3. The Security Requirements........................................................................................................6 | 3. The Security Requirements........................................................................................................6 |\n| References.......................................................................................................................................75 | References.......................................................................................................................................75 | References.......................................................................................................................................75 |\n| Appendix A. | Acronyms ................................................................................................................83 | |\n| Appendix B. | Glossary...................................................................................................................85 | |\n| Appendix C."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| |-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | ASSESSMENT OBJECTIVE Determine if: | ASSESSMENT OBJECTIVE Determine if: | | | 3.11.6e[a] | Supply chain risks associated with organizational systems and system components are identified."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\nAdditional information about this publication is available at https://csrc.nist.gov/publications/cswp, including related content, potential updates, and document history."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- A business champion: Someone who is responsible for developing and maintaining the incident response plan.\n- Who to call: List all the individuals who may be part of the incident response efforts. Include their contact information, roles, and responsibilities.\n- What/when/how to report: List the business' communications/reporting responsibilities as required by laws, regulations, contracts, agreements, or policies.\n- Also, most federal contracts will include specific reporting and notification requirements that should be included in the Incident Response Plan\n\nDescription: Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of the systems; and employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.4.4 of [SP800-63])\n\n3."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.4.4", "cmmc_practice_id": "CM.L2-3.4.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8504/final, including related content, potential updates, and document history.\n\nNoSQL databases provide flexible schemas that enable easy database changes and seamless integration with database applications. For example, in document-based systems, documents do not need to follow the same schema, which allows for faster creation and maintenance of documents with minimal overhead.\n\n- Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-162, Includes updates as of August 02, 2019. https://doi.org/10.6028/NIST.SP.800162\n- [WT] WeAreTechies (2022) NoSQL database | key value | document | wide column | graph stores. Available at https://www.youtube.com/watch?v=zG6CHYCx6ag\n- [ZA] Zaki AK (2014) NoSQL Databases: New Millennium Database for Big Data, Big Users, Cloud Computing and its Security Challenges, International Journal of Research in Engineering and Technology 3(3):403-409 (May)."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental\norganizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\nNIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements\nNIST Technical Series Publication Identifier Syntax\n\n\fPublication History\n\nApproved by the NIST Editorial Review Board on 2025-05-30. Supersedes NIST SP 800-63A (June 2017; updated March 2, 2020) https://doi.org/10. 6028/NIST.SP.800-63a\n\nHow to Cite this NIST Technical Series Publication\n\nTemoshok D, Abruzzi C, Choong YY, Fenton JL, Galluzzo R, LaSalle C, Lefkovitz N,\nRegenscheid A, Vachino M (2025) Digital Identity Guidelines: Identity Proofing and\nEnrollment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST\nSpecial Publication (SP) NIST SP 800-63A-4. https://doi.org/10.6028/NIST.SP.800-63A-4\n\nAuthor ORCID iDs\n\nDavid Temoshok: 0000-0001-6195-0331\nChristine Abruzzi: 0000-0001-8904-930X\nYee-Yin Choong: 0000-0002-3889-6047\nJames L. Fenton: 0000-0002-2344-4291\nRyan Galluzzo: 0000-0003-0304-4239\nConnie LaSalle: 0000-0001-6031-7550\nNaomi Lefkovitz: 0000-0003-3777-3106\nAndrew Regenscheid: 0000-0002-3930-527X\nMaria Vachino: 0000-0002-3494-5307\n\nContact Information\n\nmailto:dig-comments@nist.gov\n\nNational Institute of Standards and Technology\nAttn: Applied Cybersecurity Division, Information Technology Laboratory\n100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAdditional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/\nsp/800/63/A/4/final, including related content, potential updates, and document\nhistory. All comments are subject to release under the Freedom of Information Act (FOIA). NIST SP 800-63A-4\nJuly 2025\n\nAbstract\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nThis guideline focuses on identity proofing and enrollment for use in digital\nauthentication."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- The primary function of the first generation of CASBs was the discovery of resources. They provided visibility into all of the cloud resources that the enterprise users accessed, thus preventing or minimizing the chances of shadow IT. Shadow IT is the practice of some users using cloud applications that are not authorized by the enterprise IT management from home or the office using enterprise desktops. An example of this is the use of unapproved software as-a-service (SaaS) applications for file sharing, social media, collaboration, and web conferencing [4]. This generation of CASBs also provides some statistics, such as software-as-a-service (SaaS) utilization. - The current generation of CASBs enforces security and governance policies for cloud applications, thus enabling enterprises to extend their on-premises policies to the cloud. Specific security services provided by CASBs include:\n- o Protection of enterprise data that live in cloud service providers' servers (due to SaaS or IaaS subscriptions), as well as data inflow and data outflow (i.e., Data Loss Prevention [DLP] capabilities) from those servers. - o Tracking of threats, such as account hijacking and other malicious activities, some of which can detect anomalies in users' cloud access behavior (through robust User and Entity Behavior Analytics (UEBA) functionality) and stop insider threats and advanced cyberattacks [5]. - o Detection of misconfigurations in the enterprise's subscribed IaaS and cloud servers. These misconfigurations pose serious security risks, such as data breaches. Alerts generated by CASB due to misconfigurations in the enterprise's IaaS deployments direct the enterprise to follow guidelines, such as the Center for Internet Security's (CIS) benchmarks for public cloud services, thus improving the overall security profile of the enterprise for cloud access [4]."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nThe NIST Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, implementations, proofs of concept, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. Unless specified by legislation, regulation, or government-wide policy, the term system is used in this publication instead of information system . This change reflects a broad-based and holistic definition of systems that includes general-purpose systems, industrial control systems, cyberphysical systems, and individual devices that are part of the Internet of Things. As computing systems and information technologies are deployed ubiquitously worldwide and systems and components are increasingly connected through wired and wireless networks, the susceptibility of Controlled Unclassified Information to loss or compromise grows - as does the potential for adverse consequences resulting from such occurrences. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.12 (NIST 3.2.12)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.12. 3.2.12,\ncryptographic authenticators used at AAL3 are required to provide a hardware-\nprotected, isolated environment to prevent authentication keys from being leaked or\n\n8\n\n\fNIST SP 800-63B-4\nJuly 2025\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nextracted. 3.2.12."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.12", "cmmc_practice_id": "AT.L2-3.2.12", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body ...................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nuld be developed for narrower audiences, such as federal agencies, small businesses, or educational institutions. For more information on CSF 2.0 Community Profiles, see the Framework Resource Center.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------|\n| PR.AA (Identity Management, Authentication, and Access Control) | Access to physical and logical assets is limited to authorized users, services, and hardware and managed commensurate with the assessed risk of unauthorized access | Medium | N1: See the notes for PR. |\n| PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed by the organization | Medium | N1: See the notes for PR. |\n| PR.AA-02 | Identities are proofed and bound to credentials based on the context of interactions | Medium | N1: See the notes for PR."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is NIST SP 800-171 control 3.0.47?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.0.47\n-  PI Processbook 2015 R3 Patch 1 version 3."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.0.47", "cmmc_practice_id": "", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\nink one of the main reasons is this inability to quickly and agilely address vulnerabilities. So that needs to be fixed. They need to find some process.' (C19)\n\n'Now, certification is a problem there.\nIt's the same for medical equipment and for security equipment, that you get your certification and you're not allowed to change it. If you change the product you lose the certification for that product. And so you can have a vulnerability baked into a product and you're not even allowed to fix it because you're not then allowed to use it if it loses its certification. And there was a discussion by ICMC 2016, the International Cryptographic Module Conference, which basically FIPS 140 vendors, and certification houses, and NIST get together. And there was a discussion about this and we had [someone] stand up and say, 'Well, that's not true, the recommendation to the government departments is to put the patch in. If there's a patch and it's a vulnerability, put the patch in.' Then everybody else stood up and said, 'Yeah, but that's all right for you. We're not the government, we lose our certification. What do you think about that?' He didn't respond. And I think that got to the core of frustration in the vendor space with the way that the government does its certifications with respect to how do we address vulnerabilities and updates. A certification probably should be a-- how do I say? A process of state where you get something into this program where it's a certified design, and then the process of rolling out updates is part of the certification. So we might have an update and you have a vulnerability, and we have a change or a bug fix and that would go to NIST, and that would be a fairly lightweight, or the certification house and there would be a fairly lightweight mechanism of getting that checked and stamped"}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nThe information owner is the agency official with statutory or operational authority for specified information and responsibility for establishing the controls for its generation, collection, processing, dissemination, and disposal."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide?"}, {"role": "assistant", "content": "NIST Special Publication\nNIST SP 800-63A-4\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nDavid Temoshok\nChristine Abruzzi\nYee-Yin Choong\nJames L. Fenton\nRyan Galluzzo\nConnie LaSalle\nNaomi Lefkovitz\nAndrew Regenscheid\nMaria Vachino\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-63A-4\n\n\fNIST Special Publication\nNIST SP 800-63A-4\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nDavid Temoshok\nRyan Galluzzo\nConnie LaSalle\nNaomi Lefkovitz *\nApplied Cybersecurity Division\nInformation Technology Laboratory\n\nYee-Yin Choong\nInformation Access Division\nInformation Technology Laboratory\n\nAndrew Regenscheid\nComputer Security Division\nInformation Technology Laboratory\n\nChristine Abruzzi\nCacapon Cyber Solutions\n\nJames L. Fenton\nAltmode Networks\n\nMaria Vachino\nCalvert Consulting LLC\n\n* Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-63A-4\n\nJuly 2025\n\nNational Institute of Standards and Technology\nCraig Burkhardt, Acting Under Secretary for Standards and Technology and Acting NIST Director\n\nU.S. Department of Commerce\nHoward Lutnick, Secretary\n\n\fCertain equipment, instruments, software, or materials, commercial or non-commercial,\nare identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product\nor service by NIST, nor does it imply that the materials or equipment identified are\nnecessarily the best available for the purpose. There may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. Computing devices that integrate physical and/or sensing capabilities and network interface capabilities are being designed, developed, and deployed at an ever-increasing pace. These devices are fulfilling customer needs in all sectors of the economy. Many of these computing devices are connected to the internet. A novel characteristic of these devices is the combination of connectivity and the ability to sense and/or affect the physical world. As devices become smaller and more complex, with an increasing number of features, the security of those devices also becomes more complex. This publication defines a baseline set of device cybersecurity capabilities that organizations should consider when confronting the challenge of the Internet of Things (IoT)."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800\n\n## NIST SP 800-161r1-upd1\n\n## Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations\n\nJon Boyens Angela Smith Nadya Bartol Kris Winkler Alex Holbrook Matthew Fallon\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n\n\n\n## NIST Special Publication 800 NIST SP 800-161r1-upd1\n\n## Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations\n\nJon Boyens Angela Smith Computer Security Division Information Technology Laboratory\n\nNadya Bartol Kris Winkler Alex Holbrook Matthew Fallon Boston Consulting Group\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n\nMay 2022\n\nINCLUDES UPDATES AS OF 1 1 -01 -2024; SEE APPENDIX K\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nLaurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.3.1, 3. 3.3.1 SP800161 : SA-8, SA-15, SR-3 SP800181 : T0414; K0003, K0039, K0044, K0157, K0168, K0177, K0211, K0260, K0261, K0262, K0524; S0010, S0357, S0368; A0033, A0123, A0151 |\n| Define Security Requirements for Software Development (PO. 3.3.1 SP800161 : SA-3 SP800181 : K0233 |\n| Implement Roles and Responsibilities (PO."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n3.3.2 | Team Size ... 3.3.2 Team Size\n\nIn both phases of the research project, we asked several questions to collect data on the number of individuals having security awareness duties within the surveyed organizations."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nBeing proactive means doing more work now to reduce the likelihood of incidents in the future. It also means that if a patch fails, that disruption can be managed and remediated on the organization's schedule. Being reactive means that if a compromise of an unpatched vulnerability occurs (e.g., a data breach, a ransomware infection), the organization will have to perform incident response, their reputation may be damaged, and/or they may potentially be fined or sued. As part of incident response efforts, the missing patch will probably need to be installed anyway in addition to installing all the preceding patches it is dependent upon, as well as performing other prerequisite recovery actions such as reverting to a good known state or rebuilding the environment from scratch. - Emergency patching. This is the procedure to address patching emergencies in a crisis situation, such as a severe vulnerability or a vulnerability being actively exploited. If one or more of the organization's vulnerable assets have already been compromised, emergency patching may be part of incident response efforts. Emergency patching needs to be handled as efficiently as possible to prevent the imminent exploitation of vulnerable assets. - Emergency mitigation. This is the emergency procedure in a crisis situation, like those described above for the emergency patching scenario, to temporarily mitigate vulnerabilities before a patch is available. The mitigation can vary and may or may not need to be rolled back afterward. Emergency mitigations are sometimes needed because of issues with a patch. For example, a patch might be flawed and not actually correct a vulnerability, or a patch might inadvertently disrupt the operation of other software or systems. A patch could even be compromised. - Unpatchable assets. This is the implementation of isolation or other methods to mitigate the risk of systems that cannot be easily patched."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.2.6. 3.2.6."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.2.6", "cmmc_practice_id": "AT.L2-3.2.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\n## 3.1. Measurement of the Expected Proportion of Exploited CVEs\n\n```\nCVE-2023-1730, published 2023-05-02 The SupportCandy WordPress plugin before 3.1.5 does not validate and escape user input before using ... LEV probability: 0.70 Peak EPSS: 0.16, Peak date: 2024-01-27 EPSS scores: 0.00 0.00 0.00 0.05 0.06 0.06 0.06 0.10 0.13 0.16 0.08 0.05 0.05 0.04 0.05 0.05 0.05 0.05 0.05 0.06 EPSS dates: 2023-05-02 2023-06-01 2023-07-01 2023-07-31 2023-08-30 2023-09-29 2023-10-29 2023-11-28 2023-12-28 2024-01-27 2024-02-26 2024-03-27 2024-04-26 2024-05-26 2024-06-25 2024-07-25 2024-08-24 2024-09-23 2024-10-23 2024-11-22 Note: final EPSS score adjusted for window size of 21\n```"}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\ndeciding which practices and tasks to use and how much time and resources to devote to each one. Cost models may need to be updated to effectively consider the costs inherent to AI model development.\nA risk-based approach to secure software development may change over time as an organization responds to new or elevated capabilities and risks associated with an AI model or system. Generative AI and dual-use foundation models present additional challenges in tracking model versioning and lineage. Source code for defining the model architecture and building model binaries is amenable to secure software engineering practices for versioning, lineage, and reproducibility. However, the final model weights are defined only after the model is trained and fine-tuned; this is where limitations in tracking all aspects of collection, processing, and training arise. Organizations should follow secure software development practices for the parts of a model that can be covered fully and strive to introduce secure practices to the extent possible for the stages and corresponding artifacts where obtaining such security guarantees is hard to achieve. Organizations should document the parts and artifacts that are not covered by the secure software development practices. The Profile's practices, tasks, recommendations, and considerations can be integrated into machine learning operations (MLOps) along with other software assets within a continuous integration/continuous delivery (CI/CD) pipeline. organizations. For example, an AI model could be produced by one organization and executed"}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n- Break and Inspect Middlebox : Decrypts, inspects, and re -encrypts traffic to identify threats before the data is transmitted into or out of the network.\n- Real-Time Decryption : Decrypts and forwards traffic with minimal delay to support real -time security needs.\n- Real-Time Analytics : Processes data quickly for immediate threat detection and response, providing insights on network performance and potential anomalies.\n- Post-Facto Decryption and Analytics : Decrypts and stores encrypted data for later analysis, such as forensic investigations, ensuring secure handling and disposal of data.\n- Key Management Agent : Provides a secure interface for provisioning TLS server keys and implementing policies for key activation and expiration.\n-  Key Capture and Registration Agent: Captures the session keys at the time they are generated and registers the session keys with the Key Governance Platform.\n- Enterprise PKI : Manages digital certificates and validates identities, binding them to cryptographic keys for secure communication. The trust anchors for an Enterprise PKI are not expected to be known outside the enterprise.\n- Key Governance : Oversees the lifecycle of certificates and keys, including issuance, renewal, revocation, and secure storage.\n- Key Source : A secure, FIPS 140 -validated component that generates cryptographic keys for use within the TLS 1.3 project."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n'For this relatively newer area, which has to do with the competency of privacy workforce, currently, outside of the International Association for Privacy Professionals, I don't think there exists a good mechanism or assessment for the privacy workforce as of yet. So, for example, we have cybersecurity personnel who may be inheriting privacy responsibilities, but we don't have a tool yet that will help us gauge what their level of knowledge is with regards to privacy.' (S11)\n\n'There was also someone else that came on the team part time…that had the HR experience. So, they were very helpful in helping me to navigate whatever issues that may come from the personnel requirements and so forth.' (N09)\n\n| [BADA] | Bada, M, Sasse, AM, Nurse, JRC (2019) Cyber Security Awareness Campaigns: Why Do They Fail to Change Behaviour? arXiv preprint . https://arxiv.org/ftp/arxiv/papers/1901/1901.02672.pdf |\n|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [FISSEA] | National Institute of Standards and Technology (2021) FISSEA - Federal Information Security Educators . Available at https://csrc.nist.gov/projects/fissea |\n| [INDEED] | Indeed (2021) 15 Professional Skills (Plus Definition and Tips)."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| | 2.2.4 AIS Life Cycle Matrix | 2.2.4 AIS Life Cycle Matrix | 2.2.4 AIS Life Cycle Matrix | 24 | | 2.3 | LIFE CYCLE PHASES | LIFE CYCLE PHASES | LIFE CYCLE PHASES | 26 | | | 2.3.1 Initiation - Phase I | 2.3.1 Initiation - Phase I | 2.3.1 Initiation - Phase I | 27 | | | 2.3.2 Definition - Phase II | 2.3.2 Definition - Phase II | 2.3.2 Definition - Phase II | 27 | | | 2.3.3 System Design - Phase III | 2.3.3 System Design - Phase III | 2.3.3 System Design - Phase III | 27 | | | 2.3.4 Programming and Training - Phase IV | 2.3.4 Programming and Training - Phase IV | 2.3.4 Programming and Training - Phase IV | 28 | | | 2.3.5 Evaluation and Acceptance - Phase V | 2.3.5 Evaluation and Acceptance - Phase V | 2.3.5 Evaluation and Acceptance - Phase V | 28 | | | 2.3.6 Installation and Operation - Phase VI | 2.3.6 Installation and Operation - Phase VI | 2.3.6 Installation and Operation - Phase VI | 29 | | 2.4 | RESPONSIBLE PARTICIPANTS AND THEIR FUNCTION"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Key Activities | Description | Sample Questions | |--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\n----------------|\n| [BXANL] | Bouras MA, Xia B, Abuassba AO, Ning H, Lu Q (2021) IoT-CCAC: A Blockchain-Based Consortium Capability Access Control Approach for IoT. PeerJ Computer Science 7:e455.\nhttps://doi.org/10.7717/peerj-cs.455 |\n| [DMMR] | Di Francesco Maesa D, Mori P, Ricci L (2019) A Blockchain Based Approach for the Definition of Auditable Access Control Systems. Computers &Security 84(July):93-119. https://doi.org/10.1016/j.cose.2019.03.016 |\n| [GBHC] | Ghaffari F, Bertin F, Hatin J, Crespi N (2020) Authentication and Access Control Based on Distributed Ledger Technology: A survey. 2nd conference on Blockchain Research &Applications for Innovative Networks and Services ( BRAINS 2020) (IEEE, Paris), pp 79-86. https://doi.org/10.1109/BRAINS49436.2020.9223297 |\n| [GMS] | Guo H, Meamari E, Shen CC (2019). Multi-Authority Attribute-Based Access Control with Smart Contract. Proceedings of the 2019 International Conference on Blockchain Technology (ICBCT 2019) (ACM, Honolulu, Hawai'i), pp 6-11. https://doi.org/10.1145/3320154.3320164 |\n| [GPR] | Gusmeroli S, Piccione S, Rotondi D (2013) A Capability-Based Security Approach to Manage Access Control in the Internet of Things. Mathematical and Computer Modelling 58(5-6), pp 1189-1205 . https://doi.org/10.1016/j.mcm.2013.02.006 |\n| [GT] | Grant Thornton US (2020) Blockchain and Privacy: How Do You Protect Data That's Distributed?[video]."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nWe asked participants in what ways their organizations try to measure or determine the effectiveness of their security awareness program (Figure 24). Security awareness training completion rates (84%) and phishing simulation click rates (72%) were the most popular measures of effectiveness, followed by program audits/evaluations with 67% of participants. Less than 30% selected attendance at security awareness events, employee surveys, and online views of security awareness materials. Four percent said that they do not attempt to measure program effectiveness.\n\nIn the focus groups and survey, participants provided more details on the variety of methods they employ to determine the effectiveness of their security awareness programs. Training completion rates and independent inspector general (IG) audits were used to demonstrate compliance with security awareness training mandates (usually, FISMA):\n\n'We have found that, yes, management pays attention to things with compliance, but that, in my mind, doesn't really identify effectiveness…We've also really found audits to be effective in helping push the cause. Now, that doesn't identify effectiveness either, but it does help increase management awareness and attention to supporting these programs.' (S11)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nParticipants indicated how often their organization updates security awareness training content, with 80% answering that they update it at least once a year. No participants said they updated content more than every three years, and 4% did not know how often content was updated (see Figure 3).\n\nUpdating required security awareness training content: Updates to required training were viewed as very/moderately challenging by 26% of survey participants.\n\n'More frequent updates to online CBT [computer-based training]. Some courses are dated and 'corny' - this doesn't represent the organization well as some CBT seems a little gimmicky bordering on childish.' (Q38)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.3.2 Resolution\n\nThe build provides several methods for detecting and analyzing this use case."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n| 2.\nScope and Purpose.................................................................................................................. 1 | 2. Scope and Purpose.................................................................................................................. 1 |\n| 3. Definitions, Symbols and Abbreviations............................................................................... 2 | 3. Definitions, Symbols and Abbreviations............................................................................... 2 | 3. Definitions, Symbols and Abbreviations..............................................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n□ Passwords and authentication"}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide? (Part 10)"}, {"role": "assistant", "content": "Speaker Summaries\n\nThe summaries below highlight significant points from the speakers and identifies discussion topics. ## Jack Cyprus and David Keppler, MITRE Corporation, presented ' Building More Secure Devices Using Threat Modeling with MITRE EMB3D '\n\nDavid Keppler and Jack Cyprus, both from the MITRE Corporation, discussed building more secure devices through threat modeling with MITRE EMB3D 1 . They emphasized that threat modeling is crucial for identifying potential vulnerabilities and determining appropriate security measures. This process, which is increasingly used in industries such as industrial automation, automotive, and medical, involves defining the device, identifying key components and trust boundaries, and measuring the return on investment (ROI) of defenses. There are various tools and processes for threat modeling, such as adversary models and attack trees. One prominent model, the MITRE EMB3D, fills gaps in existing data sources and offers a consistent understanding of threats and mitigations. This model categorizes threats based on device properties, such as hardware, system software, application software, and networking. It also includes references to the CWE and CVE databases for additional information and threat details. The EMB3D model provides a common language for device vendors, users, and security researchers to communicate threats and mitigations. It includes three mitigation tiers -foundational, intermediate, and leading -that guide actions throughout a device's lifecycle. These mitigations are grounded in real-world information and provide a defensive starting point as well as steps for ongoing security improvements. By adopting a comprehensive threat modeling process like EMB3D, organizations can better protect their devices against potential threats and build more secure systems."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Blockchain for Access Control Systems provide? (Part 6)"}, {"role": "assistant", "content": "control data/logs and system states to be seen and tracked. - The execution of arbitrary programs in smart contracts allows for controls on distributed access control data and authorization processes.\n- Consensus mechanisms and protocols jointly regulate the participating access control entities/organizations in determining policy rules through blocks or smart contracts."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\n) Access Control Policy Composition for Resource Federation Networks Using Semantic Web and Resource Description Framework (RDF), Proceeding of 2008 International Computer Symposium , pp 497-502 (v1).\nAvailable at https://tsapps.nist.gov/publication/get\\_pdf.cfm?pub\\_id=890067\n- [MO] MongoDB (2023) What is NoSQL? Available at https://www.mongodb.com/nosqlexplained\n- [NISTIR7316] Hu VC, Ferraiolo DF, Kuhn DR (2006) Assessment of Access Control Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 7316. https://doi.org/10.6028/NIST.IR.7316\n- [NO] NoSQL (2020) Your Ultimate Guide to the Non-Relational Universe! Available at https://nextweb.gnoss.com/en/resource/nosql-databases-your-ultimate-guide-to-thenon--/479e0de7-8060-48d1-9670-bbdcd1df0610\n- [OG] Okman L, Gal-Oz N, Gonen Y, Gudes E, Abramov J (2011) Security Issues\\_in\\_NoSQL\\_Databases, International Joint Conference of IEEE TrustCom-11/IEEE ICESS-11/FCST-11 . https://doi.org/10.1109/TrustCom.2011.70\n- [OW] OWASP (2020) Web Security Testing Guide. Available at https://owasp.org/wwwproject-web-security-testing-guide\n- [SF] Sandhu R, Ferraiolo DF, Kuhn D.R (2000) The NIST Model for Role Based Access Control: Toward a Unified Standard, 5th ACM Workshop Role-Based Access Control. pp 47-63. https://doi.org/10.1145/344287.344301"}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 2)"}, {"role": "assistant", "content": "ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 2)"}, {"role": "assistant", "content": "signed statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications.\nThus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment\nperiods and provide feedback to NIST. Many NIST cybersecurity publications, other than\nthe ones noted above, are available at https://csrc.nist.gov/publications. Authority\n\nThis publication has been developed by NIST in accordance with its statutory\nresponsibilities under the Federal Information Security Modernization Act (FISMA)\nof 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible\nfor developing information security standards and guidelines, including minimum\nrequirements for federal information systems, but such standards and guidelines shall\nnot apply to national security systems without the express approval of appropriate\nfederal officials exercising policy authority over such systems. This guideline is consistent\nwith the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines\nmade mandatory and binding on federal agencies by the Secretary of Commerce\nunder statutory authority. Nor should these guidelines be interpreted as altering or\nsuperseding the existing authorities of the Secretary of Commerce, Director of the\nOMB, or any other federal official. This publication may be used by nongovernmental\norganizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nmodify the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Health Information Technology for Economic and Clinical Health (HITECH) Act, or any other federal law or regulation.\nThe participation of other federal organizations with the National Institute of Standards and Technology (NIST) in the development of this Special Publication does not and shall not be deemed to constitute the endorsement, recommendation, or approval by those organizations of its contents. The use of this publication or any other NIST publication does not ensure or guarantee that an organization will be compliant with the Security Rule."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nThe types of software available for mobile device examination include commercial and open source forensic tools, as well as non-forensic tools intended for device management, testing, and diagnostics. Forensic tools are typically designed to acquire data from the internal memory of handsets and UICCs without altering their content and to calculate integrity hashes for the acquired data. Both forensic and non-forensic software tools often use the same protocols and techniques to communicate with a device. However, non-forensic tools may allow unrestricted two-way flow of information and omit data integrity hash functions. Mobile device examiners typically assemble a collection of both forensic and non-forensic tools for their toolkit. The range of devices over which they operate is typically narrowed to: distinct platforms, a specific operating system family or even a single type of hardware architecture. Short product release cycles are the norm for mobile devices, requiring tool manufacturers to continually update their tools providing forensics examiners with an forensic solution. The task is formidable and tool manufacturers' support for newer models may lag significantly behind the introduction of a device into the marketplace. Models of older functioning mobile devices, though out of date, can remain in use for years after their initial release. Mobile device models introduced into one national market may also be used in areas by exchanging the UICC of one cellular carrier with that from another carrier. The current state is likely to continue, keeping the cost of examination significantly higher than if a few standard operating systems and hardware configurations prevailed. JTAG - Many manufacturers support the JTAG standard, which defines a common test interface for processor, memory, and other semiconductor chips."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n| Relevance to NIST SP 800-70 and the National Checklist Program ...........................\n| 2 |\n| | Document Structure.................................................................................................... | 2 |\n| Project Description .......................................................................................................... | Project Description .......................................................................................................... | 3 |\n| | Project Goals.............................................................................................................. | 3 |\n| | mSCP Content Use | ...................................................................................................."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nMalware, also known as malicious code, refers to a program that is covertly inserted into another program with the intent to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Malware is the most common external threat to most hosts, causing widespread damage and disruption and necessitating extensive recovery efforts within most organizations. This publication provides recommendations for improving an organization's malware incident prevention measures. It also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones. Malware, also known as malicious code, refers to a program that is covertly inserted into another program with the intent to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Malware is the most common external threat to most hosts, causing widespread damage and disruption and necessitating extensive recovery efforts within most organizations. Organizations also face similar threats from a few forms of non-malware threats that are often associated with malware. One of these forms that has become commonplace is phishing, which is using deceptive computer-based means to trick individuals into disclosing sensitive information. Organizations should perform threat mitigation to detect and stop malware before it can affect its targets. The most commonly used malware threat mitigation technical control is antivirus software; organizations should deploy antivirus software on all hosts for which satisfactory antivirus software is available."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 2)"}, {"role": "assistant", "content": "lar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-116 Revision 1 Natl. Inst. Stand. Technol. Spec. Publ. 800-116 Revision 1, 71 pages (June 2018) CODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-116r1\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Risk Assessment?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | Documentation : The ability for the manufacturer and/or the manufacturer's supporting entity, to create, gather, and store information relevant to cybersecurity of the IoT device prior to customer purchase, and throughout the development of a device and its subsequent lifecycle."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Personnel Security?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nwas configured for privacy. | Unauthorized Publication of Fitness Tracker Data - Fitness tracker location data for military personnel were publicly posted even when product was configured for privacy.\n|\n| Web application vulnerabilities | Product configuration Cybersecurity State Awareness Documentation Information Dissemination |\n| Mobile application vulnerabilities | Product Configuration Cybersecurity State Awareness Documentation Information Dissemination |\n| Ability for de-identified data to be re-identified | Product Configuration Data Protection Documentation |\n| Unauthorized access to home security camera data - Unauthorized access to data and views of the inside and outside of buildings occurred with multiple brands of security cameras. | Unauthorized access to home security camera data - Unauthorized access to data and views of the inside and outside of buildings occurred with multiple brands of security cameras."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 4)"}, {"role": "assistant", "content": "| ..............................................................................................................\n3 |\n| | Participant and Organization Demographics............................................................... 4 | Participant and Organization Demographics............................................................... 4 |\n| | NIST-Specific Findings ................................................................................................... 6 | NIST-Specific Findings ................................................................................................... 6 |\n| 5.1. Standards ..................................................................................................................... | 5.1. Standards ..................................................................................................................... | 6 |\n| 5.1.1. Benefits.................................................................................................................. | 5.1.1."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.7 (NIST 3.2.7)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.2.7 Access Control | 4-11 |\n| | | | 4-11 |\n| | 4. 3.2.7 Access Control ."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.2.7", "cmmc_practice_id": "AT.L2-3.2.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.4.2, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\nCONCLUSIONS | 6. CONCLUSIONS | 6."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.3.4 Verify Information on Initiation Phase Status | 4. 3.3.4 Verify Information on Initiation Phase Status | 81 |\n| | | 4. 3.3.4."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide?"}, {"role": "assistant", "content": "\n\n## NIST Internal Report NIST IR 8425\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nMichael Fagan Katerina Megas Paul Watrobski Jeffery Marron Barbara Cuthill\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8425\n\n\n\n## NIST Internal Report NIST IR 8425\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nMichael Fagan Katerina N. Megas Paul Watrobski Jeffrey Marron Barbara B. Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8425\n\nSeptember 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "tions in the public and private sectors, both\nnationally and internationally, whose insightful and constructive comments improved the\noverall quality, thoroughness, and usefulness of this publication.\nHISTORICAL CONTRIBUTIONS TO NIST SPECIAL PUBLICATION 800-53\n\nThe authors wanted to acknowledge the many individuals who contributed to previous versions\nof Special Publication 800-53 since its inception in 2005. They include Marshall Abrams, Dennis\nBailey, Lee Badger, Curt Barker, Matthew Barrett, Nadya Bartol, Frank Belz, Paul Bicknell, Deb\nBodeau, Paul Brusil, Brett Burley, Bill Burr, Dawn Cappelli, Roger Caslow, Corinne Castanza, Mike\nCooper, Matt Coose, Dominic Cussatt, George Dinolt, Randy Easter, Kurt Eleam, Denise Farrar,\nDave Ferraiolo, Cita Furlani, Harriett Goldman, Peter Gouldmann, Tim Grance, Jennifer Guild,\nGary Guissanie, Sarbari Gupta, Priscilla Guthrie, Richard Hale, Peggy Himes, Bennett Hodge,\nWilliam Hunteman, Cynthia Irvine, Arnold Johnson, Roger Johnson, Donald Jones, Lisa Kaiser,\nStuart Katzke, Sharon Keller, Tom Kellermann, Cass Kelly, Eustace King, Daniel Klemm, Steve\nLaFountain, Annabelle Lee, Robert Lentz, Steven Lipner, William MacGregor, Thomas Macklin,\nThomas Madden, Robert Martin, Erika McCallister, Tim McChesney, Michael McEvilley, Rosalie\nMcQuaid, Peter Mell, John Mildner, Pam Miller, Sandra Miravalle, Joji Montelibano, Douglas\nMontgomery, George Moore, Rama Moorthy, Mark Morrison, Harvey Newstrom, Sherrill Nicely,\nRobert Niemeyer, LouAnna Notargiacomo, Pat O’Reilly, Tim Polk, Karen Quigg, Steve Quinn,\nMark Riddle, Ed Roback, Cheryl Roby, George Rogers, Scott Rose, Mike Rubin, Karen Scarfone,\nRoger Schell, Jackie Snouffer, Ray Snouffer, Murugiah Souppaya, Gary Stoneburner, Keith\nStouffer, Marianne Swanson, Pat Toth, Glenda Turner, Patrick Viscuso, Joe Weiss, Richard\nWilsher, Mark Wilson, John Woodward, and Carol Woody."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.2.2 | Size of Review Task | Size of Review Task | 49 |\n|-----------|------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------|-----------|\n| 3. 3.2.2 System Initiation Phase Documents | 4. 3.2.2 System Initiation Phase Documents | 79 |\n| | Audit 4."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 3)"}, {"role": "assistant", "content": "lly for organizations and for their vendors. ## Perform these activities to establish your organization's C-SCRM capability:\n\nActivity 1: Create a C-SCRM strategy, objectives, policies, and processes.\n[GV.SC-01]\n\nActivity 2: Identify your organization's technology suppliers and determine how critical each one is to your organization. [GV.SC-04]\n\nActivity 3: Establish C-SCRM roles and requirements and communicate them within and outside your organization. This includes identifying C-SCRM roles and responsibilities [GV.SC- 02] and C-SCRM requirements [GV.SC-05]. ## It is also important to coordinate and harmonize activities between your C-SCRM capability and other internal capabilities. Here are a few examples:\n\n- Integrate C-SCRM into cybersecurity and enterprise risk management, risk assessment, and improvement processes, and monitor the performance of C-SCRM practices throughout the technology lifecycle. [GV.SC-03, GV.SC-09] See the Enterprise Risk Management Quick-Start Guide for more information on C-SCRM integration. - Include your relevant suppliers in cybersecurity incident planning, response, and recovery activities. [GV.SC-08] See NIST's Computer Security Incident Handling Guide for more information on key practices for cybersecurity incidents. ## Checklist of actions for Activity 1: Create a C-SCRM strategy, objectives, policies, and processes. - ☐ Establish a C-SCRM strategy that lays out the objectives of the capability. - ☐ Develop a C-SCRM plan (with milestones) and C-SCRM policies and procedures that guide implementation and improvement of the plan and the capability; socialize those policies and procedures with organizational stakeholders. - ☐ Develop and implement C-SCRM processes based on the strategy, objectives, policies, and procedures that are agreed upon and performed by the organizational stakeholders."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nNon-technical supporting capabilities are actions a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nSWID tags support the identification of installed patches, extensible metadata attributes, and software integrity measurement data not supported by CPE. Through these additional capabilities, SWID tags can support more comprehensive software inventory (including patch details), tamper detection, and application whitelisting. Through the fine-grained identification of software products and patches using SWID tags, improved automation of vulnerability and configuration management is possible in SCAP v2. NIST Internal Report (NISTIR) 8060 [5], provides details on the SWID tag format and discussion of the SWID tag operational model, which is intended to be used as part of SCAP v2."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 5)"}, {"role": "assistant", "content": "l Institute of Standards and Technology would also like to express its appreciation and thanks to the Department of Homeland Security for its sponsorship and support of NIST Special Publication 80083.\n## Trademark Information\n\nAll product names are registered trademarks or trademarks of their respective companies. ## Table of Contents\n\n| Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | |\n|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ...................................................................................................................... | 1."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 4)"}, {"role": "assistant", "content": "facturing\n\n## Acknowledgements\n\nThe editor would like to thank Suzanne Lightman, Kevin Stine (both NIST), and Mark Enstrom (Neustar) for being reviewers for this document. ## Table of Contents\n\n| 1.\n| Introduction ..............................................................................................................................1 |\n|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | Opening Remarks .....................................................................................................................2 |\n| 3 | Implantable Medical Devices - Cyber Risks and Mitigation Approaches...............................9 |\n| 4 | Safety-Critical Automotive and Industrial Data Security......................................................25 |\n| 5 | Keynote Speaker: Dr."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n3.1.1 | Security Awareness Role... 3.1.1 Security Awareness Role\n\n## Focus Groups\n\nFigure 1 shows the distribution of focus group participants' roles with respect to their organizations' security awareness program."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide?"}, {"role": "assistant", "content": "## Summary of NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations\n\nKelley Dempsey Computer Security Division Information Technology Laboratory\n\nGreg Witte Doug Rike G2, Inc. Annapolis Junction, MD\n\nFebruary 19, 2014\n\n\n\n## Abstract\n\nThis 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\n\nassurance; computer security; FIPS Publication 199; FIPS Publication 200, FISMA; Privacy Act; Risk Management Framework; security controls; security requirements\n\n## Disclaimer\n\nAny 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\n\nFor 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/223/final, including related content, potential updates, and document history.\n\noptimize network performance. The popular HPC interconnect networking includes InfiniBand [2], Omni-Path [3], Slingshot [4], Ethernet, and others. A high-performance computing zone typically utilizes non-high-performance communication networks, like ethernet, as cluster internal networks that connect the high-performance computing zone with the management zone and access zone for traffic associated with maintenance activities as opposed to HPC traffic.\n\nBoth GPFS and Lustre-based PFSs are prone to performance degradation when a certain capacity threshold is reached. These file systems may be regularly pruned of unwanted files with a strategy decided by the file system administrators. Some deployments will delete files older than a certain age, which forces HPC users to transfer job output to a longer-term file system, such as campaign storage. PFSs tends to be somewhat unreliable, depending on the types of activities being performed by running jobs and users. Because these are distributed file systems, file-system software must solve distributed locking of files to ensure deterministic file updates when multiple clients are writing to the same file at once. Additionally, PFSs are susceptible to denial-of-service conditions even during legitimate user operations, such as listing a directory with millions of files or applications that perform poor file locking semantics."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\nCombinatorial testing with constraints on the order in which values and combinations are applied in tests was analyzed extensively in [5] . Extended covering arrays that consider the sequence of values in each test were defined in [6] . Combination sequences were studied in [20] , combining configuration and the order of combinations while also considering constraints. Another structure defined as a sequence covering array of t -way combinations has been termed a multi-valued sequence covering array, introduced in [25] . - [20] James M. Higdon, Gerald Oveson, Efficient Test of Configurations and Orders of Complex Operating Procedures Tech. Rpt., COLSA North Florida Ops, 96th Cyberspace Test Group, AFMC, Eglin AFB, FL, 4 Apr 2018. - [21] Duan F, Lei Y, Kacker RN, Kuhn DR. An Approach to T-Way Test Sequence Generation With Constraints. 2019 IEEE Intl Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2019 Apr 22 (pp. 241-250). IEEE. - [22] Garn B, Simos DE, Duan F, Lei Y, Bozic J, Wotawa F. Weighted Combinatorial Sequence Testing for the TLS Protocol. In2019 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2019 Apr 22 (pp. 46-51). IEEE. - [23] Oetsch J, Nieves JC. Stable-Ordered Models for Propositional Theories with Order Operators. InEuropean Conference on Logics in Artificial Intelligence 2019 May 7 (pp. 794-802). Springer, Cham. - [24] Yuster R. Perfect sequence covering arrays. Designs, Codes and Cryptography. 2020 Mar;88(3):585-93. - [25] Younis MI. MVSCA: Multi-Valued Sequence Covering Array. Journal of Engineering. 2019 Oct 29;25(11):8291. - [26] D.R. Kuhn, I. Dominguez, R.N. Kacker and Y. Lei. \"Combinatorial Coverage Measurement Concepts and Applications\", 2nd Intl Workshop on Combinatorial Testing , Luxembourg, IWCT2013, IEEE, Mar. 2013. - [27] Zamli KZ, Othman RR, Zabil MH. On sequence based interaction testing."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\ning the non-technical support capability. - The last column lists IoT reference examples that indicate existing sources of IoT device cybersecurity guidance specifying a similar or related capability.\nBecause the table only covers the basics of the capabilities, the references can be invaluable for understanding each capability in more detail and learning how to implement each capability in a reasonable manner. The following are the references used in Table 1:\n- o AGELIGHT : AgeLight Digital Trust Advisory Group, 'IoT Safety Architecture & Risk Toolkit v4.0' [7]\n- o CTA : Consumer Technology Association, 'American National Standards Institute (ANSI)/CTA Standard - Baseline Cybersecurity Standard for Devices and Device Systems: ANSI/CTA-2088' [8]\n- o CSDE : Council to Secure the Digital Economy (CSDE), 'The C2 Consensus on IoT Device Security Baseline Capabilities' [9]\n- o ETSI : European Telecommunications Standards Institute, 'Cyber Security for Consumer Internet of Things: Baseline Requirements v2.1.0' [10]\n- o IoTSF : IoT Security Foundation (IoTSF), 'IoT Security Compliance Framework v2.1' [11]"}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\n\nThe purpose of this publication is to provide procedures for assessing the security requirements in NIST Special Publication (SP) 800-171, Protecting Controlled Unclassified Information (CUI) in Nonfederal Systems and Organizations [3]. Organizations can use the assessment procedures to generate evidence that the security requirements have been satisfied. The scope of the security assessments conducted using the procedures described in this publication is guided and informed by the system security plans for systems that process, store, or transmit CUI. The assessment procedures offer the flexibility to customize assessments based on organizational policies and requirements, known threat and vulnerability information, system and platform dependencies, operational considerations, and tolerance for risk."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nlogical store (e.g., a\n\nfile system partition). Level 3, Hex Dumping/JTAG Extraction methods, entail performing a 'physical acquisition' of mobile device memory in situ and require advanced training.\nLevel 4 Chip-Off methods involve the physical removal of memory from a mobile device to extract data, requiring extensive training in electronic engineering and file system forensics. Level 5, Micro Read methods involve the use of a high-powered microscope to view the physical state of gates. Level 5 methods are the most invasive, sophisticated, technical, expensive, and time consuming of all the methodologies."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.4.3. 3.4.3 provides more detail about integrating MFA with VPN services. 3.4.3 discusses implementing MFA with VPNs."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\nion level)\n- Retention back-up and destruction\n- Usage logs\n- Cleaning of media\n- Storage and custody of supplies and media, and\n- Disposal of sensitive media remnants. - 3.2.4 Machine Uti 1 ization .\nTo detect excessive rerun time, excessive machine down-time, unsatisfactory throughput times and/or excessive user charges, appropriate policies should be established regarding:\n- Regular production of pertinent utilization statistics. - Approval of job classifications and priorities, and\n- Machine scheduling\n- 3.2.5 Output Handling . To ensure the detection of processing errors in the output and to prevent output from being distributed inappropriately, appropriate policies should be established regarding:\n- The identification of all printed and other output\n- The quality control procedures over output for detection of errors and/or unacceptable conditions\n- Standard procedures for the physical handling (decollating, binding, etc.) and delivery of output and the disposal of remnants (e.g., extraneous copies, carbon)\n- Standard procedures and assigned accountability for handling of negotiable instruments (e.g., signed checks, purchase orders)\n- 3.2.6 Environment Control . To prevent intentional and/or unintentional damage by human attack or natural phenomena, appropriate policies designed to maintain an appropriate physical environment for the equipment, media, and personnel should be established regarding:\n- The use and testing of protective devices (e.g., smoke alarms) and procedures (e.g., guards), and\n- Installation housekeeping procedures. - 3.2.7 Access Control . To prevent unauthorized disclosure, retrieval, or modification of data or programs, appropriate policies should be established regarding:\n- Restriction of physical access to the particular equipment, media, and premises to authorized personnel only."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\n- Policy Engine (PE): The 'brain' of a ZTA implementation and the components that ultimately evaluate resource access requests. The PE relies on information from the various data sources (access logs, threat intelligence, endpoint health, and network ID authentication, etc.)\n- Policy Administrator (PA): The executor function of the PE. The PA's role is to establish, maintain and ultimately terminate sessions 1 in the data plane between the subject and the resource. The PA, PE and PEP communicate on a logically (or physically) separate set of channels called the control plane. The control plane is used to establish and configure the data plane channels used to send application traffic. - Policy Enforcement Point (PEP): The component that applications, endpoints, etc. will interact with to be granted access permission to a resource. The PEP is responsible for gathering information for the PE and following the instructions issued by the PA to establish and terminate communication sessions. All data plane communications between enterprise resources must be managed by a PEP. - Information feeds (left and right ): Sometimes called policy information points (PIPs). These are not 'core' functional ZTA components themselves but used to support the PE. These feeds include the set of codified policies, identity and endpoint attributes, environmental factors and historical data used by the PE to generate resource access decisions. - I. All data sources and computing services are considered resources. An enterprise relies on different resources to perform its mission: mobile devices, data stores, compute resources (including virtual), remote sensors/actuators, etc. All these components are resources and need to be considered in a ZTA. Some components (e.g., IoT sensors) may not be able to support some solutions such as configuration agents, application sandboxing, etc. so compensating technologies or alternative mitigations may be needed."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n## NISTIR 8259B\n\n## IoT Non-Technical Supporting Capability Core Baseline\n\nMichael Fagan Jeffrey Marron Kevin G. Brady, Jr. Barbara B. Cuthill Katerina N. Megas Rebecca Herold\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8259B\n\n\n\n## NISTIR 8259B\n\n## Internet of Things Non-Technical Supporting Capability Core Baseline\n\nMichael Fagan Jeffrey Marron Kevin G. Brady, Jr. Barbara B. Cuthill Katerina N. Megas\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nRebecca Herold\n\nThe Privacy Professor\n\nDes Moines, IA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259B\n\nAugust 2021\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259B 21 pages (August 2021)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259B\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| | | | 6-4 | |---------------|--------------------------------------------------------|---------------------------------------------------------------------------------|-----------| | 2.3 | Quantity of Terminals | Quantity of Terminals | 6-4 | | 2.4 | Terminal Characteristics | Terminal Characteristics | 6-4 | | | 2.4.1 | Portability | 6-4 6-4 | | | 2.4.2 | Bandwidth | 6-4 | | | 2.4.3 | Storage | 6-4 | | | 2.4.4 | Value | 6-4 | | | 2.4.5 | Construction, Modularity and Assembly | 6-5 | | | 2.4.6 | Intelligence | 6-5 | | | 2.4.7 | Emanations | 6-5 | | | 2.4.8 | Media | 6-5 | | 3."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.01.06.ODP[01]: personnel or roles to which privileged accounts on the system are to be restricted are defined .\n\nA.03.01.06.a: privileged accounts on the system are restricted to <A.03.01.06.ODP[01]: personnel or roles> ."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n5.3.\nSession monitoring (sometimes called continuous authentication) is the ongoing\nevaluation of session characteristics to detect possible fraud during a session. Session\nmonitoring MAY be performed by the RP in coordination with the CSP or IdP and\nassociated verifier as a risk reduction measure. When potential fraud is detected\nduring a session, the RP SHOULD act in conjunction with the CSP, IdP, or verifier to\nreauthenticate, terminate the session, or notify appropriate support personnel. Session\ncharacteristics that MAY be evaluated include:\n\nInsider Threats"}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\n| 1. Introduction...................................................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Workshop Sessions ........................................................................................................................3 |\n| 2.1.1. Speaker Viewpoints......................................................................................................................3 |\n| 2.1.2. Key Highlights ...............................................................................................................................4 |\n| 2.2.1. Speaker Viewpoints......................................................................................................................5 |\n| 2.2.2. Key Highlights ...............................................................................................................................6 |\n| 2.3.1. Speaker Viewpoints......................................................................................................................6 |\n| 2.3.2. Key Highlights ...............................................................................................................................8 |\n| 2.4.1. Speaker Viewpoints......................................................................................................................9 |\n| 2.4.2. Key Highlights .............................................................................................................................11 |\n| 2.5.1. Speaker Viewpoints....................................................................................................................11 |\n| 2.5.2."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 2)"}, {"role": "assistant", "content": "signed statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-03-05\n\n## How to cite this NIST Technical Series Publication:\n\nAlagic G, Bros M, Ciadoux P, Cooper D, Dang Q, Dang T, Kelsey J, Lichtinger J, Liu YK, Miller C, Moody D, Peralta R, Perlner R, Robinson A, Silberg H, Smith-Tone D, Waller N (2025) Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Internal Report (IR) NIST IR 8545."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 6)"}, {"role": "assistant", "content": "ates, and upgrades throughout an organization. In past perimeter-based security architectures, most software was operated on internal networks protected by several layers of network security controls.\nWhile patching was generally considered important for reducing the likelihood of compromise and was a common compliance requirement, patching was not always considered a priority. In today's environments, patching has become more important, often rising to the level of mission criticality. As part of a zero trust approach to security, it is now recognized that the perimeter largely does not exist anymore, and most technologies are directly exposed to the internet, putting systems at significantly greater risk of compromise. This dynamic applies across all computing technologies, whether they are information technology (IT), operational technology (OT), Internet of Things (IoT), mobile, cloud, virtual machine, container, or other types of assets. Zero trust architectures emphasize business asset-specific security over just protecting a network with assets on it, so patching is vital for reducing risk to those individual assets and determining the assets' trust status. There is often a divide between business/mission owners and security/technology management. Business/mission owners may believe that patching negatively affects productivity, since it requires scheduled downtime for maintenance and introduces the risk of additional downtime if something goes wrong and disrupts operations. Leadership and business/mission owners should reconsider the priority of enterprise patch management in light of today's risks. Patching should be considered a standard cost of doing business and should be rigorously followed and tracked. Just as preventive maintenance on corporate fleet vehicles can help avoid costly breakdowns, patching should be viewed as a normal and necessary part of reliably achieving the organization's missions."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof-of-concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Standard | Sections | Implementation Specifications (R) = Required, (A) = Addressable | |---------------------------------|---------------|-----------------------------------------------------------------------| | | | Emergency Access Procedure (R) | | | | Automatic Logoff (A) | | | | Encryption and Decryption (A) | | Audit Controls | 164.312(b) | (R) | | Integrity | 164.312(c)(1) | Mechanism to Authenticate Electronic Protected Health Information (A) | | Person or Entity Authentication | 164.312(d) | (R) | | Transmission Security | 164.312(e)(1) | Integrity Controls (A) | | Transmission Security | 164.312(e)(1) | Encryption (A) | | Key Activities | Description | Sample Questions | |--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nadministrative safeguards; Health Insurance Portability and Accountability Act; implementation specification; physical safeguards; risk assessment; risk management; Security Rule; standards; technical safeguards.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n\nThe terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical, or causal."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 8)"}, {"role": "assistant", "content": "| Understanding Malware Threats ..................................................................................... | Understanding Malware Threats ....................................................................................."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n- Applying a threat-centric approach to security requirements specification;\n- Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16\n- Implementing dual authorization controls for the most critical or sensitive operations;\n- Limiting persistent storage to isolated enclaves or domains;\n- Implementing a comply-to-connect approach for systems and networks;\n- Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components;\n- Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components;\n- Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and\n- Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n............................................................................... | Executive Summary.....................................................................................................\n| iv |\n|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|\n| 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | |\n| | 1.1 | Purpose and Scope ........................................................................................"}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| Component | Product/Technology | Function/Capability | Cybersecurity Framework Subcategories | |------------------------------------------------|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| | Configuration Management System | Microsoft Configuration Manager | Enforces corporate governance and policies through actions such as applying software patches and updates, removing denylisted software, and automatically updating configurations | DE.CM-7 | | Security Information and Event Management Tool | IBM QRadar | Performs real-time analysis of alerts and notifications generated by organizational information systems | DE.CM-7 | | Certificate Authority (CA) | Host Integrity at Runtime and Start-up (HIRS) Attestation Certificate Authority (ACA) | Issues an Attestation Identity Credential in accordance with Trusted Computing Group (TCG) specifications | PR.AC-6, PR.DS-8 | | Platform Integrity Validation System | Eclypsium Analytic Platform | Validates the integrity of firmware installed on computing devices | PR.DS-6 | | Platform Integrity Validation System | HIRS ACA | Validates platform components in accordance with TCG specifications | PR.DS-8 | | Platform Integrity Validation System | Platform Certificate Verification Tool (PCVT) | Validates platform components in accordance with TCG specifications | PR.DS-8 | | Platform Integrity Validation System | Secure Component Verification (SCV) | Validates platform components in accordance with TCG specifications | PR.DS-8 | | Platform Integrity Validation System | Platform Manifest"}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 10)"}, {"role": "assistant", "content": "| Government Advisory Services ...............................................................................13 | | | Stakeholders | in Federal Vulnerability Disclosure Coordination ..................................14 | | | Technical Approaches | and Resources ......................................................................14 | | | Vulnerability Disclosure Program Offices .....................................................................16 | Vulnerability Disclosure Program Offices .....................................................................16 | | | | Disclosure Program Office Structural Requirements..............................16 | | | Vulnerability Development | Vulnerability Development | | | 3.2.1."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nInformation technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .\nISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\nmultitude of errors and developer pitfalls in the cryptographic implementations of software products [1-5]. However, these studies focused on the practices of less-experienced, individual developers.\nTherefore, there was little understanding of the cryptographic development practices of organizations, including the benefits and challenges of using cryptographic resources such as standards specifications and libraries."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\n- Endpoint: An Endpoint is the target of a posture assessment. Collection applications will collect software inventory, configuration settings, and other endpoint posture and publish this posture to Posture Collection Servers using standardized protocols and interfaces. These standards will enable Endpoints to be monitored and for changes in posture to be reported automatically. These standards will also allow Posture Collection Servers to query an Endpoint's posture when new or refreshed posture information is required. The initial release of SCAP 2.0 will define protocol requirements for desktops, laptops, and servers; however, all endpoint types are in scope for SCAP v2. Later revisions will define requirements for other endpoint types (e.g., network devices, mobile devices, IoT devices). - Posture Collection Server: This server is responsible for efficiently coordinating the collection of posture from multiple Endpoints. Posture collected from an Endpoint will be published by the Posture Collection Server to the Configuration Management Database (CMDB) where it can then be accessed by other tools. This reduces duplicate posture collection and load on Endpoints that have constrained capabilities, that are under significant load, or that have strict performance requirements. The Posture Collection Server acts as a point of integration for access control and for standardized management protocols including Network Endpoint Assessment (NEA), the Simple Network Management Protocol (SNMP), the Network Configuration Protocol (NETCONF), and mobile device management (MDM) protocols. - Posture Evaluator: By decoupling collection and evaluation and creating standardized interfaces, SCAP v2 enables the distribution of Posture Evaluator service instances across the network. A Posture Evaluator retrieves previously collected posture from a CMDB and requests new posture collection from Posture Collection Servers."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\n- [20] James M. Higdon, Gerald Oveson, Efficient Test of Configurations and Orders of Complex Operating Procedures Tech. Rpt., COLSA North Florida Ops, 96th Cyberspace Test Group, AFMC, Eglin AFB, FL, 4 Apr 2018. - [21] Duan F, Lei Y, Kacker RN, Kuhn DR. An Approach to T-Way Test Sequence Generation With Constraints. 2019 IEEE Intl Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2019 Apr 22 (pp. 241-250). IEEE. - [22] Garn B, Simos DE, Duan F, Lei Y, Bozic J, Wotawa F. Weighted Combinatorial Sequence Testing for the TLS Protocol. In2019 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2019 Apr 22 (pp. 46-51). IEEE. - [23] Oetsch J, Nieves JC. Stable-Ordered Models for Propositional Theories with Order Operators. InEuropean Conference on Logics in Artificial Intelligence 2019 May 7 (pp. 794-802). Springer, Cham. - [24] Yuster R. Perfect sequence covering arrays. Designs, Codes and Cryptography. 2020 Mar;88(3):585-93. - [25] Younis MI. MVSCA: Multi-Valued Sequence Covering Array. Journal of Engineering. 2019 Oct 29;25(11):8291. - [26] D.R. Kuhn, I. Dominguez, R.N. Kacker and Y. Lei. \"Combinatorial Coverage Measurement Concepts and Applications\", 2nd Intl Workshop on Combinatorial Testing , Luxembourg, IWCT2013, IEEE, Mar. 2013. - [27] Zamli KZ, Othman RR, Zabil MH. On sequence based interaction testing. In2011 IEEE Symposium on Computers & Informatics 2011 Mar 20 (pp. 662-667). IEEE. - [28] Kuhn DR, Higdon JM, Lawrence JF, Kacker RN, Lei Y. Efficient methods for interoperability testing using event sequences. FLIGHT TEST SQUADRON (46TH) EGLIN AFB FL; 2012 Aug 1. - [29] Yilmaz C, Fouche S, Cohen MB, Porter A, Demiroz G, Koc U. Moving forward 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."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| VULNERABILITIES | VULNERABILITIES | 6-5 | | 3.1 | Targets | Targets | 6-5 | | | 3.1.1 | Vul nerabl llties of Data and Prog ranis •••••••••••«••«•••••••«••••••••• | 6~5 | | | | Vulnerabilities of Terminals | 6-7 | | | 3.1.2 3.1.3 | Vulnerabilities of Media | 6-7 | | | 3.1.4 | Vulnerability of Services | 6-9 | | 3.2 | Hazards | | 6-10 | | | 3.2.1 | Natural Hazards | 6-10 | | | 3.2.2 Man-made Hazards | 3.2.2 Man-made Hazards | 6-10 | | 4.1 | CONTROLS Control Principles | CONTROLS Control Principles | 6-11 | | | | | 6-11 | | | 4.1.1 | Separation of Duties | | | | 4.1.2 | Restrict Access | 6-12 | | | 4.1.3 | Independent Authorization | 6-12 | | | 4.1.4 | Individual Accountability | 6-12 | | | 4.1.5 | Test of Concealment | 6-12 6-12 | | | 4.1.6 Test of Sensitive Combinations | 4.1.6 Test of Sensitive Combinations | 6-12 | | 4.2 | Control Measures | Control Measures | 6-12 | | | 4.2.1 | Explicit Assignment of Responsibility 4.2.2 Physical and Environmental Controls | 6-13 |"}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST 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.\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology.\nITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems. The Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations.\n\nThese guidelines address logical access to online systems, services, and applications.\nThey do not specifically address physical access control processes. However, the\nprocesses specified in these guidelines can be applied to physical access use cases where\nappropriate. Additionally, these guidelines do not explicitly address some subjects\nincluding, but not limited to, machine-to-machine authentication, interconnected\ndevices (e.g., Internet of Things [IoT] devices), or access to Application Programming\nInterfaces (APIs) on behalf of subjects.\n\nwhether material, physical, or causal — or, in the negative, the absence of\nthat possibility or capability."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 5)"}, {"role": "assistant", "content": "----------------------------------------|\n| 1. Introduction...................................................................................................................................3 |\n| 2.\nAn Overview of MFA Technologies and Concepts ............................................................................5 |\n| 2.4.1. Benefits of Identity Federation ....................................................................................................7 |\n| 2.4.2. Benefits of Single Sign-On ............................................................................................................8 |\n| 3. Choosing an MFA Implementation for Protecting CJI .....................................................................11 |\n| 3.1.1. Principle 1: Authenticator Reusability........................................................................................12 |\n| 3.1.2. Principle 2: Authenticator Optionality .......................................................................................12 |\n| 3.1.3. Principle 3: Minimize the Passing of Memorized Secrets ..........................................................12 |\n| 3.1.4. Principle 4: Ensure MFA Is Integrated to Protect CJI..................................................................13 |\n| 3.2.1. MFA Users ..................................................................................................................................13 |\n| 3.2.2. IT Support Staff...........................................................................................................................14 |\n| 3.2.3. Other Agencies ...........................................................................................................................14 |\n| 3.2.4."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nel producers, AI system producers, AI system acquirers, and others can use the SSDF to foster their communications regarding secure AI model development throughout the software development life cycle.\n2 Following SSDF practices should help AI model producers reduce the number of vulnerabilities in their AI models, reduce the potential impacts of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of vulnerabilities to prevent recurrences. AI system producers can use the SSDF's common vocabulary when communicating with AI model producers regarding their security practices for AI model development and when integrating AI models into the software they are developing. AI system acquirers can also use SSDF terms to better communicate their cybersecurity requirements and needs to AI model producers and AI system producers, such as during acquisition processes. The SSDF Community Profile is not a checklist to follow, but rather a starting point for planning and implementing a risk-based approach to adopting secure software development practices involving AI models. The contents of the Profile are meant to be adapted and customized, as not all practices and tasks are applicable to all use cases. Organizations should adopt a riskbased approach to determine what practices and tasks are relevant, appropriate, and effective to mitigate the threats to software development practices from the organization's perspective as an AI model producer, AI system producer, or AI system acquirer. Factors such as risk, cost, feasibility, and applicability should be considered when deciding which practices and tasks to use and how much time and resources to devote to each one. Cost models may need to be updated to effectively consider the costs inherent to AI model development."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 7)"}, {"role": "assistant", "content": "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.\nThe 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. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## THE APPLICABILITY OF ENHANCED SECURITY REQUIREMENTS\n\nThe 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\ncurity officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control.\n- To provide closer linkage and communication between the risk management processes and activities at the C-suite or governance level of the organization and the individuals, processes, and activities at the system and operational level of the organization;\n- To institutionalize critical risk management preparatory activities at all risk management levels to facilitate a more effective, efficient, and cost-effective execution of the RMF;\n- To demonstrate how the NIST Cybersecurity Framework [NIST CSF] can be aligned with the RMF and implemented using established NIST risk management processes;\n- To integrate privacy risk management processes into the RMF to better support the privacy protection needs for which privacy programs are responsible;\n- To promote the development of trustworthy secure software and systems by aligning life cycle-based systems engineering processes in NIST Special Publication 800-160, Volume 1 [SP 800-160 v1], with the relevant tasks in the RMF;\n- To integrate security-related, supply chain risk management (SCRM) concepts into the RMF to address untrustworthy suppliers, insertion of counterfeits, tampering, unauthorized production, theft, insertion of malicious code, and poor manufacturing and development practices throughout the SDLC; and\n- To allow for an organization-generated control selection approach to complement the traditional baseline control selection approach and support the use of the consolidated control catalog in NIST Special Publication 800-53, Revision 5."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n…an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 5)"}, {"role": "assistant", "content": "........................................................ | 2 |\n| 2.\n| Fundamental Theories ..................................................................................................... | 4 |\n| 2.1. | Elliptic Curve | .............................................................................................................. 4 |\n| 2.2. | Elliptic-Curve Cryptography ........................................................................................ | 5 |\n| 2.3. | Bilinear Pair Mapping.................................................................................................. | 7 |\n| 2.4. | Bilinear Pairing for Cryptography................................................................................ | 9 |\n| 3. | Identity-Based Encryption ..............................................................................................11 | |\n| 4."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 7)"}, {"role": "assistant", "content": "hrough this collaboration, the NCCoE develops modular, adaptable example cybersecurity solutions demonstrating how to apply standards and best practices using commercially available technology.\n## LEARN MORE\n\nVisit https://www.nccoe.nist.gov nccoe@nist.gov 301-975-0200\n\n## NIST SPECIAL PUBLICATION 1800-26B\n\n## Detecting and Responding to Ransomware and Other\n\n## Data Integrity: Destructive Events\n\n## Volume B:\n\nApproach, Architecture, and Security Characteristics\n\n## Jennifer Cawthra\n\nNational Cybersecurity Center of Excellence NIST\n\nMichael Ekstrom Lauren Lusty Julian Sexton John Sweetnam\n\nThe MITRE Corporation McLean, Virginia\n\n## December 2020\n\nFINAL\n\nThis publications is available free of charge from https://doi.org/10.6028/NIST.SP.1800-26. This publication is available free of charge from https://www.nccoe.nist.gov/projects/building-blocks/data-integrity/detect-respond. \n\n## DISCLAIMER\n\nCertain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. National Institute of Standards and Technology Special Publication 1800-26B, Natl. Inst. Stand. Technol. Spec. Publ. 1800-26B, 54 pages, (December 2020), CODEN: NSPUE2\n\n## FEEDBACK\n\nAs a private-public partnership, we are always seeking feedback on our practice guides. We are particularly interested in seeing how businesses apply NCCoE reference designs in the real world. If you have implemented the reference design, or have questions about applying it in your environment, please email us ds-nccoe@nist.gov."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8.\nEvaluation (§ 164.308(a)(8)).......................................................................................................51 |\n| 5.2.1. Facility Access Controls (§ 164.310(a)).......................................................................................56 |\n| 5.1.9. Business Associate Contracts and Other Arrangements (§ 164.308(b)(1))................................54 |\n| 5.2.2. Workstation Use (§ 164.310(b)).................................................................................................59 |\n| 5.2.3. Workstation Security (§ 164.310(c)) ..........................................................................................61 |"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.2.1. 3.2.1."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................3 |\n| 2. An Overview of MFA Technologies and Concepts ............................................................................5 |\n| 2.4.1. Benefits of Identity Federation ....................................................................................................7 |\n| 2.4.2. Benefits of Single Sign-On ............................................................................................................8 |\n| 3. Choosing an MFA Implementation for Protecting CJI .....................................................................11 |\n| 3.1.1. Principle 1: Authenticator Reusability........................................................................................12 |\n| 3.1.2. Principle 2: Authenticator Optionality .......................................................................................12 |\n| 3.1.3. Principle 3: Minimize the Passing of Memorized Secrets ..........................................................12 |\n| 3.1.4. Principle 4: Ensure MFA Is Integrated to Protect CJI..................................................................13 |\n| 3.2.1. MFA Users ..................................................................................................................................13 |\n| 3.2.2."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nces; monitors activity down to the keystroke |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities.\n|\n| | Provides host-based application allowlisting (the blocking of unauthorized activities that have the potential to pose a harmful attack) and file integrity monitoring. |"}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\n- create the IoT product (i.e., used to create each product component). - ii. IoT platform used in the development and operation of the IoT product, its product components, including related documentation. - iii. Trustworthiness and protection of software and hardware elements implemented to create the IoT product and its product components (e.g., secure boot, hardware root of trust, and secure enclave). - iv. Consideration for the known risks related to the IoT product and known potential misuses. - v. Secure software development and supply chain practices used. - vi. Accreditation, certification, and/or evaluation results for cybersecurity-related practices. - vii. The ease of installation and maintenance of the IoT product by a customer (i.e., the usability of the product [ISO9241]). - e. Maintenance requirements for the IoT product, for example :\n- i. Cybersecurity maintenance expectations and associated instructions or procedures (e.g., vulnerability/patch management plan). - ii. How the IoT product developer identifies authorized supporting parties who can perform maintenance activities (e.g., authorized repair centers). - iii. Cybersecurity considerations of the maintenance process (e.g., how customer data unrelated to the maintenance process remain confidential even from maintainers). - f. The secure system lifecycle policies and processes associated with the IoT product, including:\n- i. Steps taken during development to ensure the IoT product and its product components are free of any known, exploitable vulnerabilities. - ii. The process of working with component suppliers and third-party vendors to ensure the security of the IoT product and its product components is maintained for the duration of its supported lifecycle. - iii. Any post end-of-support considerations, such as the discovery of a vulnerability that would significantly impact the security, privacy, or safety of customers who continue to use the IoT product and its product components. - g."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide? (Part 6)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . . | 9 |\n| 3.4. Linear Diffusion Layer 𝑝 𝐿 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 4.\nAuthenticated Encryption Scheme: Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1. Specification of Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.1. Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.2. Decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.1. Truncation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.2. Nonce Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.3. AEAD Requirements.............................................................. | 19 |\n| 4.4. Security Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.1. Single-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.2. Multi-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.3. Nonce-Misuse Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 21 |\n| 5. Hash and eXtendable-Output Functions (XOFs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 9)"}, {"role": "assistant", "content": "rity needs and goals. Information Dissemination allows for information to continue to flow to customers and others in the ecosystem about the cybersecurity of their IoT devices and associated systems.\nCustomers and others will benefit from 1) the disclosure of newly discovered cybersecurity vulnerabilities for the device, associated systems and software, etc. and 2) notifications about IoT device\n\nupdates, such as software updates, algorithm changes, new protocols, or changes in the vendors used by the manufacturer to update cybersecurity, that may impact cybersecurity risks. 1\n\nEducation and Awareness provides the educational content required to support customers and others in the secure use and safeguarding of IoT devices and associated systems, software, and hardware. By making customers and others in the ecosystem more knowledgeable about how to secure the IoT devices, and how to most effectively use the device's cybersecurity capabilities, manufacturers can help reduce the number of occurrences and related severity of IoT device compromises, thwart attacks against the devices, and reduce the number of vulnerabilities that are exploited and lead to compromised devices. Customers are the typical recipients of the non-technical supporting capabilities, but some customers may not be able to use these non-technical supporting capabilities directly. In the latter case, the capability might be used by other entities in the IoT device ecosystem (e.g., vendors, trade or professional organizations, advocacy groups, and technology media) to help customers meet their needs and goals. This baseline was developed after reviewing a variety of guidance documents from multiple sources and receiving input from stakeholders. It represents a coordinated effort to produce a definition of common capabilities not an exhaustive list. The core baseline is intended to be a flexible starting point."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does IoT Device Cybersecurity Capability Core Baseline provide?"}, {"role": "assistant", "content": "## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Karen Scarfone Matthew Smith\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\n\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Applied Cybersecurity Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nMatthew Smith Huntington Ingalls Industries Annapolis Junction, MD\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nMay 2020\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259A 23 pages (May 2020)\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Contingency Planning Guide for Federal Information Systems provide? (Part 8)"}, {"role": "assistant", "content": "Background ....................................................................................................5 | | | 2.1 | Contingency Planning and Resilience ........................................................................5 | Contingency Planning and Resilience ........................................................................5 | | | 2.2 | Types of Plans ............................................................................................................7 | Types of Plans ............................................................................................................7 | | | 2.2 | 2.2.1 | Business Continuity Plan (BCP)......................................................................8 | | | 2.2 | 2.2.2 | Continuity of Operations (COOP) Plan............................................................8 | | | 2.2 | 2.2.3 | Crisis Communications Plan............................................................................9 | | | 2.2 | 2.2.4 | Critical Infrastructure Protection (CIP) Plan.....................................................9 | | | 2.2 | 2.2.5 | Cyber Incident Response Plan......................................................................10 | | | 2.2 | 2.2.6 | Disaster Recovery Plan (DRP)......................................................................10 | | | 2.2 | 2.2.7 | Information System Contingency Plan (ISCP)...............................................10 | | | | 2.2.8 | Occupant Emergency Plan (OEP).................................................................10 | | | Chapter 3."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 7)"}, {"role": "assistant", "content": "] . . . | 6 |\n| Table 5. Performance of Classic McEliece in thousands of cycles on x86_64 | Table 5.\nPerformance of Classic McEliece in thousands of cycles on x86_64 | 6 |\n| Table 6. BIKE keys and ciphertext sizes in bytes | . . . . . . . . | 7 |\n| Table 7.HQC keys and ciphertext sizes in bytes . | . . . . . . . | 7 |\n| Table 8. Classic McEliece keys and ciphertext sizes in bytes . . | Table 8. Classic McEliece keys and ciphertext sizes in bytes . . | 7 |\n\n## Supplemental Content\n\nThe NIST Post-Quantum Cryptography Standardization Process web page is available at https://cs rc.nist.gov/Projects/post-quantum-cryptography/post-quantum-cryptography-standardization. ## Acknowledgments\n\nNIST would like to thank all of the candidate submission teams who developed, designed, and analyzed the post-quantum candidate algorithms and prepared detailed submission packages. NIST is also grateful for the efforts of those in the cryptographic community who provided security, implementation, and performance analyses of the candidate algorithms during the four rounds of the process. NIST would not be able to select post-quantum digital algorithms for standardization without the combined efforts of these individuals and the algorithm submitters. The authors of this report also appreciate the efforts by other members of NIST's PQC team who reviewed candidate algorithms, analyses, and public comments; performed testing; provided technical and administrative support; and participated in numerous meetings to discuss the selection of the candidate to be standardized."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nFew software development life cycle (SDLC) models explicitly address software security in detail, so secure software development practices usually need to be added to each SDLC model to ensure that the software being developed is well-secured. This document recommends the Secure Software Development Framework (SSDF) - a core set of high-level secure software development practices that can be integrated into each SDLC implementation. Following such practices should help software producers reduce the number of vulnerabilities in released software, reduce the potential impact of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of vulnerabilities to prevent future recurrences. Because the framework provides a common vocabulary for secure software development, software acquirers can also use it to foster communications with suppliers in acquisition processes and other management activities. This document describes a set of fundamental, sound practices for secure software development called the Secure Software Development Framework (SSDF). Organizations should integrate the SSDF throughout their existing software development practices, express their secure software development requirements to third-party suppliers using SSDF conventions, and acquire software that meets the practices described in the SSDF."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |--------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Data Protection : The IoT device can protect the data it stores and transmits from unauthorized access and modification."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.4.2 | Backup Methods and Offsite Storage... 3.4.2 should be considered and may include commercial contracts with alternate site vendors, reciprocal agreements with internal or external organizations, and service-level agreements (SLAs) with equipment vendors. 3.4.2 through 3."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "echnology Laboratory (ITL)\n\nMark G. Hakun\nChair\n\nKevin Stine\nCybersecurity Advisor, ITL\n\nMatthew Scholl\nChief, Computer Security Division\n\nKevin Stine\nChief, Applied Cybersecurity Division\n\nDominic A.\nCussatt\nCo-Chair\n\nKevin Dulany\nTri-Chair—Defense Community\n\nChris Johnson\nTri-Chair—Intelligence Community\n\nVictoria Yan Pillitteri\nRisk Management Framework Project Leader\n\nVicki Michetti\nTri-Chair—Civil Agencies\n\nJoint Task Force (JTF) Working Group\n\nVictoria Yan Pillitteri\nNIST, JTF Leader\n\nEduardo Takamura\nNIST\n\nMcKay Tolboe\nDoD\n\nDave Myers\nVeterans Affairs\n\nKelley Dempsey\nNIST\n\nVicki Michetti\nVeterans Affairs\n\nRon Ross\nNIST\n\nNaomi Lefkovitz\nNIST\n\nAndy Rovnak\nIntelligence Community\n\nPeter Duspiva\nIntelligence Community\n\nChris Johnson\nIntelligence Community\n\nJessica Dickson\nNIST\n\nAngela Smith\nNIST\n\nJon Boyens\nNIST\n\nNed Goren\nNIST\n\nKaitlin Boeckl\nNIST\n\nKatie Isaacson\nThe MITRE Corporation\n\nRandy Gabel\nThe MITRE Corporation\n\nDavid Black\nThe MITRE Corporation\n\nPam Miller\nThe MITRE Corporation\n\niii\n\n\fNIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nIn addition to the above acknowledgments, a special note of thanks goes to Jeff Brewer, Jim\nFoti, Cristina Ritfeld, Isabel Van Wyk, and the NIST web team for their outstanding\nadministrative support, Chris Enloe for his technical review and insight, and to David Waltermire\nand Wendell Piez for their contribution to the development of the SP 800-53A assessment\ntables (both electronic sources, and derivative publications) using Open Security Controls\nAssessment Language (OSCAL)."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 3)"}, {"role": "assistant", "content": "..................5 |\n| 4. Case Study .....................................................................................................................................8 |\n| 5.\nConclusion and Future Work.........................................................................................................12 |\n| References.......................................................................................................................................13 |\n| List of Figures |\n| Fig. 1. Security challenges in the semiconductor supply chain..............................................................2 |\n| Fig. 2. Methodology for supply chain threat analysis...........................................................................5 |\n| Fig. 3. Threat severity levels for colluding adversaries in the context of hardware Trojan insertion ......6 |\n| Fig. 4. Threat severity levels for colluding adversaries in context of logic obfuscation ........................10 |\n\n## 1. Introduction\n\nThere are numerous security challenges in the semiconductor supply chain. As most chip design companies have become fabless, they rely on offshore foundries for fabrication. This is especially true for the most advanced technology nodes, and the semiconductor supply shock in 2021 has manifested these supply chain security issues. In addition to availability uncertainty, there are many more nuanced security risks in the current semiconductor supply chain, such as IP theft, counterfeiting, Trojan insertion, and reverse engineering. In order to counteract these security risks, many types of solutions have been proposed, ranging from design to test phases of the supply chain."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 8)"}, {"role": "assistant", "content": "of the Workshop. from the Workshop and subsequent efforts in this area will have far-\nreaching, beneficial effects on the use of computers throughout the\ncountry\n\nThe products to be derived\n\nDennis K.\nBrans tad\nChairman, TG-15\n\niv\n\n\fABSTRACT\n\nIts purpose was to explore the state-of-the-art in this\n\nThe National Bureau of Standards, with the support of the U.S. Gen-\neral Accounting Office, sponsored an invitational workshop on \"Audit and\nEvaluation of Computer Security,\" held in Miami Beach, Florida on March\n22-24, 1977. area and define appropriate subjects for future research. perts in the audit and computer communities were invited to discuss the\nsubject in one of ten sessions, each of which considered a different as-\npect. these reports form the body of these Proceedings. The ten topics re-\nported on are: Internal Audit Standards, Qualifications and Training,\nSecurity Administration, Audit Considerations in Various System Environ-\nments, Administrative and Physical Controls, Program Integrity, Data In-\ntegrity, Communications, Post-Processing Audit Tools and Techniques, and\nInteractive Audit Tools and Techniques. A consensus report was produced by each of the ten sessions and\n\nLeading ex-\n\nAudit standards, audit techniques, audit tools, audit\n\nKEYWORDS:\ntraining, communications security, computer controls, computer\nsecurity, data integrity, interactive audit, internal audit, post-\nprocessing audit, program integrity. ACKNOViLEDGEMENTS\n\nThe success of the Workshop was dependent on the work of many peo-\nWe would particularly like to take this opportunity to thank all\n\nple. the Session Chairmen, the Session Recorders, and the attendees for their\nefforts in behalf of this Workshop. We would also like to thank the ses-\nsion coordinators Robert V. Jacobson, John Panagacos, and Thomas C. Lowe\nfor making things run smoothly while the Workshop was taking place; and\nDennis K. Branstad for photographing scenes from the Workshop."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nTo enable advanced cyber defense capabilities, SCAP v2 defines an architecture of clearly scoped and defined security components. SCAP v2 architectural components must be scalable, interoperable, easy to use, extensible, and capable of sharing data with other SCAP 2.0 components. Additionally, the architecture supports the collection and distribution of all information needed by the humans supporting operations and security functions, to include systems administrators, incident responders, network operators, and other similar stakeholders. The SCAP v2 architecture is reflective of real world scenarios of how these stakeholders use data about their networks. The SCAP architecture illustrated in Figure 1 incorporates a number of components, which are described below, and standards, which are described in section 3.3."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Getting Started with Awareness and Training\n\n## Family: Awareness and Training"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.8 (NIST 3.3.8)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.3.8 SP800161 : SA-4, SA-8, SA-9, SA-9(3), SR-3, SR-4, SR-4(3), SR-4(4) SP800181 : SP-DEV-002; K0153, K0266; S0298 |\n| | PW. 3.3.8 SP800161 : SA-15(10) SP800181 : K0041, K0042, K0151, K0292, K0317; S0054; A0025 SP800216 : All |\n| Assess, Prioritize, and Remediate Vulnerabilities (RV. 3.3.8 SP800161 : SA-15(7) SP800181 : K0009, K0039, K0070, K0161, K0165; S0078 |\n\n| Practices | Tasks | Notional Implementation Examples | References |\n|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | RV."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.3.8", "cmmc_practice_id": "AU.L2-3.3.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.2. 3.2.2. 3.2.2."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.7 (NIST 3.2.7)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.7. 3.2.7. 3.2.7."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.7", "cmmc_practice_id": "AT.L2-3.2.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nource code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications.\n| CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 8)"}, {"role": "assistant", "content": "ies included in this baseline. Figure 1: How customers and others in the IoT device ecosystem will use the capabilities in the baseline if provided by IoT device manufacturers and supporting entities.\n\n\nDocumentation captures information potential customers and others in the ecosystem may need to know about the IoT devices and ways in which it, and associated data and systems, can be secured. Such documentation is also often necessary prior to purchase and throughout the IoT device's lifecycle for the customer and others in the ecosystem (e.g., auditors and assessors). This documentation supports the appropriate treatment of risk, compliance, and assurance from internal and external perspectives when the IoT device and associated systems are implemented within the customer environment. As shown in Figure 1, documentation acts as a pillar of support for other non-technical capabilities. This is because other non-technical capabilities, including those in the IoT non-technical supporting baseline, will use the information captured via documentation to customize their delivery. Information and Query Reception occurs after purchase and allows customers and others in the ecosystem (e.g., researchers, product rating organizations) to submit questions and other information related to securing the IoT device and associated systems. The manufacturer and supporting parties can then respond. Information and query reception can assist customers and others in many ways throughout the lifecycle of an IoT device such as by allowing manufacturers and supporting third -party entities to adapt and update their support services (e.g., provided through other non-technical supporting capabilities) for the customers' cybersecurity needs and goals. Information Dissemination allows for information to continue to flow to customers and others in the ecosystem about the cybersecurity of their IoT devices and associated systems."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n- [RFC 4492] Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS), May 2006, see https://tools.ietf.org/html/rfc4492. - [RFC 5903] Elliptic Curve Groups Modulo a Prime (ECP Groups) for IKE and IKEv2, June 2010, see https://tools.ietf.org/html/rfc5903. - [RFC 7919] Negotiated Finite Field Diffie-Hellman Ephemeral Parameters, August 2016, see https://tools.ietf.org/html/rfc7919. - [SECG] Standards for Efficient Cryptography Group, see http://www.secg.org/. - [SEC2] Standards for Efficient Cryptography, SEC 2: Recommended Elliptic Curve Domain Parameters, September 2000, see http://www.secg.org/SEC2-Ver1.0.pdf. - [SP 800-38B] Special Publication 800-38B, Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication , May 2005, with updates dated October 2016. https://doi.org/10.6028/NIST.SP.800-38B\n- [SP 800-38C] Special Publication 800-38C, Recommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentiality , May 2004, with updates dated July 2007. https://doi.org/10.6028/NIST.SP.800-38C\n- [SP 800-38F] Special Publication 800-38F, Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping , December 2012. https://doi.org/10.6028/NIST.SP.800-38F\n- [SP 800-52] Special Publication 800-52 Revision 2 (DRAFT), Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations , November 15, 2017. https://csrc.nist.gov/publications/detail/sp/800-52/rev-2/draft\n- [SP 800-56B] Special Publication 800-56B Revision 1, Recommendation for Pair-Wise Key-Establishment Schemes Using Integer Factorization Cryptography , September 2014. https://doi.org/10.6028/NIST.SP.800-56Br1\n- [SP 800-56C] Special Publication 800-56C Revision 1, Recommendation for Key Derivation Methods in Key Establishment Schemes , April 2018."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 4)"}, {"role": "assistant", "content": "00-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171.\nNIST 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. \n\nNIST SP 800-172A, Assessing Enhanced Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the enhanced security requirements in SP 800-172. ## A is for Assessment\n\nKnowing what requirements to implement is important, but it is also important to understand how to evaluate the organization's implementation. Both publications work handin-hand for full implementation. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas\n\n\n\nified-information\n\nProtecting information from unauthorized modification\n\n## Key Term: Security Requirement\n\n[SP 800-171] Security Requirement: Security outcomes levied on a nonfederal organization to ensure adequate measures are taken to protect the confidentiality of CUI being processed, stored, or transmitted. \n\n\n\nImportant Note: The security requirements in NIST SP 800-171 are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. Protecting information from unauthorized access and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.4.3 | Firewalls... 3.4.3 Firewalls\n\nA network firewall is a device deployed between networks to restrict which types of traffic can pass from one network to another."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nthe Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies.\nThe scope of this publication pertains to federal information systems, which are discrete sets of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information, whether such information is in digital or non-digital form. Information resources include information and related resources, such as personnel, equipment, funds, and information technology."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nrs or services in a direct way. Privileged users responsible for configuring, maintaining, and operating the HPC system access the management zone servers and switches through extra security controls.\nFor example, from the public-facing login nodes, they may go through a bastion host that is typically located in the management zone, or they may establish a virtual private network (VPN) with separate authentication and authorization or other appropriate security controls to reach the management zone. All systems are configured on networks that are not routed beyond the perimeter of the HPC system so that only nodes like compute nodes and storage nodes can access the services."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.5 (NIST 3.7.5)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.7.5 Formulary | 3. 3.7.5 Formulary | 10-13 10-14 |\n| | | | 10-14 |\n| 4. 3.7.5 Formulary ; Ihe formulary is the most general of all forms of data classification scheme."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.7.5", "cmmc_practice_id": "MA.L2-3.7.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nPreventive Maintenance for Technology\n\nPreventive Maintenance for Technology\n\nEnterprise patch management is the process of identifying, prioritizing, acquiring, installing, and verifying the installation of patches, updates, and upgrades throughout an organization. Patching is more important than ever because of the increasing reliance on technology, but there is often a divide between business/mission owners and security/technology management about the value of patching. This publication frames patching as a critical component of preventive maintenance for computing technologies - a cost of doing business, and a necessary part of what organizations need to do in order to achieve their missions. This publication also discusses common factors that affect enterprise patch management and recommends creating an enterprise strategy to simplify and operationalize patching while also improving reduction of risk. Preventive maintenance through enterprise patch management helps prevent compromises, data breaches, operational disruptions, and other adverse events."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.4.3 | Alternate Sites ... 3.4.3 Alternate Sites\n\nAs stated in Section 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 9)"}, {"role": "assistant", "content": "..........................................6 |\n| 3. | Threat Environment.............................................................................................................\n7 |\n| 3.1 | Identifier Collisions .......................................................................................................7 |\n| 3.2 | Revoked PIV Cards .......................................................................................................8 |\n| 3.3 | Visual Counterfeiting ....................................................................................................8 |\n| 3.4 | Skimming.......................................................................................................................9 |\n| 3.5 | Sniffing ..........................................................................................................................9 |\n| 3.6 | Social Engineering.......................................................................................................10 |\n| 3.7 | Electronic Cloning.......................................................................................................10 |\n| 3.8 | Electronic Counterfeiting ............................................................................................10 |\n| 3.9 | Other Threats ...............................................................................................................11 |\n| 4. | PIV Authentication Mechanisms in PACS Applications ................................................"}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| Priority | Recommendations, Considerations, Notes making on when to escalate or elevate incident response activities.\n|\n|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| GV.RM-07 | Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions | Low | |\n| GV.RR (Roles, Responsibilities, and Authorities) | Cybersecurity roles, responsibilities, and authorities to foster accountability, performance assessment, and continuous improvement are established and communicated | Medium | R1: Cybersecurity roles, responsibilities, and authorities should include incident response."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nthat govern actions to be taken following a system disruption. The Activation/Notification Phase describes the process of activating the plan based on outage impacts and notifying recovery personnel.\nThe Recovery Phase details a suggested course of action for recovery teams to restore system operations at an alternate site or using contingency capabilities. The final phase,"}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 6)"}, {"role": "assistant", "content": "| Terms and definitions ......................................................................................................\n1 |\n| | Symbols and abbreviated terms...................................................................................... 1 |\n| | Document organization.................................................................................................... 1 |\n| | General....................................................................................................................... 1 |\n| | Modification ................................................................................................................"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-232\n\n## Ascon-Based Lightweight Cryptography Standards for Constrained Devices\n\nAuthenticated Encryption, Hash, and Extendable Output Functions\n\nMeltem Sönmez Turan Kerry A. McKay Donghoon Chang Jinkeon Kang John Kelsey\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-232\n\n\n\n## NIST Special Publication 800 NIST SP 800-232\n\n## Ascon-Based Lightweight Cryptography Standards for Constrained Devices\n\nAuthenticated Encryption, Hash, and Extendable Output Functions\n\nMeltem Sönmez Turan Kerry A. McKay Jinkeon Kang* John Kelsey\n\nComputer Security Division Information Technology Laboratory\n\n* Former Foreign Guest Researcher; all work for this publication was done while at NIST. Donghoon Chang\n\nStrativia\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-232\n\nAugust 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n- The types (e.g., hard copy, ISM), physical sizes, density (e.g., high resolution film), or capacities (e.g., megabyte, gigabyte, terabyte for ISM) of the media to be sanitized\n- The confidentiality requirement for the information recorded or stored on the media\n- Whether the media will be processed in a controlled area\n- Whether sanitization techniques should be conducted by the organization or a third party\n- Whether sanitization is performed on-site or off-site 3\n- The anticipated volume of media to be sanitized by type\n- The availability of sanitization equipment and tools\n- The training level of personnel with sanitization equipment or tools\n- How much time the complete sanitization technique will take (i.e., duration)\n- The cost of sanitization when considering tools, training, verification, and re-entering ISM into the supply stream\n\n- Alignment of the organization's data classification scheme (e.g., low, medium, and high security categorizations) with minimum acceptable sanitization methods (i.e., clear, purge, and destroy)\n- Requirements for the disposal and/or reuse of storage assets\n- Expected outcomes from storage sanitization activities (e.g., identification of specific, acceptable sanitization techniques [13])\n- Documentation or evidence associated with sanitization activities (see Sec. 4.6)\n- The identification of roles and responsibilities (see Sec. 4.7) and personnel competencies, skills, and training\n- The use of sanitization tools, including equipment calibration, testing, and maintenance\n- Type of assurances (e.g., guarantees, assessment results, formal certifications) that the ISM vendor should provide for the sanitization capabilities\n\nVarying data protection policies may be established within an organization."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171Ar3\n\n\n\n## NIST Special Publication\n\n## NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-171Ar3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in federal information systems."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| Chapter 1."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos...............................................24"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- A business champion: Someone who is responsible for developing and maintaining the incident response plan.\n- Who to call: List all the individuals who may be part of the incident response efforts. Include their contact information, roles, and responsibilities.\n- What/when/how to report: List the business' communications/reporting responsibilities as required by laws, regulations, contracts, agreements, or policies.\n- Also, most federal contracts will include specific reporting and notification requirements that should be included in the Incident Response Plan\n\nDescription: Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of the systems; and employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| 1 | Summary.............................................................................................1 | Summary.............................................................................................1 | Summary.............................................................................................1 | |-----|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | | 1.2 | Solution..........................................................................................................................3 | | | | 1.3 | Benefits..........................................................................................................................4 | | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | | 2.1 | Typographic Conventions..............................................................................................5 | | | 3 | Approach.............................................................................................6 | Approach.............................................................................................6 | | | | 3.1 | Audience........................................................................................................................6 | | | | 3.2 | Scope .............................................................................................................................6 | | | | | 3.2.1 Scenario 1: Creation of Verifiable Platform | Artifacts ..................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.1.3. 3.1.3): A secret sent or received through a separate\n\ncommunication channel with the subscriber\n\n• Single-factor one-time password (OTP) (Sec. 3.1.3."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\nlation mechanism (KEM) selected for standardization was CRYSTALS-Kyber (ML-KEM [3]). The digital signatures selected were CRYSTALS-Dilithium (ML-DSA [4]), Falcon (FN-DSA), and SPHINCS + (SLH-DSA [5]).\nFor a detailed explanation of NIST's choices, as well as a summary of the third round, see NIST IR 8413 [2]."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.5 (NIST 3.3.5)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.3.5. 3.3.5."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.3.5", "cmmc_practice_id": "AU.L2-3.3.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 2)"}, {"role": "assistant", "content": "0\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/publications/cswp, including related content, potential updates, and document history.\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis work proposes a framework for analyzing threats related to the semiconductor supply chain. The framework introduces a metric that quantifies the severity of different threats subjected to a collusion of adversaries from different stages of the supply chain. Two different case studies are provided to describe the real-life application of the framework. The metrics and analysis aim to guide security efforts and optimize the trade-offs of hardware security and costs. ## Keywords\n\ncollusion; security metrics; supply chain life cycle; supply chain security. ## Table of Contents\n\n| 1. Introduction...................................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Stages of Semiconductor Supply Chain Stages.................................................................................3 |\n| 3. Framework for Supply Chain Threat Analysis...................................................................................5 |\n| 4. Case Study .....................................................................................................................................8 |\n| 5."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8523/final, including related content, potential updates, and document history. State agencies that have already implemented MFA may decide to offer an MFA service to local agencies within their jurisdiction, as shown in Fig. 9. This model might be offered only to small or rural agencies who may lack the necessary funding and/or knowledge to implement MFA on their own, or the state might consider a shared service model where identity services are offered to all eligible and interested agencies within the state. Such an approach could result in economies of scale that could save costs for both state and local agencies and could also reduce the number of MFA architectures and implementations needed across the state. Establishing a state-shared service might also afford agencies greater ability to influence vendor capabilities and updates, including updates to support standards and best practices for MFA. - [1] U.S. Department of Justice (2024) Criminal Justice Information Services (CJIS) Security Policy, Version 6.0. CJISSECPOL v6.0. Available at https://le.fbi.gov/filerepository/cjis\\_security\\_policy\\_v6-0\\_20241227.pdf\n- [2] Wisconsin Law Enforcement Network (2024) Public Safety Threat Report: 2024 Threat Landscape. https://wilenet.widoj.gov/sites/default/files/public\\_files-2025-02/ijis2024-threat-landscape-report.pdf\n- [3] Temoshok D, Proud-Madruga D, Choong YY, Galluzzo R, Gupta S, LaSalle C, Lefkovitz N, Regenscheid A (2025) Digital Identity Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63-4. https://doi.org/10.6028/NIST.SP.800-63-4\n- [4] Temoshok D, Fenton JL, Choong YY, Lefkovitz N, Regenscheid A, Galluzzo R, Richer JP (2025) Digital Identity Guidelines: Authentication and Authenticator Management."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n.................................................................... | LIST OFTABLES....................................................................................................................\n| VIII |\n| EXECUTIVE SUMMARY........................................................................................................... | EXECUTIVE SUMMARY........................................................................................................... | 1 |\n| 1. INTRODUCTION.................................................................................................................. | 1. INTRODUCTION.................................................................................................................. | 1 |\n| 1.1 | PURPOSEAND SCOPE ......................................................................................................... | 1 |\n| 1.2 | AUDIENCEAND ASSUMPTIONS .........................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.5.3 | A Detailed Scoring Approach | A Detailed Scoring Approach | 60 |\n| | 3. 3.5.3 | Survey Questionnaire - Initiation Phase | 86 |\n\n| 4. 3.5.3 A Detailed Scoring Approach\n\nThe more detailed approach looks in depth at the characteristics associated with each dimension."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "following components: (i) a control section; (ii) a supplemental guidance section; (iii) a control enhancements section; (iv) a references section; and (v) a priority and baseline allocation section.\nFigure 2: The Risk Management Framework\n\n\n\n## 3 Control Baselines and Tailoring\n\nTo assist organizations in making the appropriate selection of security controls for information systems, the concept of security control baselines is introduced. Security control baselines are the starting point for the security control selection process and are chosen based on the security category and associated impact level of information systems determined in accordance with FIPS Publication 199 and FIPS Publication 200, respectively (Step One of the RMF). SP 800-53 Rev. 4 states that 'the security controls and control enhancements listed in the initial baselines are not a minimum- but rather a proposed starting point from which controls and controls enhancements may be removed or added.' Appendix D provides a listing of baseline security controls corresponding to the low-impact, moderate-impact, and high-impact information systems, using the high water mark defined in FIPS Publication 200. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 7)"}, {"role": "assistant", "content": "171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements.\n|\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |\n\n\n\nView more FAQs here. If you still have a question after reviewing all our FAQs , send your question to: sec-cert@nist.gov. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n\n\n## Additional Resources\n\n## Online Introductory Courses Available for the NIST SP 800-53 Series\n\n\n\nSP 800-171 requirements are focused on protecting confidentiality and are based on a subset of controls found in SP 800-53, which is a catalog of security and privacy controls for systems and organizations. With that in mind, it is important to have a basic understanding of the SP 800-53 series. To assist, NIST has released three self-guided online introductory courses to provide a high-level overview of foundational security and privacy risk management concepts. The online introductory courses are between 45-60 minutes, are available at no cost, and registration is not required. Access the courses. ## Roles of Different Federal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nives), there need to be different tiers of metrics based on the audience or user. For example, the CWE structure could be used to define security requirements that lead to associated security metrics.\nJason noted that CWEs for hardware are relatively new, starting around 2020, compared to CWEs' long track record for software, which started around 2006. Since CWEs point out common root cause weaknesses that lead to vulnerabilities, they foster a more proactive approach by allowing security issues to be discovered and mitigated earlier in the hardware development life cycle, thus lowering the financial impact. Having good metrics that can be used to inform design and business decisions would be helpful to the semiconductor community. Finally, Mark Tehranipoor from the University of Florida emphasized the importance of thinking about security and associated metrics in the early stages of the hardware development life cycle. Specifically, this involves conducting a security and risk assessment and developing a"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\nData administration is viewed as responsible for successful management and controls of data files and data bases necessary to support the information processing system. It is supported by data management systems and data base management systems. The control policies revolve around the three concepts of identification, authorization, and authentication and Include consideration of access policies, detection of unauthorized statistical disclosure, the maintaining of appropriate transaction trails, and the integrity of data and programs.\n\nTop management should require a security check of individuals participating in the design, operation, and maintenance of its data processing systems. (See section 3.5.) It is appropriate to assign responsibility for screening to the agency personnel office.\n\nAuthentication is a measure designed to increase protection against fraudulent transmissions by establishing the validity of a transmission, message, station, or originator."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nhe State of Maryland and Montgomery County, Maryland. The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register.\nRespondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution. We worked with:"}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-11-13\n\n## How to Cite this NIST Technical Series Publication:\n\nHawes D, Calis A, Crombie R (2023) Cryptographic Module Validation Program (CMVP) Security Policy Requirements: CMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-140Br1. https://doi.org/10.6028/NIST.SP.800-140Br1\n\n## Author ORCID iDs\n\nDavid Hawes: 0000-0002-0173-6795 Alexander Calis: 0000-0003-1937-8129\n\n## Contact Information\n\nsp800-140-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nNIST Special Publication (SP) 800-140Br1 is to be used in conjunction with ISO/IEC 19790 Annex B and ISO/IEC 24759 Section 6.14. This Special Publication modifies only those requirements identified in this document. NIST SP 800-140Br1 also specifies the content of the information required in ISO/IEC 19790 Annex B. As a validation authority, the Cryptographic Module Validation Program (CMVP) may modify, add, or delete Vendor Evidence (VE) and/or Test Evidence (TE) specified under paragraph 6.14 of the ISO/IEC 24759 and specify the order of the security policy as stated in ISO/IEC 19790:2012 B.1."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Access Control on NoSQL Databases provide? (Part 10)"}, {"role": "assistant", "content": "the late 2000s, triggered by the growing popularity of distributed systems, such as cloud computing and big data, which required a shift away from relational databases (RDBMS) toward NoSQL databases.\nOrganizations now deal with enormous and constantly growing data and infrastructure needs or increasingly use the Web 3.0 framework for big data and real-time web applications, including handling unstructured data like documents, emails, and social media [AA, NO]. NoSQL databases are particularly useful for managing unstructured or very large data objects stored across distributed and cooperating devices. Use cases for retrieving such data range from critical scenarios (e.g., storing financial data and healthcare records) to more casual applications (e.g., chat log data, video, images, and readings from smart devices). Major Web (Cassandra) have developed or adopted different flavors of NoSQL databases to meet their growing data and infrastructure needs. Their success has inspired many of today's NoSQL applications [AA, CJ]. NoSQL database systems and data stores often outperform traditional RDBMS in various aspects, such as data analysis efficiency, system performance, ease of deployment, flexibility/scalability of data management, and users' availability. However, with an increasing number of people storing sensitive data in NoSQL databases, security issues have become critical concerns. NoSQL databases suffer from vulnerabilities, particularly due to the lack of effective support for data protection, including weak authorization mechanisms. As access control is a fundamental data protection requirement of any database management system the NoSQL database types along with their support for access control models and describing store and manage access control data (e.g., subjects, objects, actions, and attributes) in external systems rather than the NoSQL database itself, which has a wide range of different implementations not discussed in this document."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 3)"}, {"role": "assistant", "content": "programs may face a number of challenges, including lack of: leadership support; resources; and staff with sufficient background and skills to implement an effective and engaging program.\nHowever, no prior research has explored security awareness programs specifically in the United States (U.S.) government (federal) sector. To address this gap, NIST conducted a two-phase, mixed methods research study to understand the needs, challenges, and practices of federal security awareness programs. This report describes the research background and methodology, along with the characteristics of the participants, organizations, and programs represented in the study. Research results can serve as a resource for federal security awareness professionals, managers, and organizational decision makers to improve and advocate for their organizations' security awareness programs. Results can also inform the development of federal security awareness guidance, policies, sharing forums, and initiatives meant to aid programs in becoming more effective. While focused on the U.S. government, findings may also have implications for organizational security awareness programs in other sectors. ## Keywords\n\ncybersecurity; cybersecurity awareness; focus groups; mixed methods; security professionals; survey; training; usable cybersecurity\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| | INTRODUCTION................................................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication NIST SP 800-219r1\n\n## Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)\n\nMark Trapnell\n\nEric Trapnell\n\nMurugiah Souppaya\n\nBob Gendler\n\nDan Brodjieski\n\nAllen Golbig\n\nKaren Scarfone\n\nBlair Heiserman\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-219r1\n\n\n\n## NIST Special Publication NIST SP 800-219r1\n\n## Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)\n\nMark Trapnell Eric Trapnell Murugiah Souppaya Computer Security Division Information Technology Laboratory\n\n## Bob Gendler\n\nCustomer Access and Support Division Office of Information Systems Management\n\nDan Brodjieski\n\nNASA\n\nAllen Golbig\n\nJamf\n\nKaren Scarfone\n\nScarfone Cybersecurity\n\nBlair Heiserman\n\nInformation Technology Security & Networking Division Office of Information Systems Management\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-219r1\n\nJuly 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.......................................................................75 |\n| 5.4.1.\nBusiness Associate Contracts or Other Arrangements (§ 164.314(a)).......................................77 |\n| 5.4.2. Requirements for Group Health Plans (§ 164.314(b))................................................................79 |\n| 5.5.1. Policies and Procedures (§ 164.316(a))......................................................................................81 |\n| 5.5.2. Documentation (§ 164.316(b))...................................................................................................83 |\n| References.......................................................................................................................................85 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................87 |\n| Appendix B. Glossary .......................................................................................................................91 |\n| Appendix C."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n...........13 |\n| 3.2.1. MFA Users ..................................................................................................................................13 |\n| 3.2.2.\nIT Support Staff...........................................................................................................................14 |\n| 3.2.3. Other Agencies ...........................................................................................................................14 |\n| 3.2.4. Procurement Teams...................................................................................................................14 |\n| 3.2.5. Compliance Teams .....................................................................................................................15 |\n| 3.2.6. Legal Teams................................................................................................................................15 |\n| 3.2.7. Technology Vendors...................................................................................................................15 |\n| 3.4.1. Local Agency MFA Architectures................................................................................................17 |\n| 3.4.2. State MFA Deployments.............................................................................................................21 |\n| 3.4.3. Implementing MFA with VPNs ...................................................................................................25 |\n| 4. Key Takeaways.............................................................................................................................29 |\n| References.......................................................................................................................................31 |\n| Appendix A."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n## Data Integrity:\n\nThis publication is available free of charge from https://www.nccoe.nist.gov/projects/building-blocks/data-integrity/detect-respond.\n\n## Data Integrity: Detecting and Responding to Ransomware and Other Destructive Events"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines provide? (Part 4)"}, {"role": "assistant", "content": "e guidelines cover the identity proofing, authentication, and federation of users\n(e.g., employees, contractors, or private individuals) who interact with government\ninformation systems over networks.\nThey define technical requirements in each of\nthe areas of identity proofing, enrollment, authenticators, management processes,\nauthentication protocols, federation, and related assertions. They also offer technical\nrecommendations and other informative text as helpful suggestions. The guidelines are\nnot intended to constrain the development or use of standards outside of this purpose. This publication supersedes NIST Special Publication (SP) 800-63-3. Keywords\n\nassertions; authentication; authentication assurance; authenticator; credential service\nprovider; digital authentication; identity proofing; federation; passwords; PKI. Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems. The Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "privacy” is universally used since the\nguidance is applicable to both security and privacy control assessments. For certain systems,\nhowever, the guidance may only be relevant for security or privacy.\nOrganizations make their\nown determinations on when to manage security and privacy control assessments together or\nseparately. SP 800-53A provides guidance on assessing controls in information security program plans,\nprivacy program plans, system security plans, and privacy plans. Where the guidance refers to all\nplans listed above, the term “security and privacy plans” is used. If the guidance is specific to a\nsingle type of plan (e.g., system security plan), the specific type of plan is specified. Supplemental Content\n\nThe assessment procedures in Chapter 4 are published in multiple data formats, including\ncomma-separated values (CSV), plain text, and Open Security Controls Assessment (OSCAL). The\navailable data formats are accessible from the NIST SP 800-53A Revision 5, publication details\npage at https://csrc.nist.gov/publications/detail/sp/800-53a/rev-5/final. The OSCAL Content Git\nRepository is available at https://github.com/usnistgov/oscal-content. The CSV, plain text, and OSCAL formats represent derivative formats of the (normative)\nassessment procedures in this publication. If there are any discrepancies between the content in\nderivative formats and this publication, please contact sec-cert@nist.gov. Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent\nclaims whose use may be required for compliance with the guidance or requirements of this\npublication disclose such patent claims to ITL. However, holders of patents are not obligated to\nrespond to ITL calls for patents and ITL has not undertaken a patent search in order to identify\nwhich, if any, patents may apply to this publication."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.1.2 Years of Security Awareness Experience... 3.1.2 Years of Security Awareness Experience... 3.1.2 Years of Security Awareness Experience..."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\n...............................11 |\n| 2.5.1. Speaker Viewpoints....................................................................................................................11 |\n| 2.5.2.\nKey Highlights .............................................................................................................................13 |\n| 3. Summary and Road Ahead ...........................................................................................................15 |\n| Appendix A. Workshop Agenda........................................................................................................16 |\n| List of Figures |\n| Fig. 1. Components for securing microelectronics................................................................................1 |\n| Fig. 2. Distribution of workshop participants.......................................................................................2 |"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 10)"}, {"role": "assistant", "content": "and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance.\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement. Tailoring: The process by which control baselines are modified to achieve certain organizational goals and objectives. Definitions provided are intended as plain language. Review the NIST Glossary for official NIST definitions. Determine if your business has CUI. ## General Tips for Getting Started with NIST SP 800-171\n\nEveryone will have different approaches to getting started, but here are a few tips to get you started down the right path:\n\nUnderstand current (or future) legal, regulatory, or contractual requirements for protecting CUI. The federal agency is responsible for communicating what CUI the business is responsible for protecting as part of the contractual arrangement. If there are questions, reach out to the contracting officer. The business may also have additional compliance requirements beyond SP 800-171. If so, an initial task might be to understand where the requirements overlap and where they differ. With that information, the business can begin addressing requirements that meet multiple compliance requirements. Understand how CUI flows into, within, and out of the business. \n\nInventorying what systems or components the business has, and how the data flows into, within, and out of those systems or components, helps practitioners understand the scope of applicability of SP 800-171 security requirements to business systems. \n\nScope and Applicability of SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nDr. Arnold previously served as a Vice-President at Lucent Technologies Bell Laboratories where he directed the company's global standards efforts. His organization played a leading role in the development of international standards for Intelligent Networks and IP-based Next Generation Networks. In previous assignments at AT&T Bell Laboratories he had responsibilities in network planning, systems engineering, and application of information technology to automate operations and maintenance of the nationwide telecommunications network. Deployment rates for implantable medical devices (IMDs) have skyrocketed over the past decade. Devices such as pacemakers, cardiac defibrillators, heart monitors, cochlear implants, insulin pumps, infusion pumps and other similar devices are routinely used to monitor and treat a plethora of medical conditions. These IMDs have been increasingly accessible through wireless channels to support functions such as emergency extraction of patient health history, remote monitoring of health status, firmware updates and local as well as remote therapy reprogramming. As with all things connected to the cyber world, there are known and unknown threats lurking that threaten the reliability and safety of these devices as well the privacy of patients who depends on them. Audit logs are essential for tracking patient history and IMD behavior over a period of time. The audit records provide information needed for adequate patient care as well as updates to patient therapy delivered through the IMD. Given the limited storage capabilities of IMDs, it is possible to overflow the audit logs through certain types of attacks on the IMD. Creative techniques for selective overwriting of audit records based on significance of each type of audit record may be useful."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n..................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5.\nTraceability of CE Operations.....................................................................................................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1. Information Decisions in the System Life Cycle..........................................................................20 |\n| 4.3.2. Determination of Security Categorization..................................................................................21 |\n| 4.3.3. Reuse of Media...........................................................................................................................22 |\n| 4.3.4. Control of Media ........................................................................................................................22 |\n| 4.3.5. Data Protection Level .................................................................................................................23 |\n| 4.3.6. Sanitization and Disposal Decision.............................................................................................23 |"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\n- '…The executive branch operates its information technology (IT) on behalf of the American people. Its IT and data should be secured responsibly using all United States Government capabilities...'\n- '…Cybersecurity risk management comprises the full range of activities undertaken to protect IT and data from unauthorized access and other cyber threats, to maintain awareness of cyber threats, to detect anomalies and incidents adversely affecting IT and data, and to mitigate the impact of, respond to, and recover from incidents…'\n\nThe RMF emphasizes risk management by promoting the development of security and privacy capabilities into information systems throughout the system development life cycle (SDLC); 10 by maintaining situational awareness of the security and privacy posture of those systems on an ongoing basis through continuous monitoring processes; and by providing information to senior leaders and executives to facilitate decisions regarding the acceptance of risk to organizational operations and assets, individuals, other organizations, and the Nation arising from the use and operation of their systems. The RMF:\n\n- Chapter Two describes the concepts associated with managing information system-related security and privacy risk. This includes an organization-wide view of risk management; the RMF steps and task structure; the relationship between information security and privacy programs and how these programs are addressed in the RMF; information resources as system and system elements; authorization boundaries; security and privacy posture; and security and privacy considerations related to supply chain risk management."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\n## Blockchain for Access Control Systems\n\n## Blockchain for Access Control Systems\n\nThe rapid development and wide application of distributed network systems have made network security - especially access control and data privacy - ever more important. Blockchain technology offers features such as decentralization, high confidence, and tamper-resistance, which are advantages to solving auditability, resource consumption, scalability, central authority, and trust issues - all of which are challenges for network access control by traditional mechanisms. This document presents general information for blockchain access control systems from the views of blockchain system properties, components, functions, and supports for access control policy models. Considerations for implementing blockchain access control systems are also included."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThe new format for assessment procedures introduced in Special Publication (SP) 800-53A Revision 4, is\nfurther improved in this revision (SP 800-53A Revision 5). The format continues to reflect the\ndecomposition of assessment objectives into more granular determination statements wherever possible,\nthus providing the capability to identify and assess specific parts of security and privacy controls. Updates\nto SP 800-53A Revision 5:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ..............................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\nagement, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in federal information systems.\nThe Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 8)"}, {"role": "assistant", "content": "ederal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui.\n- NIST is responsible for developing and publishing the security requirements for the protection of CUI. How requirements are mandated, and any compliance issues related to nonfederal implementation of SP 800-171, are the responsibility of the federal agency requiring its use , as expressed in a specific contract or agreement. ## Additional NIST Resources\n\n- NIST's Protecting CUI Frequently Asked Questions\n- Changes Between SP 800-171 Rev. 2 and Rev. 3 (.xlsx)\n- The NIST Cybersecurity and Privacy Reference Tool (CPRT) provides online, interactive versions of the updated security requirements in SP 800-171, Revision 3 and the updated assessment procedures in SP 800-171A, Revision 3\n- Event Recording: ' CUI Security Requirements Workshop ,' which provides a general overview of SP 800 -171 and SP 800-171A\n- NIST Small Business Cybersecurity Corner\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n## What to Expect\n\nThe following pages delve deeper into the SP 800-171 R3 publication to provide more details for those responsible for implementing the requirements 3 . The following pages cover:\n\n\n\nPage 8: Key differences between SP 800-171 R2 and R3. Pages 9-10: General tips for getting started. Pages 11-28: Tips for getting started, broken out by Control Family. 3 We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\ns cryptographic modules utilize authentication that meets federal requirements. Operating systems utilizing encryption _MUST_ use FIPS-validated mechanisms for authenticating to cryptographic modules.\nNOTE: /etc/ssh/sshd_config will be automatically modified to its original state following any update or major upgrade to the operating system. check: | /usr/bin/grep -c \"^Ciphers aes256-ctr,aes192-ctr,aes128-ctr\" /etc/ssh/sshd_config result: integer: 1\n```"}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nThe Security Content Automation Protocol (SCAP) version 2 (v2) automates endpoint posture information collection and the incorporation of that information into network defense capabilities using standardized protocols. SCAP v2 expands the endpoint types supported by SCAP v1 through the explicit inclusion of network equipment, Internet of Things (IoT), and mobile devices in its scope. To automate self-reporting of posture information from endpoint machines, SCAP v2 will integrate with existing network management protocols that include the Internet Engineering Task Force (IETF) Network Endpoint Assessment (NEA) protocols. SCAP v2 will streamline SCAP content acquisition and reuse through its use of the IETF Resource Oriented Lightweight Information Exchange (ROLIE) protocol. Improvements to software version identification and the incorporation of patch information will be made by transitioning from the Common Platform Enumeration (CPE) to Software Identification (SWID) Tags. SCAP v2 provides component-level interoperability via a modular and extensible architecture. This white paper provides a gap analysis of SCAP v1 and an overview of how SCAP v2 will address these gaps; describes the SCAP 2.0 architecture; and provides a plan for completing the work necessary to finalize SCAP v2."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 3)"}, {"role": "assistant", "content": "signed statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST publications, other than the ones noted above, are available at http://csrc.nist.gov/publications. ## Abstract\n\nProceedings of the Cybersecurity in Cyber-Physical Workshop, April 23 - 24, 2012, complete with abstracts and slides from presenters. Some of the cyber-physical systems covered during the first day of the workshop included networked automotive vehicles, networked medical devices, semi-conductor manufacturing, and cyber-physical testbeds. Day two of the workshop covered the electric smart grid. Dr. Farnham Jahanian, NSF, was the keynote speaker on day one. ## Keywords\n\nCPS; cyber-physical systems; cybersecurity; networked automotive vehicles; networked medical devices; semi-conductor manufacturing\n\n## Acknowledgements\n\nThe editor would like to thank Suzanne Lightman, Kevin Stine (both NIST), and Mark Enstrom (Neustar) for being reviewers for this document. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide? (Part 3)"}, {"role": "assistant", "content": "baseline; Internet of Things (IoT); IoT products; manufacturing; privacy; risk management; securable products; security requirements; software development; threat modelling. ## Table of Contents\n\n| 1.\nIntroduction.....................................................................................................................................3 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Speaker Summaries..........................................................................................................................6 |\n| 3. Workshop Takeaways ......................................................................................................................9 |\n| References......................................................................................................................................... 15 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms ............................................................... 16 |\n| List of Tables |\n| Table 1 - Table of Takeaways ...............................................................................................................3 |\n| Table 2 - Agenda for the Workshop......................................................................................................5 |\n\n## 1. Introduction\n\nOn December 4 th , 2024, NIST hosted a workshop titled ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development ' to introduce and discuss potential areas to update as the NIST Cybersecurity for Internet of Things (IoT) program revises Foundational Cybersecurity Activities for IoT Device Manufacturers, NIST IR 8259."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. Security baselines are groups of settings used to configure a system to meet a target level or set of requirements or to verify that a system complies with requirements. The mSCP seeks to simplify the macOS security development cycle by reducing the amount of effort required to implement security baselines. This collaboration between federal agencies minimizes duplicate effort that would otherwise be needed for these agencies to administer individual security baselines."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nassociated with the centralized management of AC enforcement or AC data ownership [IR8202]. - Full blockchain nodes are not only a repository of AC data and logs of blocks but can also store objects.\nEven though blockchain contents are tamper-evident and tamper-resistant, [Kuhn] proposed a data structure with similar features to a blockchain - the data block matrix data structure - that allows for the deletion of arbitrary records and preserves hashbased integrity assurance that other blocks are unchanged. Such a feature may be incorporated into AC systems that require integrity and privacy protection such that organizations or users are able to delete all information related to a particular access request. - A consensus mechanism ensures that only valid transactions are recorded on the blockchain. Different kinds of consensus mechanisms can be used for AC systems, including proof of work (PoW), proof of stake (PoS), and single committee-based [LQLL]. For mandatory AC (MAC) policies, the integrity and consistency of AC administrations are maintained by consensus mechanisms configured for permissioned blockchains. Consensus mechanisms configured for permissionless blockchains are crucial for discretional AC (DAC) policies due to the dynamic management requirement for scalability and decentralization of the system."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\nThe assessment methods described above have associated attributes of depth and coverage , which affect the level of effort for the assessment. These attributes provide a means to define the rigor and scope of the assessment to obtain the assurance needed for enhanced security requirements. A description of assessment methods and objects is provided in Appendix C. Figure 1 illustrates an example of an assessment procedure for the CUI enhanced security requirement 3.1.3e from [SP 800-172].\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 3)"}, {"role": "assistant", "content": "reafter shortened to 'security awareness') programs may experience a number of challenges, including lack of funding and staff with the appropriate knowledge and skills to manage an effective program.\nWhile prior surveys and research have examined programs in the private sector, there is little understanding of whether these findings also apply within the U.S. government. To address this gap and better understand the needs, challenges, practices, and necessary competencies of federal security awareness teams and programs, NIST conducted a research study that leveraged both qualitative and quantitative methodologies. This companion document to NISTIR 8420 'Federal Cybersecurity Awareness Programs: A Mixed Methods Research Study' reports on a subset of study results focused on identifying the current job classifications, roles, and desired knowledge and skills for security awareness professionals within the federal government. Insights gained from these results are informing guidance and other initiatives to aid federal organizations in building security awareness teams with the appropriate competencies. While focused on the U.S. government, findings may also have implications for organizational security awareness professionals in other sectors. ## Keywords\n\ncybersecurity; cybersecurity awareness; focus groups; knowledge; mixed methods; professional development; security professionals; skills; survey; training; usable cybersecurity; work roles\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Executive Summary\n\nSecurity awareness programs aim to assist employees in recognizing and responding to security issues with a goal of achieving long-term behavior changes. Security awareness professionals are individuals who are tasked with managing and executing the security awareness programs within their organizations."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.2.\n\n3.2.1. CSP Fraud Management . . . . . . . . . . . . . . . . . . . . . .\n\n3.2.2. RP Fraud Management . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.1.3. 3.1.3). 3.1.3) should be used."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n....................................................................................... | 63 |\n| A.1.1.\nC-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 5)"}, {"role": "assistant", "content": "s and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n## Overview\n\n## Structure of SP 800-171\n\nSP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page). | Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Understanding the Security Requirements in SP 800-171\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n\n\n## Top 5 Frequently Asked Questions\n\n## Top five questions NIST receives on SP 800-171:\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Awareness and Training?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Cybersecurity State Awareness : The IoT device can report on its cybersecurity state and make that information accessible to authorized entities only."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does IoT Device Cybersecurity Capability Core Baseline support CMMC certification?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nDevice cybersecurity capabilities are cybersecurity features or functions that computing devices provide through their own technical means (i.e., device hardware and software). This publication defines an Internet of Things (IoT) device cybersecurity capability core baseline, which is a set of device capabilities generally needed to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 8)"}, {"role": "assistant", "content": " ## Examples of CSF Categories and Subcategories that are likely to include requirements for suppliers ## Govern: - Organizational Context: Legal, regulatory, and contractual requirements regarding cybersecurity including privacy and civil liberties obligations - are understood and managed [GV.OC-03] - Roles, Responsibilities, and Authorities: Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced [GV.RR02] - Cybersecurity Supply Chain Risk Management: Cyber supply chain risk management processes are identified, established, managed, monitored, and improved by organizational stakeholders [GV.SC] ## Identify: - Risk Assessment: The authenticity and integrity of hardware and software are assessed prior to acquisition and use [ID.RA-09]; Critical suppliers are assessed prior to acquisition [ID.RA-10] - Improvement: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties [ID.IM-02] ## Protect: - Identity Management, Authentication, and Access Control: Identities and credentials for authorized users, services, and hardware are managed by the organization [PR.AA-01] - Awareness and Training: Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind [PR.AT-02] ## Detect: - Continuous Monitoring: Personnel activity"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.1.4 | Non-Compliance Actions and Consequences | ... 3.1.4 Non-Compliance Actions and Consequences\n\nWe asked participants what happens when employees do not complete their required training by the deadline designated by the organization (select all that apply question type)."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.2.3 | Despliegue basado en un portal de recursos... 3.2.3), ya que la identidad y el estado del dispositivo proporcionan datos de referencia secundarios para las decisiones de acceso. 3.2.3 Despliegue basado en un portal de recursos\n\nEn este tipo de implementación, el PEP es un componente único que actúa como puerta de enlace para las solicitudes de los sujetos."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n.................................................................... | LIST OFTABLES....................................................................................................................\n| VIII |\n| EXECUTIVE SUMMARY........................................................................................................... | EXECUTIVE SUMMARY........................................................................................................... | 1 |\n| 1. INTRODUCTION.................................................................................................................. | 1. INTRODUCTION.................................................................................................................. | 1 |\n| 1.1 | PURPOSEAND SCOPE ......................................................................................................... | 1 |\n| 1.2 | AUDIENCEAND ASSUMPTIONS .........................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 10)"}, {"role": "assistant", "content": "not supported by SCAP v1. SCAP v2 will be developed iteratively. The first version of SCAP v2, SCAP 2.0, will focus on improving support for software inventory and vulnerability management use cases.\nAdditional use cases, including configuration assessment, will be addressed in future SCAP v2 revisions (e.g., 2.1, 2.2), which will incorporate new capabilities. By working iteratively, SCAP v1 capabilities will be gradually transitioned to SCAP v2, allowing new capabilities (e.g., improved software inventory support) to be adopted in parallel with existing SCAP v1 capabilities. The following subsections describe the design goals for SCAP v2, outline an initial SCAP 2.0 architecture, and identify several international standards that can be adopted by SCAP 2.0. Engagement with the community is needed to refine and build consensus around the approach and to complete the remaining work. ## 3.1 Design Goals for SCAP v2\n\nThe following SCAP v2 design goals address gaps in SCAP v1 and support new capabilities. Expanded Endpoint Type Support: In SCAP v2, all endpoint types are explicitly in scope. Supporting additional endpoint types will provide a more uniform endpoint posture assessment capability across all endpoints managed by an enterprise. This will help to unify software inventory, vulnerability management, and configuration setting management capabilities. SCAP 2.0 will focus on supporting desktop, laptop, and server computing devices, and support for additional endpoint types will be addressed in future SCAP v2 revisions. Event-driven Data Collection: SCAP v2 supports the collection and reporting of endpoint posture in cyber-relevant timeframes (e.g., seconds, minutes) based on reporting of endpoint posture change events. This avoids the lengthy, multi-day scanning frequencies commonly used to assess enterprise endpoint posture today."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-56A Revision 3\n\n## Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography\n\nElaine Barker Lily Chen Allen Roginsky Apostol Vassilev Richard Davis\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-56Ar3\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-56A Revision 3\n\n## Recommendation for Pair-Wise Key-\n\n## Establishment Schemes Using Discrete Logarithm Cryptography\n\nElaine Barker Lily Chen Allen Roginsky Apostol Vassilev\n\nComputer Security Division Information Technology Laboratory\n\nRichard Davis National Security Agency\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-56Ar3\n\nApril 2018\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by the National Institute of Standards and Technology (NIST) in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 10)"}, {"role": "assistant", "content": "able only covers the basics of the capabilities, the references can be invaluable for understanding each capability in more detail and learning how to implement each capability in a reasonable manner.\nThe following are the references used in Table 1:\n- o AGELIGHT : AgeLight Digital Trust Advisory Group, 'IoT Safety Architecture & Risk Toolkit (IoTSA) v3.1' [5]\n- o BITAG : Broadband Internet Technical Advisory Group (BITAG), 'Internet of Things (IoT) Security and Privacy Recommendations' [6]\n- o CSA : Cloud Security Alliance (CSA) IoT Working Group, 'Identity and Access Management for the Internet of Things' [7]\n- o CSDE : Council to Secure the Digital Economy (CSDE), 'The C2 Consensus on IoT Device Security Baseline Capabilities' [8]\n- o CTIA : CTIA, 'CTIA Cybersecurity Certification Test Plan for IoT Devices, Version 1.0.1' [9]\n\n- o ENISA : European Union Agency for Network and Information Security (ENISA), 'Baseline Security Recommendations for IoT in the context of Critical Information Infrastructures' [10]\n- o ETSI : European Telecommunications Standards Institute (ETSI), 'Cyber Security for Consumer Internet of Things' [11]\n- o GSMA : Groupe Spéciale Mobile Association (GSMA), 'GSMA IoT Security Assessment' [12]\n- o IEC : International Electrotechnical Commission (IEC), 'IEC 62443-4-2, Edition 1.0, Security for industrial automation and control systems - Part 4-2: Technical security requirements for IACS components' [13]\n- o IIC : Industrial Internet Consortium (IIC), 'Industrial Internet of Things Volume G4: Security Framework' [14]\n- o IoTSF : IoT Security Foundation (IoTSF), 'IoT Security Compliance Framework, Release 2' [15]\n- o ISOC/OTA : Internet Society/Online Trust Alliance (OTA), 'IoT Security & Privacy Trust Framework v2.5' [16]\n- o NEMA : National Electrical Manufacturers Association (NEMA), 'Cyber Hygiene Best Practices' [17]\n- o OCF : Open Connectivity Foundation (OCF) 'OCF Security Specification Version 2.1.2' [18]\n- o PSA : Platform Security Architecture (PSA) Joint Stakeholder Agreement (JSA) Members, 'PSA Certified™ Level I Questionnaire, Version 2.0 Beta' [19]\n\nAppendix B provides the definitions for the underlined terms in Table 1."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 10)"}, {"role": "assistant", "content": "vi | |---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| | 1 | Introduction ............................................................................................................1 | | 2 | The Secure Software Development Framework..................................................4 | | References...................................................................................................................20 | References...................................................................................................................20 | | The SSDF and Executive Order 14028 ..............................................24 | The SSDF and Executive Order 14028 ..............................................24 | | Acronyms............................................................................................25 | Acronyms............................................................................................25 | | Change Log.........................................................................................27 | Change Log.........................................................................................27 | | List of Tables | List of Tables | | Table 1: The Secure Software Development Framework (SSDF) Version 1.1................5 | Table 1: The Secure Software Development Framework (SSDF) Version 1.1................5 | | Table 2: SSDF Practices Corresponding to EO 14028 Clauses....................................24 | Table 2: SSDF Practices Corresponding to EO 14028 Clauses....................................24 | ## 1 Introduction A software development life cycle (SDLC) 1 is a formal or informal methodology for designing, creating, and maintaining software (including code built into hardware)."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.5 (NIST 3.4.5)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.4.5 | Application Whitelisting ... 3.4.5 Application Whitelisting\n\nApplication whitelisting technologies, also known as application control programs, are used to specify which applications are authorized for use on a host. 3.4.5) to prevent unauthorized applications from being run within it."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.4.5", "cmmc_practice_id": "CM.L2-3.4.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\ns specification requirements -that is, capabilities that implement all or part of a control and that may be assessed (i.e., as part of the verification, validation, testing, and evaluation processes).\nFinally, organizations may use the term statement of work requirements to refer to actions that must be performed operationally or during system development."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.4.1 | Threats ... 3.4.1 | Configuration... 3.4.1 Threats\n\nA threat is 'any circumstance or event with the potential to adversely impact organizational operations' [11]."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 5)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## 1 Introduction\n\nComputing devices that integrate physical and/or sensing capabilities and network interface capabilities are being designed, developed, and deployed at an ever-increasing pace. These devices are fulfilling customer needs in all sectors of the economy. Many of these computing devices are connected to the internet. A novel characteristic of these devices is the combination of connectivity and the ability to sense and/or affect the physical world. As devices become smaller and more complex, with an increasing number of features, the security of those devices also becomes more complex. This publication defines a baseline set of device cybersecurity capabilities that organizations should consider when confronting the challenge of the Internet of Things (IoT). Device cybersecurity capabilities are cybersecurity features or functions that computing devices provide through their own technical means (i.e., device hardware and software). The IoT device cybersecurity capability core baseline ( core baseline ) 1 defined in this publication is a set of device capabilities generally needed to support commonly used cybersecurity controls that protect devices as well as device data, systems, and ecosystems. The concept of a baseline in any context requires careful consideration; security capabilities for IoT devices are no exception."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n[IR7864] | Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nin place\n- Makes the practices broadly applicable, not specific to particular technologies, platforms, programming languages, SDLC models, development environments, operating environments, tools, etc.\n- Can help an organization document its secure software development practices today and define its future target practices as part of its continuous improvement process\n- Can assist an organization currently using a classic software development model in transitioning its secure software development practices for use with a modern software development model (e.g., agile, DevOps)\n- Can assist organizations that are procuring and using software to understand secure software development practices employed by their suppliers"}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nTechnology (NIST), Amy Wohl Phillips, Dean Gallup, and David Lynes of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content.\nThe authors would like to acknowledge Kelley Dempsey, Esther Katzman, Peter Mell, Murugiah Souppaya, Lee Badger, and Elizabeth Lennon of NIST, and David Linthicum of Booz Allen Hamilton for their keen and insightful assistance with technical issues throughout the development of the document."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n- A patch may not be available yet. For example, a vulnerability may be announced before a patch is ready, and it could be days, weeks, or months before the patch is released. - The vendor may no longer support the vulnerable software, meaning that a patch for it will never be released because the software is at end-of-life. - The organization may need to wait for a scheduled outage window, perform testing first, update other software that interacts with the software to be patched, or train employees on new features or interfaces. - Some patches may be considered a higher priority, so other patches are delayed due to limited resources. - The manufacturer may require customers to update the software on a delayed schedule, such as for assets with human safety implications in a highly regulated sector, because of the extensive testing and certification that must be performed first. In these cases, organizations that choose to implement updates on their own may be voiding the product warranty and preventing future support from the manufacturer. - The organization may need to comply with specific legal, regulatory, or business requirements. For example, an organization may need to use Federal Information Processing Standards (FIPS)-validated cryptographic modules for protecting data, but the cryptographic modules in the upgraded software are not yet FIPS-validated. 1. Know when new software vulnerabilities affect your organization's assets, including applications, operating systems, and firmware. This involves knowing what assets your organization uses and which software and software versions those assets run down to the level of packages and libraries, as well as keeping track of new vulnerabilities in that software. For example, your organization might subscribe to vulnerability feeds from software vendors, security researchers, and the National Vulnerability Database (NVD). 2. Plan the risk response."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\n## Overview and Considerations of Access Control Based on Attribute Encryption\n\n## Overview and Considerations of Access Control Based on Attribute Encryption\n\nHu VC (2023) Overview and Considerations of Access Control Based on Attribute Encryption. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8450-upd1, Includes updates as of December 20, 2023. https://doi.org/10.6028/NIST.IR.8450-upd1"}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.1.3 rsakpg1-crt ... 3.1.3 rsakpg1-crt\n\nrsakpg1-crt is the generator in the RSAKPG1 family such that the private key is in the Chinese Remainder Theorem format ( n , e , d , p , q , dP , dQ , qInv ). 3.1.3)."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 8)"}, {"role": "assistant", "content": "## Tabla de contenidos | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\n## 3.3. Augmenting KEV-Based Remediation Prioritization"}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nsiderations, such as the discovery of a vulnerability that would significantly impact the security, privacy, or safety of customers who continue to use the IoT product and its product components. - g.\nThe vulnerability management policies and processes associated with the IoT product, including :\n- i. Methods of receiving reports of vulnerabilities (see Information and Query Reception below). - ii. Processes for recording reported vulnerabilities. - iii. Policy for responding to reported vulnerabilities, including the"}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nThis document leverages the ISO/IEC standards as much as possible in forming vulnerability disclosure guidelines for the Federal Government. Federal vulnerability disclosure programs should follow, to the extent possible, the terminology used in this document to facilitate interoperability in communications (e.g., using the same names for the various actors), as well as for internal efforts of identification, assessment, and the minimization or elimination of vulnerabilities. When a needed term is not defined in this document but does exist in the ISO/IEC standards, the term from the standards should be used. A glossary of the major terms used in this document is provided in Appendix B.\n\nEach FCB member should develop the ability to receive source vulnerability reports from reporters, maintain a database of received reports, and engage in secure communications (e.g., using a report tracking system). 2 The expectation for communication with the reporter should be established, including the initial acknowledgment, status updates, and agreed-upon method of communication. The actual receipt of a source vulnerability report may take multiple forms (e.g., email, web forms, or a phone hotline) and should be stated in a public policy. It is also\n\nPrior to the receipt of any vulnerabilities, each FCB member will determine which government VDPOs fall within the scope of their services. The FCB member will then obtain and maintain a list of VDPO contacts within the relevant government agencies that receive and handle source vulnerability reports. Each FCB member should develop the capability to forward reports to VDPOs and to engage in ongoing communications to enable coordination. Lastly, FCB members may engage with industry-tied vulnerability coordination entities (e.g., CERT/CC 3 ) to facilitate coordination with non-government software and/or service providers."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 6)"}, {"role": "assistant", "content": "publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication.\n## Table of Contents\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Incident Response as Part of Cybersecurity Risk Management.........................................................4 |\n| 3. CSF 2.0 Community Profile for Cyber Incident Risk Management...................................................10 |\n| References.......................................................................................................................................36 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................38 |\n| Appendix B. Glossary .......................................................................................................................39 |\n| Appendix C. Change Log...................................................................................................................40 |\n| List of Tables |\n| Table 1. Previous incident response life cycle model's phases and corresponding CSF 2.0 Functions.....6 |\n| Table 2."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide?"}, {"role": "assistant", "content": "## NISTIR 8241\n\n## Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs\n\nJulie Haney Mary Theofanos Yasemin Acar Sandra Spickard Prettyman\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8241\n\n\n\n## NISTIR 8241\n\n## Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs\n\nJulie Haney Information Technology Laboratory\n\nMary Theofanos Material Measurement Laboratory\n\nYasemin Acar Leibniz University Hannover\n\nSandra Spickard Prettyman Culture Catalyst, LLC\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8241\n\nDecember 2018\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Undersecretary of Commerce for Standards and Technology\n\n## Abstract\n\nCryptography is an essential component of modern computing. Unfortunately, implementing cryptography correctly is a non-trivial undertaking. Past research studies have supported this observation by revealing a multitude of errors and pitfalls in the cryptographic implementations of software products. However, the emphasis of these studies was on the practices of less-experienced, individual developers. Therefore, there is little understanding of the cryptographic development practices of organizations, including the benefits and challenges of using cryptographic resources such as standards specifications and libraries. To address this gap, a research team led by the National Institute of Standards and Technology (NIST) Information Technology Laboratory Visualization and Usability Group conducted a qualitative investigation into the processes and resources that organizations employ in the development and testing of cryptographic products."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.2.1 Scenario 1: Creation of Verifiable Platform | Artifacts ... 3.2.1 Scenario 1: Creation of Verifiable Platform Artifacts\n\nAn OEM, VAR, or other authoritative source creates a verifiable artifact that binds reference platform attributes to unique, trusted, hardware-based components of the computing device. 3.2.1 ID."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n| Collaborator | Component |\n|----------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| | Provides secure remote access with authentication and authorization support. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n| | Offers secure data storage on-prem. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n\nintegrity-checking, change control management, and user authentication and authorization. The solution was tested in two distinct lab settings: a discrete manufacturing workcell, which represents an assembly line production, and a continuous process control system (PCS), which represents chemical manufacturing industries.\n\nApplication allowlisting; behavioral anomaly detection; file integrity checking; firmware modification; industrial control systems; manufacturing; remote access; software modification; user authentication; user authorization."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 4)"}, {"role": "assistant", "content": "cation security point of view, this requires authentication and authorization policies based on application and service identities in addition to the underlying network parameters and user identities.\nThis in turn requires a platform that consists of Application Programming Interface (API) gateways, sidecar proxies, and application identity infrastructures (e.g., Secure Production Identity Framework for Everyone [SPIFFE]) that can enforce those policies irrespective of the location of the services or applications, whether on-premises or on multiple clouds. The objective of this publication is to provide guidance for realizing an architecture that can enforce granular application-level policies while meeting the runtime requirements of ZTA for multicloud and hybrid environments. ## Keywords\n\negress gateway; identity-tier policies; ingress gateway; microservices; multi-cloud; network-tier policies; service mesh; sidecar proxy; SPIFFE; transit gateway; zero trust; zero trust architecture. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n| 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 |"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe 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. The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.12 (NIST 3.1.12)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.12. 3.1.12."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.12", "cmmc_practice_id": "AC.L2-3.1.12", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Security Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nControlled Unclassified Information; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; nonfederal organizations; nonfederal systems; organization-defined parameter; security assessment; security control; security requirement.\n\n- Federal agencies responsible for managing and protecting CUI\n- Nonfederal organizations responsible for protecting CUI\n- Individuals with system development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Individuals with acquisition or procurement responsibilities (e.g., contracting officers)\n- Individuals with system, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Individuals with security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, analysts, independent verifiers and validators)\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide?"}, {"role": "assistant", "content": "## Proceedings of the Cybersecurity in CyberPhysical Systems Workshop, April 23 - 24, 2012\n\nEditor:\n\nTanya Brewer http://dx.doi.org/10.6028/NIST.IR.7916\n\n\n\nNISTIR 7916\n\n## Proceedings of the Cybersecurity in CyberPhysical Systems Workshop, April 23 - 24, 2012\n\nEditor: Tanya Brewer\n\nComputer Security Division Information Technology Laboratory http://dx.doi.org/10.6028/NIST.IR.7916\n\nFebruary 2013\n\n\n\nU.S. Department of Commerce\n\nRebecca M. Blank, Acting Secretary of Commerce and Deputy Secretary of Commerce\n\nNational Institute of Standards and Technology\n\nPatrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. ## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Management Act (FISMA), Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\n|\n| 3.3 Adoption of International Standards | in SCAP v2 ............................................\n6 |\n| 4 SCAP v2 Development | Plan..................................................................................7 |\n| List of Appendices | List of Appendices |\n| Appendix A-Applications of the SCAP 2.0 Architecture.........................................9 | Appendix A-Applications of the SCAP 2.0 Architecture.........................................9 |\n| A.1 Vulnerability Assessment................................................................................ | 9 |\n| A.2 Configuration Setting Checklist | Assessment ................................................"}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nso develop and maintain procedures for particularly important processes that may be urgently needed during emergency situations, such as redeploying the organization's primary authentication platform.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------|\n| PR.AA (Identity Management, Authentication, and Access Control) | Access to physical and logical assets is limited to authorized users, services, and hardware and managed commensurate with the assessed risk of unauthorized access | Medium | N1: See the notes for PR. |\n| PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed by the organization | Medium | N1: See the notes for PR. |\n| PR.AA-02 | Identities are proofed and bound to credentials based on the context of interactions | Medium | N1: See the notes for PR."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 4)"}, {"role": "assistant", "content": "ganizational stakeholders. - ☐ Develop and implement C-SCRM processes based on the strategy, objectives, policies, and procedures that are agreed upon and performed by the organizational stakeholders.\n- ☐ Establish a cross-organizational mechanism that ensures alignment between functions that contribute to C-SCRM management, such as cybersecurity, IT, legal, human resources, engineering, etc. ## Checklist of actions for Activity 2: Identify your organization's technology suppliers and determine how critical each one is to your organization. - ☐ Develop criteria for supplier criticality based on, for example, the importance of the supplier's products or services to the organization's business, sensitivity of data processed or stored by the supplier, and degree of access to the organization's systems. - ☐ Prioritize suppliers into criticality levels based on the criteria. See NIST IR 8179, Criticality Analysis Process Model: Prioritizing Systems and Components for more information on a structured method for prioritization. - ☐ Keep a record of all suppliers, prioritized based on the criticality criteria. ## NIST CSF 2.0: CYBERSECURITY SUPPLY CHAIN RISK MANAGEMENT (C-SCRM)\n\nA QUICK-START GUIDE\n\n## HOW TO USE THE CSF TO ESTABLISH AND OPERATE A C-SCRM CAPABILITY\n\n\n\n## Checklist of actions for Activity 3: Establish C-SCRM roles and requirements and communicate them within and outside your organization. ## C-SCRM roles and responsibilities:\n\n☐ Identify one or more specific roles or positions that will be responsible and accountable for planning, resourcing, and executing C-SCRM activities. ☐ Document C-SCRM roles and responsibilities in policy. ☐ Create responsibility matrixes (e.g., RACI charts) to document who will be responsible, accountable, consulted, and informed for C-SCRM activities and how those teams and individuals will be consulted and informed."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| 1 | Summary.............................................................................................1 | Summary.............................................................................................1 | Summary.............................................................................................1 | |-----|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | | 1.2 | Solution..........................................................................................................................3 | | | | 1.3 | Benefits..........................................................................................................................4 | | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | | 2.1 | Typographic Conventions..............................................................................................5 | | | 3 | Approach.............................................................................................6 | Approach.............................................................................................6 | | | | 3.1 | Audience........................................................................................................................6 | | | | 3.2 | Scope .............................................................................................................................6 | | | | | 3.2.1 Scenario 1: Creation of Verifiable Platform | Artifacts ..................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.2.4 eyeSight SecureConnector Agent\n\n1."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\npplication identity: The fundamental requirement to enable this is the assignment of a unique identity to each application or service, just like how each user carries a unique identity (e.g., userid).\nPrior to the era of cloud-based applications, the application requests were validated based on the IP subnet or IP address from which they originated. Ubiquitous access and multi-clouds have eliminated the concept of network perimeters. Hence, authentication and authorization based on those parameters are neither feasible nor scalable. Further, the presence of proxies, network address translation, dynamic infrastructure (e.g., migration of applications between VMs), and load balancers make it impossible for the called application to know the IP address of the calling application in order to make authentication or authorization decisions. A unique application identity is inevitable. - Establishment of trust in application identity: The created application (workload or service) identity should not be subject to spoofing and should be continuously verifiable. An example of workload identity is a SPIFFE ID [47]. A SPIFFE ID is a string that uniquely and specifically identifies a workload and encoded as a Uniform Resource Identifier (URI), which takes the following format: spiffe:// trust domain / workload identifier where the workload identifier uniquely identifies a specific workload within a trust domain. The SPIFFE ID is carried in a cryptographically-verifiable document called a SVID (SPIFFE Verifiable Identity Document). The two formats supported for SVID in SPIFFE specification are a short-lived X.509 certificate or a Java Web Token (JWT) token. - Discovery of application resources: There should be a robust secure method for discovering all application resources (e.g., services, networks), called service discovery capability."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\nCryptography is an essential component of modern computing. Unfortunately, implementing cryptography correctly is a non-trivial undertaking. Past research studies have supported this observation by revealing a multitude of errors and pitfalls in the cryptographic implementations of software products. However, the emphasis of these studies was on the practices of less-experienced, individual developers. Therefore, there is little understanding of the cryptographic development practices of organizations, including the benefits and challenges of using cryptographic resources such as standards specifications and libraries. To address this gap, a research team led by the National Institute of Standards and Technology (NIST) Information Technology Laboratory Visualization and Usability Group conducted a qualitative investigation into the processes and resources that organizations employ in the development and testing of cryptographic products. The study involved 21 in-depth interviews of 29 participants representing organizations that develop either a security product that uses cryptography or a non-security product that heavily relies on cryptography. This report categorizes and enumerates a subset of findings that document participant comments specific to NIST cryptographic publications and testing/validation programs, with a goal of informing future decisions of NIST and other standards bodies working in this space. cryptography; development; standards; testing; validation\n\nCryptography is an essential component of modern computing. Unfortunately, implementing cryptography correctly is a non-trivial undertaking. Past research studies have supported this observation by revealing a multitude of errors and developer pitfalls in the cryptographic implementations of software products [1-5]. However, these studies focused on the practices of less-experienced, individual developers."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 2)"}, {"role": "assistant", "content": "lar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-56A Revision 3 Natl. Inst. Stand. Technol. Spec. Publ. 800-56A Rev. 3, 151 pages (April 2018) CODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-56Ar3\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nt of Defense Federal Acquisition Regulation). Organizations can use the assessment procedures to generate evidence to support the assertion that the enhanced security requirements have been satisfied.\nThe assessment procedures are typically used as part of an assessment process. An assessment process is an information-gathering and evidenceproducing activity to determine the effectiveness of the safeguards implemented to meet the set of security requirements specified in [SP 800-172]. The information gathered and evidence produced can be used by an organization to:"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nBlockchain properties improve the security, flexibility, scalability, integrity, and confidentiality of AC data/logs and processes (compared to traditional AC systems) by allowing organizations to verify and audit AC data transactions and processes to track the states of their AC systems hosted on distributed sites [SP162]. - A node is an individual computer system within a blockchain network. It can act as an AC system's entity or organization and is called an AC node within the AC network. AC nodes including lightweight nodes (i.e., a node that does not store or maintain a copy of the blockchain), full nodes (i.e., a node that stores the entire blockchain and ensures that transactions are valid), and publishing nodes (i.e., a full node that also publishes new blocks). Lightweight nodes must pass their transactions to full nodes. Depending on the design of the AC system, AC nodes can act as host servers for AC data (e.g., subject/object attributes, environment conditions, and policy rules) or as administrators for AC policy management and enforcement. - A block contains trustable and tamper-resistant AC data as well as a history of access logs without third parties or centralized management. Distributed blocks solve the single point of failure problem and provide information for distributed architectures, which often involve a much larger set of AC entities or organization. Distributed ownership of blocks is necessary because of possible trust, security, and reliability concerns that are associated with the centralized management of AC enforcement or AC data ownership [IR8202]. - Full blockchain nodes are not only a repository of AC data and logs of blocks but can also store objects."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n| Table of Contents | Table of Contents | Table of Contents |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| TABLE OFCONTENTS.............................................................................................................V | TABLE OFCONTENTS.............................................................................................................V | |\n| LIST OF FIGURES....................................................................................................................VII | LIST OF FIGURES....................................................................................................................VII | |\n| LIST OFTABLES.................................................................................................................... | LIST OFTABLES...................................................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Access Control\n\n## Getting Started with Access Control"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n| 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 |"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.4 (NIST 3.6.4)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.6.4 | Secure Subsystem Approach | 10-11 10-11 |\n| | 3. 3.6.4 Secure Subsystem Approach : TSie idea behind the secure subsystem approach is to have the host operating system environment so configured that only the data management system may be used."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.6.4", "cmmc_practice_id": "IR.L2-3.6.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 2)"}, {"role": "assistant", "content": "aft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-05-17\n\n## How to Cite this NIST Technical Series Publication:\n\nSchaffer K, Mell P, Trinh H, Van Wyk I (2023) Recommendations for Federal Vulnerability Disclosure Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST (Special Publication) NIST SP 800-216."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "|\n| Appendix A. C-SCRM Security Controls...............................................................................................\n| 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n- [1] DARPA (2020) DARPA Selects Teams to Increase Security of Semiconductor Supply Chain. Available at https://www.darpa.mil/news/2020/semiconductor-supply-chainsecurity\n- [2] DARPA (2021) Expanding Domestic Manufacturing of Secure, Custom Chips for Defense Needs. Available at https://www.darpa.mil/news-events/2021-03-18\n- [3] NSWC Crane Corporate Communications (2019) NSWC Crane leverages OTA to ensure that the U.S. Government has access to secure state-of-the-art design, assembly, packaging and test for state-of-the-art microelectronics. Available at https://www.navsea.navy.mil/Media/News/Article/2005099/nswc-crane-leverages-otato-ensure-that-the-us-government-has-access-to-secure/\n- [4] Institute for Systems Research (2020) AFRL-Northrop Grumman: Locked Electronics for Assured Design (LEAD): Delay Locking ASIC IP Blocks to Protect Functionality. Available at https://isr.umd.edu/research-funding/afrl-northrop-grumman-locked-electronicsassured-design-lead-delay-locking-asic-ip\n- [5] Wolfe F (2020) Aether Spy Next-Generation Multi-Function Radar to Advance, Northrop Grumman Says. Defense Daily . Available at https://www.defensedaily.com/aether-spynext-generation-multi-function-radar-advance-northrop-grumman-says/air-force/\n- [6] CISA (2020) Defining Insider Threats. Available at https://www.cisa.gov/topics/physicalsecurity/insider-threat-mitigation/defining-insider-threats\n- [7] Areno M (2020) Supply chain threats against integrated circuits. Intel Whitepaper . Available at https://www.intel.com/content/dam/www/centrallibraries/us/en/documents/2022-08/supply-chain-threats-against-integrated-circuitswhitepaper-july2020.pdf\n- [8] Evernex (2024) EOL Meaning: What Does End of Life Mean for Your Hardware? Available at https://evernex.com/industry-guide/eol-meaning/\n- [9] Vincent J (2018) Chinese spies reportedly inserted microchips into servers used by Apple, Amazon, and others."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 6)"}, {"role": "assistant", "content": "chnology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## HOW TO USE THIS PUBLICATION\n\nThis publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice PE.L2-3.10.1 (NIST 3.10.1)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.10.1. 3.10.1."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.10.1", "cmmc_practice_id": "PE.L2-3.10.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| ...................................................................................................\n3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 4)"}, {"role": "assistant", "content": "00-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171.\nNIST 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. \n\nNIST SP 800-172A, Assessing Enhanced Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the enhanced security requirements in SP 800-172. ## A is for Assessment\n\nKnowing what requirements to implement is important, but it is also important to understand how to evaluate the organization's implementation. Both publications work handin-hand for full implementation. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas\n\n\n\nified-information\n\nProtecting information from unauthorized modification\n\n## Key Term: Security Requirement\n\n[SP 800-171] Security Requirement: Security outcomes levied on a nonfederal organization to ensure adequate measures are taken to protect the confidentiality of CUI being processed, stored, or transmitted. \n\n\n\nImportant Note: The security requirements in NIST SP 800-171 are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. Protecting information from unauthorized access and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 7)"}, {"role": "assistant", "content": "of the Computer on Controls | Impact of the Computer on Controls | 10 | | | 1.3.2 | Internal Control and Computer Security Review Policy | Internal Control and Computer Security Review Policy | 11 | | 1.4 | EVIDENCE IN AUTOMATED SYSTEMS | EVIDENCE IN AUTOMATED SYSTEMS | EVIDENCE IN AUTOMATED SYSTEMS | 14 | | 1.5 | AIS AUDITABILITY | AIS AUDITABILITY | AIS AUDITABILITY | 15 | | CHAPTER 2 | CHAPTER 2 | CHAPTER 2 | CHAPTER 2 | | | AIS LIFE CYCLE | CONSIDERATIONS | CONSIDERATIONS | CONSIDERATIONS | 16 | | 2.1 | BACKGROUND | BACKGROUND | BACKGROUND | 16 | |-------|------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|------| | | 2.1.1 | PCIE - EDP Systems Review and Security Work Group | PCIE - EDP Systems Review and Security Work Group | 16 | | | 2.1.2 | System Development Life Cycle | System Development Life Cycle | 16 | | 2.2 | OPERATING ENVIRONMENT | OPERATING ENVIRONMENT | OPERATING ENVIRONMENT | 17 | | | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 17 | | | 2.2.1.1"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Device Configuration : The configuration of the IoT device's software can be changed, and such changes can be performed by authorized entities only."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Developing Security Plans for Federal Information Systems provide? (Part 10)"}, {"role": "assistant", "content": "|\n| 3.16 ONGOING SYSTEM SECURITY PLAN MAINTENANCE ..............................................................\n| 26 |\n| APPENDIX A: SAMPLE INFORMATION SYSTEM SECURITY PLAN TEMPLATE...... 27 | APPENDIX A: SAMPLE INFORMATION SYSTEM SECURITY PLAN TEMPLATE...... 27 |\n| APPENDIX B: GLOSSARY.......................................................................................................... 31 | APPENDIX B: GLOSSARY.......................................................................................................... 31 |\n| APPENDIX C: REFERENCES..................................................................................................... 41 | APPENDIX C: REFERENCES..................................................................................................... 41 |\n\nvi\n\n## Executive Summary\n\nThe objective of system security planning is to improve protection of information system resources. All federal systems have some level of sensitivity and require protection as part of good management practice. The protection of a system must be documented in a system security plan. The completion of system security plans is a requirement of the Office of Management and Budget (OMB) Circular A-130, 'Management of Federal Information Resources,' Appendix III, 'Security of Federal Automated Information Resources,' and' Title III of the E-Government Act, entitled the Federal Information Security Management Act (FISMA). The purpose of the system security plan is to provide an overview of the security requirements of the system and describe the controls in place or planned for meeting those requirements."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication describes the Risk Management Framework (RMF) and provides guidelines for applying the RMF to information systems and organizations. The RMF provides a disciplined, structured, and flexible process for managing security and privacy risk that includes information security categorization; control selection, implementation, and assessment; system and common control authorizations; and continuous monitoring. The RMF includes activities to prepare organizations to execute the framework at appropriate risk management levels. The RMF also promotes near real-time risk management and ongoing information system and common control authorization through the implementation of continuous monitoring processes; provides senior leaders and executives with the necessary information to make efficient, cost-effective, risk management decisions about the systems supporting their missions and business functions; and incorporates security and privacy into the system development life cycle. Executing the RMF tasks links essential risk management processes at the system level to risk management processes at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 2)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 8)"}, {"role": "assistant", "content": "| Time Spent on Security Awareness .............................................................................\n| 9 |\n| 3.2 ORGANIZATIONS ................................................................................................................ 10 | 3.2 ORGANIZATIONS ................................................................................................................ 10 | 3.2 ORGANIZATIONS ................................................................................................................ 10 |\n| 3.2.1 | Organization Type .................................................................................................... | 10 |\n| 3.2.2 | Organization Size...................................................................................................... | 11 |\n| 3.3 SECURITY AWARENESS PROGRAMS ................................................................................... | 3.3 SECURITY AWARENESS PROGRAMS ..................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n. . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . .\n. . . | 14 |\n| 3.4. | SIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 16 |\n| 4. Conclusion . . | . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| References . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms | . | 26 |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | 2 |\n| Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | 4 |\n| Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | 6 |\n| Table 4. Performance of HQC in thousands of cycles on x86_64 [1] . . . | Table 4."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.3.3 | Gather Phase Status | 81 |\n| | 4. 3.3.3 Gather Information on the Initiation Phase Status - The auditor should obtain and review the following Initiation Phase documents:\n1."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 5)"}, {"role": "assistant", "content": "d government training and guidance that allow customization for the unique needs of each organization. - Automation was viewed as essential for efficient tracking of employees' completion of training.\nHowever, some organizations lacked this automation, especially when tracking contractors, who may not have access to organizations' learning management systems. - When dealing with individuals who do not complete their training by the deadline, many organizations disabled accounts of non-compliant employees, resulting in higher compliance numbers. Still, almost half (47%) said that getting employees to complete the required training was challenging, largely because employees were busy or disinterested. ## Security Awareness Approaches\n\n- In addition to the required annual training, 79% of surveyed programs held a variety of security awareness activities throughout the year, such as speaker events, instructor-led sessions, webinars, and interactive activities like escape rooms. Smaller programs were less likely to offer additional activities. - Programs often disseminated information that employees could use in both their work and personal lives, which was viewed as important for establishing consistent security habits. They have also recently introduced more topics relevant to teleworking. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n- Programs utilized a wide range of other communication channels, such as email, newsletters, posters, and videos. However, 56% of surveyed programs had difficulty providing security awareness information in an engaging way, 47% experienced challenges customizing security awareness information to a diverse workforce, and 40% struggle with ensuring materials are Section 508 compliant, especially when utilizing interactive approaches."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. Mobile device forensics is the science of recovering digital evidence from a mobile device under forensically sound conditions using accepted methods. Mobile device forensics is an evolving specialty in the field of digital forensics. This guide attempts to bridge the gap by providing an indepth look into mobile devices and explaining technologies involved and their relationship to forensic procedures."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 7)"}, {"role": "assistant", "content": "es the use of all other security functions. ## Approved security functions\n\nFor the current list of CMVP-approved security functions, see https://csrc.nist.gov/projects/cmvp/sp800-140c. ## Appendix A.\nDocument Revisions\n\n| Edition | Date | Change |\n|-----------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Revision 1 (r1) | May 2022 | 6.2 Approved security functions Added/Modified: Security function subsection headers. Added: SP 800-90A and SP 800-90B 6.2.1 Transitions Removed: SP 800-131Ar2 section references 6.2.3 Digital Signature Added: SP 800-208, October 2020 6.2.9 Other Security Functions Added: SP 800-140Dr1, May 2022 |\n| Revision 2 (r2) | July 2023 | 6.2 Approved security functions Removed: All subsections. Added: Reference to a CMVP web link that includes the CMVP-approved security functions. Future modifications to the list will be made on that website, minimizing the need to revise this publication. |"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Karen Scarfone Matthew Smith\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\n\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Applied Cybersecurity Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nMatthew Smith Huntington Ingalls Industries Annapolis Junction, MD\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nMay 2020\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259A 23 pages (May 2020)\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 7)"}, {"role": "assistant", "content": "communication networks, timing, and cybersecurity. ITL's Computer Security Division (CSD) has provided leadership and expertise to the Smart Grid Interoperability Panel's Cyber Security Working Group.\nLeveraging our broad expertise in relevant areas, we are now looking at the broader landscape of cyber-physical systems, and how cybersecurity fits into that landscape. CSD hosted a two-day workshop to explore CPS cybersecurity needs, with a focus on research results and real-world deployment experiences. On the first day, speakers addressed CPS across multiple sectors of industry (e.g., automotive, healthcare, semi-conductor manufacturing). The second day focused on cyber security needs of CPS in the electric smart grid. This document provides abstracts and corresponding slides from the plenary presentations at the workshop. 3\n\n1 For more information on this definition, please see George Arnold's slides from the workshop. 2 Performance metrics include safety and security, reliability, agility and stability, efficiency and sustainability. 3 The website for the event is at http://www.nist.gov/itl/csd/cyberphysical-workshop.cfm, and the agenda is available at http://csrc.nist.gov/news\\_events/cps-workshop/cps-workshop-agenda\\_04-03-2012.pdf. The agenda document has links to electronic copies of the abstracts and slides. ## 2. Opening Remarks\n\nGeorge W. Arnold, DESc National Coordinator, Smart Grid Interoperability Director, Cyber-Physical Systems Engineering Laboratory NIST\n\nDr. Arnold joined the National Institute of Standards and Technology (NIST) in September 2006 as Deputy Director, Technology Services, after a 33-year career in the telecommunications and information technology industry. He was appointed National Coordinator for Smart Grid Interoperability at in April 2009. He has been responsible for leading the development of standards underpinning the nation's Smart Grid. In October 2011, Dr."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nAny vulnerability of a blockchain AC system on the level of the entire system or an underlying function of a smart contract can be hacked (e.g., reentrancy vulnerability) or misused. For instance, the publicly available smart contract's byte code might generate erroneous system state data that will be securely logged on the blockchain. The only way to fix errors is to delete, correct, and redeploy the entire smart contract. Thus, it is necessary for smart contracts to be correctly deployed (i.e., they work as intended by the developer and cannot be exploited by attackers).\n\nProtocol of the consensus mechanism is another security concern of vulnerability. For example, PoS mechanisms are vulnerable to attacks such as nothing-at-stake, grinding, long-range, and stake bleeding attacks. PoW and PoS mechanisms may cause low throughput and long transaction confirmation delay, leading to weak consistency problems because an AC process cannot be finalized until its block reaches a certain depth in the blockchain. These might degrade the performance of AC process, so consistency - including common-prefix, chain growth, and chain quality properties of the consensus mechanism - needs to be considered [PDA]."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nProvides the national system of physical and chemical measurement; coordinates the system with measurement systems of other nations and furnishes essential services leading to accurate and uniform physical and chemical measurement throughout the Nation's scientific community, industry, and commerce; provides advisory and research services to other Government agencies; conducts physical and chemical research; develops, produces, and distributes Standard Reference Materials; provides calibration services; and manages the National Standard Reference Data System. The Laboratory consists of the following centers:\n\nThe two elements that generate the risks in a computerized environment are its unique vulnerabilities and its unique set of threats. A vulnerability is a weakness or flaw in a computer-based system that may be exploited by a threat to cause destruction or misuse of its assets or resources. Threats can be physical (e.g., fire, water damage, earthquakes, and hurricanes) or people-oriented (e.g., errors, omissions, intentional acts ofviolence, and fraud). When a threat materializes and takes advantage of a system's vulnerabilities, a damaging event occurs that causes a loss. The risk of damaging events cannot be totally eliminated, but the use of controls on vulnerabilities and/or threats can reduce such risks to an acceptable level. 4. Ineffective Security Practices for the AppHcation - Inadequate manual checks and controls to ensure correct processing by the ADP system, or negligence by those responsible for carrying out these checks, result in many vulnerabilities. 5. Procedural Errors Within the ADP Facility - Both errors and intentional acts committed by the ADP operations staff may result in improper operational procedures, lapsed controls, and losses in storage media and output. 6."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.5.4 | Discretionary Audits | Discretionary Audits | 60 |\n| 3. 3.5.4 Discretionary Audits\n\nAfter the systems have been identified and ranked, using the risk based evaluation, several back-end qualifiers must be considered by the auditor in determining how many discretionary audits can be added to the audit plan (See Figure 3)."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.5.4", "cmmc_practice_id": "IA.L2-3.5.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 7)"}, {"role": "assistant", "content": "ce. Help the NCCoE make this guide better by sharing your thoughts with us as you read the guide. If you adopt this solution for your own organization, please share your experience and advice with us.\nWe recognize that technical solutions alone will not fully enable the benefits of our prototype solution, so we encourage organizations to share lessons learned and best practices for integrating the C-SCRM processes associated with implementing this guide. To provide comments, join the community of interest, or learn more about the project and example implementation, contact the NCCoE at supplychain-nccoe@nist.gov. ## COLLABORATORS\n\nCollaborators participating in this project submitted their capabilities in response to an open call in the Federal Register for all sources of relevant security capabilities from academia and industry (vendors and integrators). Those respondents with relevant capabilities or product components signed a Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to build this example solution. Certain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. ## NIST SPECIAL PUBLICATION 1800-34B\n\n## Validating the Integrity of Computing Devices\n\n## Volume B:\n\nApproach, Architecture, and Security Characteristics\n\nTyler Diamond* Nakia Grayson William T."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 7)"}, {"role": "assistant", "content": "e first round. NIST\nwould not be able to select additional post-quantum digital signature algorithms for standardization\nwithout the combined efforts of these individuals and the algorithm submitters.\nThe authors of this report are also appreciative of the efforts by other members of NIST’s PQC team\nwho reviewed candidate algorithms, analyses, and public comments; performed testing; provided\ntechnical and administrative support; and participated in numerous meetings to discuss the se-\nlection of the second-round candidates. They are Zuzana Bajcsy, Larry Bassham, Lily Chen, Morris\nDworkin, Sara Kerman, and Andrew Regenscheid. iv\n\n\fNIST IR 8528\nOctober 2024\n\n1. Introduction\n\nAdditional Digital Signatures\nFirst Round Status Report\n\nThe National Institute of Standards and Technology (NIST) initiated the public Post-Quantum\nCryptography (PQC) Standardization Process in December 2016 to select quantum-resistant\npublic-key cryptographic algorithms for standardization in response to the substantial de-\nvelopment and advancement of quantum computing. After three rounds of evaluation and\nanalysis, NIST announced the selection of the first algorithms to be standardized [1]. The\npublic-key encapsulation mechanism (KEM) selected for standardization was CRYSTALS-\nKyber (ML-KEM). The digital signatures selected were CRYSTALS-Dilithium (ML-DSA), Falcon\n(FN-DSA), and SPHINCS+ (SLH-DSA). Except for SPHINCS+, all of these schemes are based\non the computational hardness of problems that involve structured lattices. While several\nnon-lattice-based KEMs remained under consideration in the fourth round, no signature\nschemes remained. In July 2022, NIST called for additional digital signature proposals to be considered in the\nPQC standardization process to diversify its post-quantum signature portfolio."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Configuration Management?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nFagan M, Megas KN, Watrobski P, Marron J, Cuthill B (2022) Profile of the IoT Core Baseline for Consumer IoT Products. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8425. https://doi.org/10.6028/NIST.IR.8425"}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 7)"}, {"role": "assistant", "content": "| AUDIENCEAND ASSUMPTIONS ..........................................................................................\n| 1 |\n| 1.3 | DOCUMENT STRUCTURE.................................................................................................... | 1 |\n| 2. BACKGROUND.................................................................................................................... | 2. BACKGROUND.................................................................................................................... | 3 |\n| 2.1 | MOBILE DEVICE CHARACTERISTICS ................................................................................. | 3 |\n| 2.2 | MEMORY CONSIDERATIONS .............................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nassessment; assessment method; assessment object; assessment procedure; assurance; enhanced security requirement; enhanced security requirement assessment; Controlled Unclassified Information; coverage; CUI Registry; depth; Executive Order 13556; FISMA; NIST Special Publication 800-53; NIST Special Publication 800-53A; NIST Special Publication 800-171; NIST Special Publication 800-172; NIST Special Publication 800-172A; nonfederal organization; nonfederal system; security assessment; security control. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nRequirements Document | 41 | | | | 2.6.8.1 | | | | | 2.6.8.2 Functional Security and Internal Control Requirements | 2.6.8.2 Functional Security and Internal Control Requirements | 2.6.8.2 Functional Security and Internal Control Requirements | | | | | Document | Document | 42 | | | | 2.6.8.3 Data Requirements Document | 2.6.8.3 Data Requirements Document | 42 | | | | 2.6.8.4 Data Sensitivity/Criticality Description | 2.6.8.4 Data Sensitivity/Criticality Description | 42 | | | 2.6.9 | Specifications Documents | Specifications Documents | 42 | | | 2.6.9.1 | | System/Subsystem, Program and Data Base Specifications | 42 | | | 2.6.9.2 | Security and Internal Control Related Specifications | Security and Internal Control Related Specifications | 43 | | | 2.6.10 | Validation, Verification and Testing Plan and Specifications | Validation, Verification and Testing Plan and Specifications | 43 | | | 2.6.11 | User Manual | User Manual | 44 | | | 2.6.12 | Operations/Maintenance Manual | Operations/Maintenance Manual | 44 | | | 2.6.13 | Installation and Conversion Plan | Installation and Conversion Plan | 44 | | | 2.6.14 | Test Analysis and Security Evaluation Report | Test Analysis and"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide?"}, {"role": "assistant", "content": "NIST Internal Report\nNIST IR 8528\nStatus Report on the First Round of the\nAdditional Digital Signature Schemes for\nthe NIST Post-Quantum Cryptography\nStandardization Process\n\nGorjan Alagic\nMaxime Bros\nPierre Ciadoux\nDavid Cooper\nQuynh Dang\nThinh Dang\nJohn Kelsey\nJacob Lichtinger\nYi-Kai Liu\nCarl Miller\nDustin Moody\nRene Peralta\nRay Perlner\nAngela Robinson\nHamilton Silberg\nDaniel Smith-Tone\nNoah Waller\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.IR.8528\n\n\fNIST Internal Report\nNIST IR 8528\n\nStatus Report on the First Round of the\nAdditional Digital Signature Schemes for\nthe NIST Post-Quantum Cryptography\nStandardization Process\n\nGorjan Alagic\nMaxime Bros\nPierre Ciadoux\nDavid Cooper\nQuynh Dang\nThinh Dang\nJohn Kelsey\nJacob Lichtinger\n\nCarl Miller\nDustin Moody\nRene Peralta\nRay Perlner\nAngela Robinson\nHamilton Silberg\nDaniel Smith-Tone\nNoah Waller\nComputer Security Division\nInformation Technology Laboratory\n\nYi-Kai Liu\nApplied and Computational Mathematics Division\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.IR.8528\n\nOctober 2024\n\nNational Institute of Standards and Technology\nLaurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nU.S. Department of Commerce\nGina M. Raimondo, Secretary\n\n\fCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in\nthis paper in order to specify the experimental procedure adequately. Such identification does not imply\nrecommendation or endorsement of any product or service by NIST, nor does it imply that the materials or\nequipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 5)"}, {"role": "assistant", "content": "ryption; passive inspection; protocol; Transport Layer Security (TLS); visibility. ## ACKNOWLEDGMENTS\n\nWe are grateful to the following individuals for their generous contribu�ons of exper�se and �me.\n| Name | Organization |\n|---------------------------|-----------------------------------|\n| Ravishankar Chamarajnagar | AppViewX |\n| Michael Ackermann | Blue Cross Blue Shield |\n| Jonathan Chen | F5 |\n| Ryan Johnson | F5 |\n| Brad Otlin | F5 |\n| Kevin Stewart | F5 |\n| Nanjaiah Vijayalakshmi | NETSCOUT Corporation |\n| Gina Scinta | Thales Trusted Cyber Technologies |\n| Lauren Brown | JPMorgan Chase& Company |\n\nThe Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register. Respondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution. We worked with:\n\n| Technology Partner/Collaborator | Build Involvement |\n|-----------------------------------|-----------------------------------|\n| AppViewX | NETSCOUT Corporation |\n| DigiCert | Not for Radio LLC |\n| F5 | Thales Trusted Cyber Technologies |\n| JPMorgan Chase& Company | U.S. Bank Corporation |\n\n| Technology Partner/Collaborator | Build Involvement |\n|-----------------------------------|---------------------|\n| Mira Security, Inc."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\n|\n| 2. | Fundamental Theories .....................................................................................................\n| 4 |\n| 2.1. | Elliptic Curve | .............................................................................................................. 4 |\n| 2.2. | Elliptic-Curve Cryptography ........................................................................................ | 5 |\n| 2.3. | Bilinear Pair Mapping.................................................................................................. | 7 |\n| 2.4. | Bilinear Pairing for Cryptography................................................................................ | 9 |\n| 3. | Identity-Based Encryption ..............................................................................................11 | |\n| 4. | Attribute-Based Encryption............................................................................................13 | |\n| 4.1."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThis publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, 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. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nMegas K, Fagan M, Cuthill B, Hoehn N, and Petrella E (2025) Summary Report for 'Workshop on Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562. https://doi.org/10.6028/NIST.IR.8562"}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.8 (NIST 3.1.8)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.8. 3.1.8."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.8", "cmmc_practice_id": "AC.L2-3.1.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The NIST team developed a series of Product Data Cards to support the Design-A-Thon. These cards served as the prompts for teams to design approaches for cybersecurity education and awareness related to the products described on the cards. Each of the Product Data Cards featured a mock IoT product and fictional information about the product, its development, and supported cybersecurity. Each card contained the following information:\n\nThis section presents observations and takeaways from the event and teams' designs that were generated after the event and can inform future research and standardization efforts. All three teams identified different approaches in their plans, showing the wide range of tools and concepts that can be used for cybersecurity education and awareness for IoT products. As teams discussed and identified their plans, they found that standardization of available approaches and selection of appropriate approaches could help increase the speed of material development. All teams deeply considered the expected customers of each product to ensure awareness and education approaches were adequately tailored. Teams indicated that any standardization effort should similarly be human-centric and consider the spectrum of potential users of a given application or product."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nThe following are the references used in Table 1: - o AGELIGHT : AgeLight Digital Trust Advisory Group, 'IoT Safety Architecture & Risk Toolkit (IoTSA) v3.1' [5] - o BITAG : Broadband Internet Technical Advisory Group (BITAG), 'Internet of Things (IoT) Security and Privacy Recommendations' [6] - o CSA : Cloud Security Alliance (CSA) IoT Working Group, 'Identity and Access Management for the Internet of Things' [7] - o CSDE : Council to Secure the Digital Economy (CSDE), 'The C2 Consensus on IoT Device Security Baseline Capabilities' [8] - o CTIA : CTIA, 'CTIA Cybersecurity Certification Test Plan for IoT Devices, Version 1.0.1' [9] | Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Device Identification : The IoT device can be uniquely identified logically and physically."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n| 2.2.1. Security . . . . . . . . . . . . . . . . . . . . . .\n| 4 |\n| | 2.2.2.Cost and Performance . . . . . . . . . . . . . | 5 |\n| | 2.2.3.Algorithm and Implementation Characteristics | 8 |\n| 2.3. | Selection of the Candidates for Standardization . . . | 8 |\n| 3. Summary of the Fourth-Round Candidates . | . . . . . . . . | 10 |\n| 3.1. | HQC . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . . . . . | 14 |\n| 3.4. | SIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 16 |\n| 4. Conclusion . . | . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| References . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms | ."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Data Structure for Integrity Protection with Erasure Capability provide? (Part 3)"}, {"role": "assistant", "content": "contain a single record or multiple transactions. Every row or column is terminated with a block containing a hash of that row or column (e.g., H 0 , -is the hash of row 0).\nVarious forms of the hash structure are also possible. For example, the hash value can be stored in the last block of the row or column instead of a separate hash block. Another alternative is to concatenate hashes of each block in a row or column, similar to the blockchain process. The hash of this concatenation would then serve as the hash value for that row or column. Figure 1. Basic block matrix\n\n\n\nAs an example of the process, the block labeled 'X' may be deleted by writing all zeroes to that block, or revised with different values. Either of these changes will affect the hash values of H 3 , -and H -, 2 for row 3 and column 2. However, the integrity of all blocks except the one containing 'X' is still ensured by the other hash values. That is, other blocks of row 3 are included in the hashes for columns 0, 1, 3, and 4. Similarly, other blocks of column 2 are included in the hashes for rows 0, 1, 2, and 4. Thus, the integrity of blocks that have not been deleted is assured. An algorithm to maintain this structure is given below and its properties described. Within the data structure, blocks are numbered 1 ..k , and are added to the data structure starting with cell 0 , 1 . (It is desirable to keep cells on the diagonal null, for reasons explained later.) Variables i, j are column indices, and swap ( i, j ) exchanges the values of i and j , i.e., i ′ = j and j ′ = i . With this algorithm, cells are filled as shown in Algorithm 1. ## Algorithm 1 Data block matrix construction\n\nFigure 2. Block matrix with numbered cells\n\n\n\n## III. PROPERTIES\n\nCertain desirable properties are maintained with this data structure."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n| | INTRODUCTION................................................................................................................. 1 | INTRODUCTION................................................................................................................. 1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | STUDY METHODOLOGY................................................................................................. 2 | STUDY METHODOLOGY................................................................................................. 2 |\n| 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 | 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 | 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 |\n| 2.1.1 | Focus Group Design..................................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\n- I. All data sources and computing services are considered resources. An enterprise relies on different resources to perform its mission: mobile devices, data stores, compute resources (including virtual), remote sensors/actuators, etc. All these components are resources and need to be considered in a ZTA. Some components (e.g., IoT sensors) may not be able to support some solutions such as configuration agents, application sandboxing, etc. so compensating technologies or alternative mitigations may be needed. If the resource lacks certain security capabilities, the enterprise may need to add a PEP component to provide that functionality. - II. The enterprise monitors and measures the integrity and security posture of all owned and associated resources. This tenet deals with the aspects of cyber hygiene for both enterprise-owned resources and those that may not be owned, but used in an enterprise workflow such as configuration, patching, application loading, etc. The state of resources should be monitored, and appropriate action taken when new information such as a new vulnerability or attack is reported or observed. The confidentiality and integrity of data on the resource should be protected. This requires enterprise admins to know how resources are configured, maintained, and monitored. Moving to a zero trust architecture will likely never start from scratch but will involve a series of upgrades and changes over time. Some changes may be simple configuration changes, and some may involve the purchase and deployment of new infrastructure; it all depends on what tools are currently used and available to the enterprise. This step also does not change in a zero trust planning process. The baseline controls for LOW, MODERATE and HIGH-impact systems are listed in NIST SP 800-53B [10]."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.4.3. 3.4.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe 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. The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n| Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | |\n|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ...................................................................................................................... | 1. Introduction ...................................................................................................................... | 1. Introduction ......................................................................................................................"}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 4-15 |\n| 5.6 | System Testing | 4-15 |\n| 5.7 6.\n| Conversion | 4-16 |\n| | INTERNAL CONTROL | 4-16 |\n| 6.1 | General | 4-16 4-16 |\n| 6.2 | Control Policies | 4-17 |\n| 6.3 7. | Control Procedures HARDWARE SUPPORT | 4-17 |\n| 7.1 | General | 4-17 |\n| 7.2 | Introduction | 4-17 |\n| 7.3 | Control Policies | 4-18 |\n| | BIBLIOGRAPHY | 4-19 |\n| 8. | | |\n| PART V: | SESSION 3 - MANAGERIAL AND ORGANIZATIONAL VULNERABILITIES AND CONTROLS - LINE LEVEL - GENERAL | 5-1 |\n| EDITOR'S 1. | NOTE INTRODUCTION | 5-2 5-3 |\n| 2."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.2. 3.1.2. 3.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.8. Artificial Intelligence and Machine Learning in Identity Systems\n\n– The IdP is provisioned either directly by the CSP or indirectly through\naccess to attributes of the subscriber account. The CSP maintains the\nsubscriber account, its status, and the enrollment data collected in\naccordance with the records retention and disposal requirements described\nin Sec. 3.1 of [SP800-63A]. The subscriber maintains their authenticators. The\nIdP maintains its view of the subscriber account, any federated identifiers\nassigned to the subscriber account, and any policies and decisions regarding\nthe release of attributes and information to RPs.\n\n3.8. Artificial Intelligence and Machine Learning in Identity Systems\nIdentity solutions use artificial intelligence (AI) and machine learning (ML) in various\nways, such as improving the performance of biometric matching systems, automating\nevidence or attribute validation, detecting fraud, and even assisting users (e.g.,\nchatbots). While the potential applications of AI and ML are extensive, these\ntechnologies may also introduce new risks or produce unintended negative outcomes."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| Chapter 1."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.5.2 | Training... 3.5.2 Training\n\nTraining for personnel with contingency plan responsibilities should focus on familiarizing them with ISCP roles and teaching skills necessary to accomplish those roles."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n| 5.2.1 | Scenario 1: Protect Host from Malware Infection via USB..................................... | 37 |\n|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| 5.2.2 | Scenario 2: Protect Host from Malware Infection via Network Vector.................. | 37 |\n| 5.2.3 | Scenario 3: Protect Host from Malware via Remote Access Connections ............. | 39 |\n| 5.2.4 | Scenario 4: Protect Host from Unauthorized Application Installation ................... | 40 |\n| 5.2.5 | Scenario 5: Protect from Unauthorized Addition of a Device ................................ | 42 |\n| 5.2.6 | Scenario 6: Detect Unauthorized Device-to-Device Communications................... | 43 |\n| 5.2.7 | Scenario 7: Protect from Unauthorized Deletion of Files....................................... | 43 |\n| 5.2.8 | Scenario 8: Detect Unauthorized Modification of PLC Logic.................................. | 45 |\n| 5.2.9 | Scenario 9: Protect from Modification of Historian Data....................................... | 46 |\n| 5.3.1 | PR.AC-1: Identities and Credentials are Issued, Managed, Verified, Revoked, and Audited for Authorized Devices, Users, and Processes........................ | 50 |\n| 5.3.2 | PR.AC-3: Remote Access is Managed ..................................................................... | 50 |\n| 5.3.3 | PR.AC-4: Access Permissions and Authorizations are Managed, Incorporating the Principles of Least Privilege and Separation of Duties ........................."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nThe Tenable.OT (Version 3.8.17) appliance is installed in a rack with network connections for the Management/Query traffic on Port 1 and SPAN traffic on Port 2 of the appliance. Documentation for Tenable.OT is available at https://docs.tenable.com/Tenableot.htm."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication describes the Risk Management Framework (RMF) and provides guidelines for applying the RMF to information systems and organizations. The RMF provides a disciplined, structured, and flexible process for managing security and privacy risk that includes information security categorization; control selection, implementation, and assessment; system and common control authorizations; and continuous monitoring. The RMF includes activities to prepare organizations to execute the framework at appropriate risk management levels. The RMF also promotes near real-time risk management and ongoing information system and common control authorization through the implementation of continuous monitoring processes; provides senior leaders and executives with the necessary information to make efficient, cost-effective, risk management decisions about the systems supporting their missions and business functions; and incorporates security and privacy into the system development life cycle. Executing the RMF tasks links essential risk management processes at the system level to risk management processes at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n3.2.1. 3.2.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n- Securely Provision (SP): Risk Management (RSK), Software Development (DEV), Systems Requirements Planning (SRP), Test and Evaluation (TST), Systems Development (SYS) - Operate and Maintain (OM): Systems Analysis (ANA) - Oversee and Govern (OV): Training, Education, and Awareness (TEA); Cybersecurity Management (MGT); Executive Cyber Leadership (EXL); Program/Project Management (PMA) and Acquisition - Protect and Defend (PR): Incident Response (CIR), Vulnerability Assessment and Management (VAM) - Analyze (AN): Threat Analysis (TWA), Exploitation Analysis (EXP) | Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.2.4, 3. 3.2.4, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n3.1.1. 3.1.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 9)"}, {"role": "assistant", "content": "nts with respect to the Additional Digital Signatures\nfor the NIST PQC Standardization Process to date. 1\n\n\fNIST IR 8528\nOctober 2024\n\nAdditional Digital Signatures\nFirst Round Status Report\n\nTable 1.\nTimeline of the Additional Digital Signatures for the NIST PQC Standardization\nProcess\n\nDate\nJuly 2022\n\nSeptember 2022\n\nJune 2023\n\nJuly 2023\n\nApril 2024\n\nOctober 2024\n\nEvent\nNIST announced a forthcoming Call for Proposals for Additional\nDigital Signatures to diversify its portfolio [1]. The Call for Proposals for Additional Digital Signatures was pub-\nlished, outlining the submission requirements and evaluation cri-\nteria [2]. Submission deadline for the Additional Digital Signatures pro-\ncess. NIST announced 40 First-Round candidates. The public comment\nperiod for the first-round candidates began. The Fifth NIST PQC Standardization Conference was held in\nRockville, Maryland. Submission teams presented posters for\ntheir candidate algorithms. NIST announced 14 Second-Round candidates. NIST IR 8528, Sta-\ntus Report on the First Round of the Additional Digital Signature\nSchemes for the NIST Post-Quantum Cryptography Standardiza-\ntion Process, was released. The public comment period for the\nsecond-round candidates began. 1.1. Purpose and Organization of This Document\n\nThe purpose of this document is to report on the first round of the NIST PQC Standardiza-\ntion Process. Section 2 enumerates the candidates that were included in the first round. It also describes\nthe evaluation criteria and selection process used to ultimately select the second-round\ncandidates. Section 3 summarizes each of the second-round candidates with a brief description of the\nalgorithm, the properties of interest, and characteristics that might cause some concern. This report focuses on the reasons why candidate algorithms were selected rather than\nproviding detailed justifications for why candidate algorithms were not selected."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 4)"}, {"role": "assistant", "content": "Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96].\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThis publication describes the Risk Management Framework (RMF) and provides guidelines for applying the RMF to information systems and organizations. The RMF provides a disciplined, structured, and flexible process for managing security and privacy risk that includes information security categorization; control selection, implementation, and assessment; system and common control authorizations; and continuous monitoring. The RMF includes activities to prepare organizations to execute the framework at appropriate risk management levels."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy.\n\nThe criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nIn an open-ended question, we also asked what other job functions or roles the participants had in addition to their security awareness responsibilities. All but two participants had other substantial cybersecurity duties beyond awareness training, for example, incident response, supply chain risk management, audits and compliance, policy, information systems security management, privacy awareness and training, cybersecurity role-based training, and project management.\n\n'I think you need someone who is able to converse with network engineers, incident response teams, and when those people start talking about like FIPS [Federal Information Processing Standards] encryption or cloud infrastructure or something like that.' (S06)\n\n'We have one annual course, and we've bundled a lot of training requirements in this one course. It's security awareness, privacy, incident response, rules of behavior, all these things in one course.' (S06)"}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................4 |\n| 2. HIPAA Security Rule .......................................................................................................................9 |\n| 3. Risk Assessment Guidance............................................................................................................14 |\n| 4. Risk Management Guidance .........................................................................................................24 |\n| 5. Considerations When Implementing the HIPAA Security Rule........................................................28 |\n| 5.1.2. Assigned Security Responsibility (§ 164.308(a)(2)) ....................................................................35 |\n| 5.1.3. Workforce Security (§ 164.308(a)(3)).........................................................................................36 |\n| 5.1.4. Information Access Management (§ 164.308(a)(4)) ..................................................................38 |\n| 5.1.5. Security Awareness and Training (§ 164.308(a)(5)) ...................................................................41 |\n| 5.1.6. Security Incident Procedures (§ 164.308(a)(6)) .........................................................................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nThe types of software available for mobile device examination include commercial and open source forensic tools, as well as non-forensic tools intended for device management, testing, and diagnostics. Forensic tools are typically designed to acquire data from the internal memory of handsets and UICCs without altering their content and to calculate integrity hashes for the acquired data. Both forensic and non-forensic software tools often use the same protocols and techniques to communicate with a device. However, non-forensic tools may allow unrestricted two-way flow of information and omit data integrity hash functions. Mobile device examiners typically assemble a collection of both forensic and non-forensic tools for their toolkit. The range of devices over which they operate is typically narrowed to: distinct platforms, a specific operating system family or even a single type of hardware architecture. Short product release cycles are the norm for mobile devices, requiring tool manufacturers to continually update their tools providing forensics examiners with an forensic solution. The task is formidable and tool manufacturers' support for newer models may lag significantly behind the introduction of a device into the marketplace. Models of older functioning mobile devices, though out of date, can remain in use for years after their initial release. Mobile device models introduced into one national market may also be used in areas by exchanging the UICC of one cellular carrier with that from another carrier. The current state is likely to continue, keeping the cost of examination significantly higher than if a few standard operating systems and hardware configurations prevailed. An important characteristic of a forensic tool is its ability to maintain the integrity of the original data source being acquired and also that of the extracted data."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nThe target audience for this publication includes cybersecurity program leadership, cybersecurity personnel, and others who are responsible for preparing for, detecting, responding to, or recovering from cybersecurity incidents. This publication is intended for use by most organizations, regardless of sector, size, or other factors.\n\nAt that time, incidents were relatively rare, the scope of most incidents was narrow and welldefined, and incident response and recovery was usually completed within a day or two. Under those conditions, it was realistic to treat incident response as a separate set of activities performed by a separate team of personnel and to depict all incident response activities as part of a circular life cycle. Formal post-incident activities would identify needed improvements and feed them into the preparation stage, thus starting the cycle again. Incident response activities were typically intermittent rather than continuous.\n\n(e.g., detecting the presence of a new threat and characterizing its behavior) and communicate those lessons to the appropriate personnel so that the organization's incident response and other cybersecurity risk management policies, processes, and practices can be adjusted as needed."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 4)"}, {"role": "assistant", "content": "astructure, such as a service mesh, that provides all application services. This class of applications is generally developed using a flexible and agile software development paradigm called DevSecOps.\nA salient feature of this paradigm is the use of flow processes called continuous integration and continuous deployment (CI/CD) pipelines, which initially take the software through various stages (e.g., build, test, package, and deploy) in the form of source code through operations that constitute the software supply chain (SSC) in order to deliver a new version of software . This document outlines strategies for integrating SSC security measures into CI/CD pipelines. ## Keywords\n\nactor; artifact; attestation; CI/CD pipeline; package; provenance; repository; SBOM; SDLC; SLSA; software supply chain. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nExample 5 : Establish and follow processes to address risk when there are security requirements that third-party software components to be acquired do not meet; this should include periodic reviews of all approved exceptions to requirements. | SCAGILE : Tasks Requiring the Help of Security Experts 8 SCFPSSD : Manage Security Risk Inherent in the Use of Third-Party Components SCSIC : Vendor Sourcing Integrity Controls SP80053 : SA-4, SA-9, SA-10, SA-10(1), SA-15, SR-3, SR-4, SR-5 SP800160 : 3.1.1, 3.1.2 SP800161 : SA-4, SA-9, SA-9(1), SA-9(3), SA-10, SA-10(1), SA-15, SR-3, SR-4, SR-5 SP800181 : T0203, T0415; K0039; S0374; A0056, A0161 |\n| Implement Roles and Responsibilities (PO.2) : Ensure that everyone inside and outside of the organization involved in the SDLC is prepared to perform their SDLC-related roles and responsibilities throughout the SDLC. | PO.2.1 : Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed. | Example 1 : Define SDLC-related roles and responsibilities for all members of the software development team. Example 2 : Integrate the security roles into the software development team. Example 3 : Define roles and responsibilities for cybersecurity staff, security champions, project managers and leads, senior management, software developers, software testers, software assurance leads and staff, product owners, operations and platform engineers, and others involved in the SDLC. Example 4 : Conduct an annual review of all roles and responsibilities."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.8 (NIST 3.2.8)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.8. 3.2.8. 3.2.8."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.8", "cmmc_practice_id": "AT.L2-3.2.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.5.4 TT&E | Exercises... 3.5.4 provides guidance on the type of TT&E identified for each FIPS 199 impact level. 3.5.4 TT&E Program Summary\n\nA TT&E program provides an overall framework for determining, scheduling, and setting objectives for TT&E activities."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.5.4", "cmmc_practice_id": "IA.L2-3.5.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 3)"}, {"role": "assistant", "content": "efore the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nend of life devices, supported devices with unsupportive owners, and herd immunity against malicious actors. ' Zombie devices ' are those that no longer receive software support and security updates.\nHigginbotham noted that unsupportive owners can neglect cybersecurity issues, leading to vulnerabilities. Herd immunity in cybersecurity requires collective action from manufacturers and consumers. Most consumers are unaware or indifferent to the end of life status of their products, resulting in ' zombie hordes ' . Communicating end of life status and dates is crucial, including proactive notification to consumers, retailers, and third parties. Companies should track devices to address critical vulnerabilities and create structured options for off-ramping zombie devices. Higginbotham emphasized that company priorities often overlook device security. Manufacturers should implement vulnerability disclosure programs, track issues, conduct comprehensive security audits, and allocate budgets for security maintenance. Buyers must keep products updated or segmented, and legislation should clarify responsibility to ensure herd immunity. Companies should have a dedicated point of contact for security researchers and consider recalls for insecure devices. Stacey also addressed secure repairs, both before and after end of life. Good hardware should not end up in landfills, but unpatched zombie devices pose risks. Consumer Reports advocates for designing products for longevity, including features like hardware upgrades, crypto agility, and increased memory."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\n3.2.3. 3.2.3."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication contains comprehensive updates to the Risk Management Framework . The updates include an alignment with the constructs in the NIST Cybersecurity Framework; the integration of privacy risk management processes; an alignment with system life cycle security engineering processes; and the incorporation of supply chain risk management processes. Organizations can use the frameworks and processes in a complementary manner within the RMF to effectively manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. Revision 2 includes a set of organization-wide RMF tasks that are designed to prepare information system owners to conduct system-level risk management activities. The intent is to increase the effectiveness, efficiency, and cost-effectiveness of the RMF by establishing a closer connection to the organization's missions and business functions and improving the communications among senior leaders, managers, and operational personnel. * Note: The publication pertains to information systems, which are discrete sets of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information, whether such information is in digital or non-digital form. Information resources include information and related resources, such as personnel, equipment, funds, and information technology. Therefore, information systems may or may not include hardware, firmware, and software. This publication is intended to help organizations manage security and privacy risk, and to satisfy the requirements in the Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "----------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2.\nEnterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3. Level 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 2)"}, {"role": "assistant", "content": "ds and Technology\n\n## NIST SPECIAL PUBLICATION 1800-34A\n\n## Validating the Integrity of Computing Devices\n\nVolume A: Executive Summary\n\nJon Boyens Tyler Diamond* Nakia Grayson Celia Paulsen William T.\nPolk Andrew Regenscheid Murugiah Souppaya\n\nNational Institute of Standards and Technology Information Technology Laboratory\n\n## Karen Scarfone\n\nScarfone Cybersecurity Clifton, Virginia\n\n*Former employee; all work for this publication was done while at employer\n\n## December 2022\n\nFINAL\n\nThis publication is available free of charge from https://doi.org/10.6028/NIST.SP.1800-34\n\n\n\n## Executive Summary\n\nThe supply chains of information and communications technologies are increasingly at risk of compromise. Additional risks causing supply chain disruptions include counterfeiting, unauthorized production, tampering, theft, and insertion of unexpected software and hardware. Managing these risks requires ensuring the integrity of the supply chain and its products and services. This project demonstrates how organizations can verify that the internal components and system firmware of the computing devices they acquire are genuine and have not been unexpectedly altered during manufacturing, distribution, or operational use. ## CHALLENGE\n\nTechnologies today rely on complex, globally distributed and interconnected supply chain ecosystems to provide highly refined, cost-effective, and reusable solutions. Most organizations' security processes consider only the visible state of computing devices. The provenance and integrity of a delivered device and its components are typically accepted without validating through technology that there were no unexpected modifications. A delivered device has integrity if it is genuine and all changes to the device were authorized and expected. Provenance is the comprehensive history of a device throughout the entire life cycle from creation to ownership, including changes made within the device or its components."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\n................................................ 4 |\n| 2.2. | Elliptic-Curve Cryptography ........................................................................................\n| 5 |\n| 2.3. | Bilinear Pair Mapping.................................................................................................. | 7 |\n| 2.4. | Bilinear Pairing for Cryptography................................................................................ | 9 |\n| 3. | Identity-Based Encryption ..............................................................................................11 | |\n| 4. | Attribute-Based Encryption............................................................................................13 | |\n| 4.1. | Ciphertext-Policy Attribute-Based Encryption | ............................................................13 |\n| 4.2."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\ntection and response (EDR) solutions that collect security telemetry data on endpoints. Any threat that is already inside of a network can move laterally and remain undetected for days or even months.\n- Edge computing [1], where much of the computing takes place close to the location of multiple IoT devices that may be geographically dispersed\n- Users located both within and outside of the corporate network, such as in homes, remote branch offices, and public locations (e.g., hotels, pubs); some enterprises must also provide access to ecosystem partners, who may be on their own corporate networks"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| | reward models; adaptation layers; and configuration parameters -before using them. R2: Scan and thoroughly test acquired AI models and their components for vulnerabilities and malicious content before use. | |\n| Create Source Code by Adhering to Secure Coding Practices (PW.5): Decrease the number of security vulnerabilities in the software, and reduce costs by minimizing vulnerabilities introduced during source code creation that meet or exceed organization-defined vulnerability severity criteria. | PW.5.1: Follow all secure coding practices that are appropriate to the development languages and environment to meet the organization's requirements. | High | R1: Expand secure coding practices to include AI technology-specific considerations. R2: Code the handling of inputs (including prompts and user data) and outputs carefully. All inputs and outputs should be logged, analyzed, and validated within the context of the AI model, and those with issues should be sanitized or dropped. R3: Encode inputs and outputs to prevent the execution of unauthorized code. | AI RMF: Manage 1.2, 1.3, 1.4 OWASP: LLM01, LLM02, LLM04-1, LLM06, LLM07, LLM09-9, LLM10 |\n| Configure the Compilation, Interpreter, and Build Processes to Improve Executable Security (PW.6): Decrease the number of security vulnerabilities in the software and reduce costs by eliminating vulnerabilities before testing occurs. | PW.6.1: Use compiler, interpreter, and build tools that offer features to improve executable security. | Low | C1: Consider using secure model serialization mechanisms that reduce or eliminate vectors for the introduction of malicious content."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nOrganizations participating in this project submitted their capabilities in response to an open call in the Federal Register for all sources of relevant security capabilities from academia and industry (vendors and integrators). The following respondents with relevant capabilities or product components (identified as 'Technology Partners/Collaborators' herein) signed a Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to build this example solution. The National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity issues. This public-private partnership enables the creation of practical cybersecurity solutions for specific industries, as well as for broad, cross-sector technology challenges. Through consortia under Cooperative Research and Development Agreements (CRADAs), including technology partners-from Fortune 50 market leaders to smaller companies specializing in information technology security-the NCCoE applies standards and best practices to develop modular, adaptable example cybersecurity solutions using commercially available technology. The NCCoE documents these example solutions in the NIST Special Publication 1800 series, which maps capabilities to the NIST Cybersecurity Framework and details the steps needed for another entity to re-create the example solution. The NCCoE was established in 2012 by NIST in partnership with the State of Maryland and Montgomery County, Maryland. The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nSemiconductor-based hardware is the foundation of modern-day electronics - from smartphones, computers, and telecommunications to transportation and critical infrastructure. The semiconductor hardware supply chain is a complex network of companies that collectively provide intellectual property, designs, and raw materials and manufacture, test, package, and distribute products. Coordination among the components of a supply chain is required at different stages, including inception, deployment to end users, maintenance during use, and disposal or end of life. Securing semiconductor-based hardware and their supply chains help protect sensitive information, maintain the integrity of systems, and ensure overall stability across the infrastructure and connected world."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nChanges in application architecture: Application architectures - especially those of cloud-native applications - have changed from being monolithic to being microservices-based in order to meet the deployment agility and modular scalability requirements. This, combined with DevSecOps (a paradigm covering Development, Security and Operations) primitives such as continuous integration/continuous deployment (CI/CD) pipelines for the development and deployment of software, has improved the security profile of the applications but has also introduced new threat vectors related to the CI/CD workflows themselves. - Distributed nature of the application into ones located within a corporate data center, remote branch offices, and multiple cloud locations\n- Perimeter approach based on the premise that the threat originates outside of the network, which is why most perimeter security solutions (e.g., intrusion prevention system - IPS, intrusion detection systems - IDS, firewalls) focus only on north-south traffic (i.e., ingress, which refers to traffic that originates from outside of the local network and destined for endpoints in the local cluster network). However, over 75 % of network traffic is now east-west (i.e., within the local network) or server-to-server (due to applications being based on microservices), which is largely invisible to security teams, though some visibility is now sought through endpoint detection and response (EDR) solutions that collect security telemetry data on endpoints. Any threat that is already inside of a network can move laterally and remain undetected for days or even months."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.1.2 | SP-ARC-001 |\n| DETECT (DE) | Anomalies and Events (DE. 3.1.2 Resolution\n\nThe build provides a significant defense in depth against this use case."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 8)"}, {"role": "assistant", "content": "ex with many business drivers, relying on expertise at best cost across a global supply chain. This panel discussion focused on open security concerns in the hardware development life cycle. ## 2.1.1.\nSpeaker Viewpoints\n\nThe panel opened with Jonathan Ring, Deputy Assistant National Cyber Director for Technology Security from the Office of the National Cyber Director (ONCD). Jonathan reflected that ONCD's National Cybersecurity Strategy recognizes the importance of improving the cybersecurity of the Nation's critical infrastructure, which includes restoring the production of critical goods to the United States (US) as well as improving cybersecurity in the semiconductor/IC supply chain. Jonathan highlighted past achievements of the Biden-Harris Administration that overlap with cybersecurity in the hardware development life cycle, including:\n\n- Shifting the balance of security to those best suited to bear it, as represented in the Cybersecurity and Infrastructure Security Agency's (CISA) Secure by Design initiative\n- The NIST CHIPS (Creating Helpful Incentives to Produce Semiconductors) R&D Metrology Program, which outlines gaps in the semiconductor ecosystem\n- Ongoing work through the Subcommittee for Microelectronics Leadership\n- Eliminating entire classes of software vulnerabilities in Back to the Building Blocks: A Path Toward Secure and Measurable Software\n\nFurthermore, Jonathan stressed the importance and continued need for public-private partnerships, like the Semiconductor Research Corporation and the Semiconductor Industry Association. He also stressed the need for continued conversations concerning advanced metrology for supply chain trust and assurance, guidelines for security analytics and automation, vulnerability management across all product life cycles, and the use of machine learning in chip design and manufacturing. The second speaker for the panel was Adam Golodner, advisor to the Semiconductor Industry Association."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.4.1 | Risk... 3.4.1, Risk, provides a description of the risk analysis we performed. 3.4.1 Risk\n\nUsing the guidance in NIST's series of publications concerning risk, we worked with financial institutions and the Financial Sector Information Sharing and Analysis Center to identify the most compelling risk factors encountered by this business group."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n|\n| ID.RA-10 | Critical suppliers are assessed prior to acquisition | Low | N1: See the notes for ID.RA. |\n| ID.IM (Improvement) | Improvements to organizational cybersecurity risk management processes, procedures, and activities are identified across all CSF Functions | Medium | N1: See the note for ID. |\n| ID.IM-01 | Improvements are identified from evaluations | Medium | R1: Periodically evaluate incident response program performance to identify problems and deficiencies that should be corrected. N1: Possible evaluation forms include self- assessments, third-party assessments, and independent audits. |\n| ID.IM-02 | Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties | High | N1: Incident response exercises and tests may provide helpful information for program evaluation and prepare staff and involved third parties (e.g., critical service providers and product suppliers) for future incident response activities. N2: See [SP800-84] for more information on simulations, tabletop discussions, and other forms of exercises. |\n| ID.IM-03 | Improvements are identified from the execution of operational processes, procedures, and activities | High | N1: The execution of operational processes, procedures, and activities includes all incident response and recovery efforts."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe need and methods for conducting media sanitization should be identified and developed before arriving at the disposal phase in the system life cycle. ISM sanitization controls should be developed, documented, and deployed when the initial system security plan is developed [12]."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\n| 1. | Government actions to support strengthening IoT cybersecurity need to be coordinated with industry. |\n|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | The use of robust frameworks and the adoption of open standards are crucial for effectively managing risks across heterogeneous environments. |\n| 3 | The dynamic nature of threats requires more context aware inputs, more proactive tracking and mitigation measures, and more examination into the inputs of the threat modeling approach. |\n| 4 | There are market opportunities to securely design the next wave of products with cybersecurity through end of life and instill incentives into the maintenance of existing products. |\n| 5 | The balance of shared responsibility between manufacturers and users for improving security varies by sector and needs the right incentives for both. |\n| 6 | There are broad challenges to integrating privacy objectives into IoT cybersecurity risk management. |\n| 7 | There is an increased awareness for evolving cybersecurity responsibilities across the players of the IoT ecosystem from manufacturers to users of the ecosystem. |\n\nStacey Higginbotham of Consumer Reports noted that connected devices establish an ongoing relationship between the buyer, seller, and manufacturer. The lifetime of a connected product is often separate from its physical state. While physical products fail in visible ways, software degrades more quickly, often without consumer awareness. The industry also lacks adequate support for maintenance. Stacey's discussion highli ghted three key areas: zombie hordes of end of life devices, supported devices with unsupportive owners, and herd immunity against malicious actors. ' Zombie devices ' are those that no longer receive software support and security updates."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nor mobile devices/systems, do not require a separate risk management process but rather a tailored set of controls and specific implementation details determined by applying the existing RMF process.\n1 An information system is a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information [44 USC 3502]. The term information system includes, for example, general-purpose computing systems; industrial/process control systems; cyber-physical systems; weapons systems; super computers; command, control, and communications systems; devices such as smart phones and tablets; environmental control systems; embedded devices/sensors; and paper-based systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "tise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D.\nThe controls described assist organizations in defining the controls needed to satisfy minimum assurance requirements. Where additional assurance is desired to achieve risk management objectives, Table E-4 provides additional security controls and control enhancements to achieve enhanced assurance. Implementers should note that designation of assurance-related controls is not intended to imply a greater level of importance for such controls. Achieving adequate security for organizational information systems requires the correct combination of both functionality- and assurance-related security controls. ## 6 Security Controls\n\nAppendix F, the Security Control Catalog, provides a comprehensive range of countermeasures for organizations and information systems. The security controls are designed to be technologyneutral such that the focus is on the fundamental countermeasures needed to protect organizational information during processing, storage, or transmission. SP 800-53 Rev. 4, therefore, does not provide guidance on the application of security controls to specific technologies, environments of operation, or missions/business functions. These specific areas may be addressed using overlays (see below). Control enhancements are included with many security controls and are selected in order to increase the strength of the base control. Control enhancements are intended to be implemented only in conjunction with implementation of the base control. Some security controls and control enhancements include one or more assignment and selection statements. These are variable 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nDevice cybersecurity capabilities are cybersecurity features or functions that computing devices provide through their own technical means (i.e., device hardware and software). This publication defines an Internet of Things (IoT) device cybersecurity capability core baseline, which is a set of device capabilities generally needed to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . .\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.1. Truncation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.2. Nonce Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.3. AEAD Requirements.............................................................. | 19 |\n| 4.4. Security Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.1. Single-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.2. Multi-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.3. Nonce-Misuse Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 21 |\n| 5. Hash and eXtendable-Output Functions (XOFs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.1. Specification of Ascon-Hash256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.2. Specification of Ascon-XOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 25 |\n| 5.3. Specification of Ascon-CXOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 28 |\n| 5.4. Streaming API for XOF............................................................ | 30 |\n| 5.5. Security Strengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nIn developing standards and guidelines required by [FISMA], NIST consults with other federal agencies and\noffices as well as private sector entities to improve information security, avoid unnecessary and costly\nduplication of effort, and ensure that NIST publications complement the standards and guidelines\nemployed for the protection of national security systems. In addition to its comprehensive public review\nand vetting process, NIST collaborates with the Office of the Director of National Intelligence (ODNI), the\nDepartment of Defense (DoD), and the Committee on National Security Systems (CNSS) to establish and\nmaintain a unified framework and common foundation for information security across the Federal\nGovernment. A common foundation and framework for information security provides the intelligence,\ndefense, and civilian sectors of the Federal Government and their contractors more uniform and\nconsistent ways to manage risks to organizational operations and assets, individuals, other organizations,\nand the Nation that result from the operation and use of systems. A common foundation and framework\nalso provides a strong basis for the reciprocal acceptance of security authorization decisions and facilitate\ninformation sharing. NIST also works with public and private sector entities to establish and maintain\nspecific mappings and relationships between the security standards and guidelines developed by NIST, the\nInternational Organization for Standardization (ISO), and the International Electrotechnical Commission\n(IEC)."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 5)"}, {"role": "assistant", "content": "gement, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\nThe Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Audience\n\nThere are three primary audiences for this document:\n\n- AI model producers - Organizations that are developing their own generative AI and dual-use foundation models, as defined in EO 14110\n- AI system producers - Organizations that are developing software that leverages a generative AI or dual-use foundation model\n- AI system acquirers 1 - Organizations that are acquiring a product or service that utilizes one or more AI systems\n\nIndividuals who are interested in better understanding secure software development practices for AI models may also benefit from this document. Readers are not expected to be experts in secure software development or AI model development, but such expertise may be needed to implement these recommended practices. ## Note to Readers\n\nIf you are from a standards developing organization (SDO) or another organization that is defining a set of secure practices for AI model development and you would like to map your standard or guidance to the SSDF profile, please contact the authors at ssdf@nist.gov. They will introduce you to the National Online Informative References Program (OLIR), where you can submit your mapping to augment the existing set of informative references. The authors also welcome feedback at any time on any part of the document, as well as suggestions for Implementation Examples and Informative References to add to this document. All feedback should be sent to ssdf@nist.gov. ## Trademark Information\n\nAll registered trademarks belong to their respective organizations."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.2.1. 3.2.1. 3.2.12 of [SP800-63B])."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\nThe Criminal Justice Information Services (CJIS) Security Policy versions 5.9.2 and later [1] require the use of multi-factor authentication (MFA) to protect access to criminal justice information (CJI). MFA is important for protecting against credential compromises and other cyber risks that may threaten CJI. Criminal and non-criminal justice agencies around the country will need to work with their technology vendors to implement this CJIS requirement. Credential compromises represent a critical and pervasive cybersecurity threat, serving as a gateway for malicious actors to infiltrate networks and systems, thus gaining access to sensitive data. Whether through phishing, brute-force attacks, or exploiting vulnerabilities in authentication mechanisms, credential compromise poses a significant risk to organizations and individuals alike. To mitigate this threat, version 5.9.2 and subsequent versions of the Federal Bureau of Investigation (FBI) Criminal Justice Information Services (CJIS) Security Policy [1] require multi-factor authentication (MFA) for all users when accessing criminal justice information (CJI). Both criminal and non-criminal justice agencies that receive CJI are subject to this requirement. In this document, we refer to these organizations generically as agencies . - [1] U.S. Department of Justice (2024) Criminal Justice Information Services (CJIS) Security Policy, Version 6.0. CJISSECPOL v6.0. Available at https://le.fbi.gov/filerepository/cjis\\_security\\_policy\\_v6-0\\_20241227.pdf\n- [2] Wisconsin Law Enforcement Network (2024) Public Safety Threat Report: 2024 Threat Landscape. https://wilenet.widoj.gov/sites/default/files/public\\_files-2025-02/ijis2024-threat-landscape-report.pdf\n- [3] Temoshok D, Proud-Madruga D, Choong YY, Galluzzo R, Gupta S, LaSalle C, Lefkovitz N, Regenscheid A (2025) Digital Identity Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63-4."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 4)"}, {"role": "assistant", "content": "pment of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems.\nThe Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThe protection of Controlled Unclassified Information (CUI) resident in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides federal agencies with recommended enhanced security requirements for protecting the confidentiality of CUI: (1) when the information is resident in nonfederal systems and organizations; (2) when the nonfederal organization is not collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency; and (3) where there are no specific safeguarding requirements for protecting the confidentiality of CUI prescribed by the authorizing law, regulation, or government-wide policy for the CUI category listed in the CUI Registry. The enhanced requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide security protection for such components when the designated CUI is associated with a critical program or high value asset. The enhanced requirements supplement the basic and derived security requirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| | | PO.3.3: Configure tools to generate artifacts of their support of secure software development practices as defined by the organization."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Contingency Planning Guide for Federal Information Systems provide? (Part 7)"}, {"role": "assistant", "content": "Background ....................................................................................................5 | Chapter 2. Background ....................................................................................................5 | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nEnterprise Campus Network (red de las instalaciones de la empresa). Internal App Server (servidor de aplicaciones interno). Database (base de datos). Internet (Internet). Employees (empleados). Employee (empleado). Contractor Service Tech (técnico de servicio de contratistas ). Contracted HVAC (contratación de climatización). Conference Center (centro de conferencias). Visitors (visitantes)."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n| 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 |"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe enhanced security requirements are organized into 14 families consistent with the families for basic and derived requirements. Each family contains the requirements related to the general security topic of the family. The families are closely aligned with the minimum security requirements for federal information and information systems in [FIPS 200]. The security requirements for contingency planning , system and services acquisition , and planning are not included within the scope of this publication due to the tailoring criteria in [SP 800-171]. Table 1 lists the security requirement families addressed in this publication. 17\n\n- 3.11.4e Document or reference in the system security plan the security solution selected, the rationale for the security solution, and the risk determination."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n...................................................................... 14\nCHAPTER THREE THE CONTROLS .................................................................................................\n16\n3.1 ACCESS CONTROL .................................................................................................................. 18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nolidated, centralized, and correlated. -  When logging of network traffic is turned off or reduced, which is often the case, visibility into network data may be the only alternative to see anomalies.\nVisibility into network data is preferable when the endpoint (or a middlebox , a network device that often intercepts and manipulates network traffic for security, optimization, or content filtering ) platform is incapable of adequate logging without causing utilization or performance issues on the platform. -  There are many security threats that are more easily identifiable or only visible with visibility into network data. Where and how the network data is identified and collected can reveal key information about security threats . -  Staff can analyze network data to ensure that endpoint security agents are operating properly . If an endpoint is compromised or its security agent is not running properly, network data is the only line of defense and the most critical tool for performing related triage and forensics to quickly resolv e related issues. -  If network data cannot be decrypted, a security breach, malware, or other compromise can more easily spread throughout the entire organization via a single platform. -  Nearly all attacks occur over the network-leaving behind traces or tracks. To understand q uestionable traffic , it is necessary to understand the source of the traffic. Without decrypt ion, you cannot gain such insights, nor can you detect, trace, or eliminate malicious actions . -  Root cause analysis is critical to most large organizations. Forensics performed after a breach or other security exposure event depends heavily on DPI and network data to figure out what happened, why, and what can be done about it. Alternatives to DPI require significant time and effort and are generally prohibitively disruptive and expensive."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 4.2 | Access Policies | 4-12 |\n|-------------|------------------------------------------------------------------------------------------------|-----------|\n| 4.3 | Unauthorized Statistical Disclosure | 4-12 |\n| 4.4 | Transaction Trail | 4-13 |\n| | 4.4.1 Automated Journals | 4-13 |\n| 4.5 | Data Checks and Integrity | 4-13 |\n| 5. | APPLICATIONS INTERFACE | 4-14 |\n| 5.1 | General | 4-14 |\n| 5.2 | System Development Controls | 4-14 |\n| 5.3 | Project Definition | 4-14 |\n| 5.4 | System Design | 4-15 |\n| 5.5 | Detailed Design and Programming | 4-15 |\n| 5.6 | System Testing | 4-15 |\n| 5.7 6."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.3.4 KAS2-bilateral-confirmation... 3.3.4. 3.3.4 can be used to provide assurance to a key-pair owner acting as either party U or party V that both parties are in possession of the correct private key; i."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "The guide was developed and is maintained by the Joint Task Force Transformation Initiative Interagency Working Group, part of an ongoing information security partnership among the U.S. Department of Defense, the Intelligence Community, the Committee on National Security Systems, the Department of Homeland Security, and U.S. federal civil agencies. SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. SP 800-53 Revision 4 is part of the NIST Special Publication 800-series that reports on the NIST Information Technology Laboratory's (ITL) computer security-related research, guidelines, and outreach. The publication provides a comprehensive set of security controls, three security control baselines (low, moderate, and high impact), and guidance for tailoring the appropriate baseline to specific needs according to the organization's missions, environments of operation, and technologies used. As the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 5)"}, {"role": "assistant", "content": "gement, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems.\nThe Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations. i\n\n\fNIST SP 800-63B-4\nJuly 2025\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nPatent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for\ncompliance with the guidance or requirements of this publication disclose such patent\nclaims to ITL. However, holders of patents are not obligated to respond to ITL calls for\npatents and ITL has not undertaken a patent search in order to identify which, if any,\npatents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims\nwhose use may be required for compliance with the guidance or requirements of this\npublication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid\npatent infringement in the use of this publication. ii\n\n\fNIST SP 800-63B-4\nJuly 2025\n\nTable of Contents\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\n1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1. Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. Document Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. Authentication Assurance Levels . . . . . . . . . . . . . . . . . . . . . . . . . 2.1. Authentication Assurance Level 1 . . . . . . . . . . . . . . . . . . . . . 2.1.1. Permitted Authenticator Types\n\n. . . . . . . . . . . . . . . . . . 2.1.2. Authenticator and Verifier Requirements . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n| [RFC5280] | D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R. Housley, and W. Polk, Inter X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile , Internet Engineering Task Force (IETF) Network Working Group Request for Comments (RFC) 5280, May 2008. https://doi.org/10.17487/RFC5280. |\n|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [SECTION508] | Section 508 of the Rehabilitation Act of 1973, as amended , 29 U.S.C. §794(d), https://www.section508.gov [accessed 5/16/18]. |\n| [SKIMMER] | I. Kirschenbaum and A. Wool, 'How to Build a Low-Cost, Extended-Range RFID Skimmer,' Proceedings of the 15th USENIX Security Symposium (Security '06) , Vancouver, British Columbia, Canada, July 31 - August 4, 2006, USENIX Association: Berkeley, California, 2006, pp. 43-57. https://www.usenix.org/legacy/event/sec06/tech/full_papers/kirschenbaum/ kirschenbaum.pdf [accessed 3/1/17]. |\n| [SP800-73] | NIST Special Publication 800-73-4, Interfaces for Personal Identity Verification, May 2015 (including updates as of 2/8/16). https://doi.org/10.6028/NIST.SP.800-73-4. |\n| [SP800-76] | NIST Special Publication 800-76-2, Biometric Specifications for Personal Identity Verification , July 2013. https://doi.org/10.6028/NIST.SP.800-76-2. |\n| [SP800-78] | NIST Special Publication 800-78-4, Cryptographic Algorithms and Key Sizes for Personal Identity Verification , May 2015. https://doi.org/10.6028/NIST.SP.800-78-4. |\n| [SP800-87] | NIST Special Publication 800-87 Revision 2, Codes for the Identification of Federal and Federally-Assisted Organizations , April 2018."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nvelopers will also find it useful guidance on security and control issues. The guide is designed to provide audit/review programs for each major phase of the SDLC and assumes a large sensitive system.\nThe reader is expected to make appropriate modifications for a small less sensitive system."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 8)"}, {"role": "assistant", "content": "|\n\n## Introduction\n\nCryptography is an essential component of modern computing.\nUnfortunately, implementing cryptography correctly is a non-trivial undertaking. Past research studies have supported this observation by revealing a multitude of errors and developer pitfalls in the cryptographic implementations of software products [1-5]. However, these studies focused on the practices of less-experienced, individual developers. Therefore, there was little understanding of the cryptographic development practices of organizations, including the benefits and challenges of using cryptographic resources such as standards specifications and libraries. To address this gap, between January and September 2017, a four-person research team led by the National Institute of Standards and Technology (NIST) Information Technology Laboratory Visualization and Usability Group conducted a qualitative investigation into the processes and resources that organizations employ in the development and testing of cryptographic products. The study involved in-depth interviews of participants representing organizations that develop either a security product that uses cryptography or a non-security product that heavily relies on cryptography. The study aimed to answer the following research questions:\n\n- What are the cryptographic development and testing practices of organizations? - What challenges, if any, do organizations encounter while developing and testing these products? - What cryptographic resources do these organizations use, and what are their reasons for choosing them? This NIST Internal Report (NISTIR) is a companion to the research paper 'We make it a big deal in the company': Security Mindsets in Organizations that Develop Cryptographic Products [6]."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U:\n\nCryptographic Module Validation Program; CMVP; FIPS 140 testing; FIPS 140-3; ISO/IEC 19790; ISO/IEC 24759; sensitive security parameter establishment methods; sensitive security parameter generation; testing requirement; vendor evidence; vendor documentation.\n\nThis document is intended for use by vendors, testing labs, and the CMVP."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/\nsp/800/63/4/final, including related content, potential updates, and document history.\n\n3.7.\n\ncollection, maintenance, use, and disclosure of information about individuals that\nis maintained by federal agencies in systems of records"}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Standard | Sections | Implementation Specifications (R) = Required, (A) = Addressable | |-----------------------------------------------------|---------------------------|-------------------------------------------------------------------| | Administrative Safeguards | Administrative Safeguards | Administrative Safeguards | | Security Management Process | 164.308(a)(1) | Risk Analysis (R) | | Security Management Process | 164.308(a)(1) | Risk Management (R) | | Security Management Process | 164.308(a)(1) | Sanction Policy (R) | | Security Management Process | 164.308(a)(1) | Information System Activity Review (R) | | Assigned Security Responsibility | 164.308(a)(2) | (R) | | Workforce Security | 164.308(a)(3) | Authorization and/or Supervision (A) | | Workforce Security | 164.308(a)(3) | Workforce Clearance Procedure (A) | | Workforce Security | 164.308(a)(3) | Termination Procedures (A) | | Information Access Management | 164.308(a)(4) | Isolating Health care Clearinghouse Function (R) | | Information Access Management | 164.308(a)(4) | Access Authorization (A) | | Information Access Management | 164.308(a)(4) | Access Establishment and Modification (A) | | Security Awareness and Training | 164.308(a)(5) | Security Reminders (A) | | Security Awareness and Training | 164.308(a)(5) | Protection from Malicious Software (A) | | Security Awareness and Training | 164.308(a)(5) | Log-in Monitoring (A) | | Security Awareness and Training | 164.308(a)(5) | Password Management (A) |"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 10)"}, {"role": "assistant", "content": "cations are developed through an agile software development life cycle (SDLC) paradigm called DevSecOps, which uses flow processes called Continuous Integration/ Continuous Delivery (CI/CD) pipelines.\nThe security of applications during runtime is ensured through various security measures, such as assigning unique service identities for microservices and subjects that invoke those services and policy enforcement through proxies. However, sophisticated attacks on software have been carried out through the stealthy introduction of attack vectors during various activities in the SDLC, which collectively constitute the software supply chain (SSC). Thus, in the context of cloud-native applications, SSC security assurance measures must be integrated into CI/CD pipelines. ## 1.1. Purpose\n\nThis document outlines strategies for integrating SSC security assurance measures into CI/CD pipelines to protect the integrity of the underlying activities. The overall goal is to ensure that the CI/CD pipeline activities that take source code through the build, test, package, and deployment stages are not compromised. ## 1.2. Scope\n\nSSC security assurance measures use various artifacts, such as a software bill of materials (SBOM) and frameworks for the attestation of software components. The specification of these artifacts, their mandatory constituents, and the requirements that processes using them must satisfy are continually evolving through projects in government organizations and various industry forums and are, therefore, beyond the scope of this document. Rather, this document focuses on actionable measures to integrate various building blocks for SSC security assurance into CI/CD pipelines to enhance the preparedness of organizations to address SSC security in the development and deployment of their cloud-native applications. ## 1.3."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract. |\n|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| How do I know if I have CUI? | It is the responsibility of the federal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n| 1 | Summary..............................................................................................1 | Summary..............................................................................................1 | |-----|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | 1.2 | Solution..........................................................................................................................2 | | | 1.3 | Benefits..........................................................................................................................3 | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | 2.1 | Typographic Conventions..............................................................................................5 | | 3 | Approach .............................................................................................6 | Approach .............................................................................................6 | | | 3.1 | Audience........................................................................................................................6 | | | 3.2 | Scope .............................................................................................................................6 | | | 3.3 | Assumptions..................................................................................................................7 | | | 3.4 | Risk Assessment ............................................................................................................7 | | | 3.4.1 | Risk................................................................................................................................8 | | | | 3.4.2 Security Control Map....................................................................................................9 | | | 3.5 Technologies................................................................................................................13 | 3.5 Technologies................................................................................................................13 | | 4 | Architecture .......................................................................................16 | Architecture .......................................................................................16 | | | 4.1 Architecture Description .............................................................................................16 | 4.1 Architecture Description .............................................................................................16 | | | 4.1.1 | High-Level Architecture ..............................................................................................16 | | | 4.1.2 | Architecture Components...........................................................................................17 | | 5 | Security Characteristic Analysis..........................................................20 | Security Characteristic Analysis..........................................................20 | | | 5.1 Assumptions and Limitations | ......................................................................................20 | | | 5.2 Build | Testing................................................................................................................20 | | | 5.3 | Scenarios and Findings................................................................................................21 | | | 5.3.1 | Ransomware via Web Vector and Self-Propagation...................................................21 | | | 5.3.2 | Destructive Malware via USB Vector..........................................................................22 | | |"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nIMDs are tiny computing platforms that run firmware in extremely power constrained environments. They offer data storage for static data (such as device information), relatively static data (such as patient identification, medical condition, therapy configuration) and dynamic data (such as recent patient readings and audit logs). IMDs offer wireless access for read and write operations to the data on the IMD (including the firmware) to a variety of stakeholders and roles.\n\nSome of the threats to wireless IMDs include device reprogramming, data extraction, data tampering, repeated access attempts and data flooding. Vulnerabilities include unsecured communication channels, inadequate authentication and access control, weak audit mechanisms and meager storage. The resulting risks include patient safety compromise resulting from firmware malfunction or therapy misconfiguration, device unavailability due to battery power depletion, patient privacy loss due to data leakage to unauthorized parties, and inappropriate medical follow-up due to tampering of patient readings. While some cyber threats may be unintentional, various motivations exist for deliberate cyber attacks, such as patient information gathering, negative impact to patient health status, ego satisfaction of the attacker, as well as gaining competitive advantage over another vendor through negative press.\n\nIdentification of the various data types within an IMD is an essential step in analyzing the security and privacy risks of such devices. Possible data types include firmware (though technically not 'data'), device identification data, patient identification and health condition data, therapy configuration data, patient readings, audit log data, and other data."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos... 3.2.1) o cortafuegos en el o los puntos finales. 3.2.1)."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nassessment; assessment method; assessment object; assessment procedure; assurance; Controlled Unclassified Information; coverage; FISMA; NIST Special Publication 800-171; NIST Special Publication 800-53A; nonfederal organization; nonfederal system; security assessment; security requirement.\n\n- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Acquisition or procurement responsibilities (e.g., contracting officers)\n- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts)\n\n- Federal perspective : The entity establishing and conveying security assessment requirements in contractual vehicles or other types of agreements\n- Nonfederal perspective : The entity responding to and complying with the security assessment requirements set forth in contracts or agreements"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.5.2. 3.5.2."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract. |\n|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| How do I know if I have CUI? | It is the responsibility of the federal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Ordered t-way Combinations for Testing State-based Systems provide?"}, {"role": "assistant", "content": "## Ordered t-way Combinations for Testing State-based Systems\n\nD. Richard Kuhn M S Raunak Computer Security Division Information Technology Laboratory\n\nRaghu N. Kacker Applied and Computational Mathematics Division Information Technology Laboratory\n\nJune 13, 2022\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.CSWP.26\n\n\n\n## Abstract\n\nFault detection often depends on the specific order of inputs that establish states which eventually lead to a failure. However, beyond basic structural coverage metrics, it is often difficult to determine if code has been exercised sufficiently to ensure confidence in its functions. Measures are needed to ensure that relevant combinations of input values have been tested with adequate diversity of ordering to ensure correct operation. Combinatorial testing and combinatorial coverage measures have been applied to many types of applications but have some deficiencies for verifying and testing state-based systems where the response depends on both input values and the current system state. In such systems, internal states change as input values are processed. Examples include network protocols, which may be in listening, partial connection, full connection, disconnected, and many other states depending on the values of packet fields and the order of packets received. Similarly, merchant account balances in credit card systems change continuously as transactions are processed. This publication introduces a notion of ordered t-way combinations, proves a result regarding the construction of adequate blocks of test inputs, and discusses the application of the results to verify and test state-based systems. ## Keywords\n\ncombinatorial coverage; combinatorial methods; combinatorial testing; software testing; structural coverage; test coverage."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 9)"}, {"role": "assistant", "content": "Automated Network Provisioning Tools....................................................................12 | | | Networking Appliances as Services ............................................................................13 | Networking Appliances as Services ............................................................................13 | | | Network Configurations for Basic Security Functions..................................................14 | Network Configurations for Basic Security Functions..................................................14 | Network Configurations for Basic Security Functions..................................................14 | | 4.1 Conceptual Underpinning - Contextual Information .............................................................14 | 4.1 Conceptual Underpinning - Contextual Information .............................................................14 | 4.1 Conceptual Underpinning - Contextual Information .............................................................14 | | 4.2 Network Configuration for Device Management ...................................................................15 | 4.2 Network Configuration for Device Management ...................................................................15 | 4.2 Network Configuration for Device Management ...................................................................15 | | 4.3 Network Configuration for User Authentication.....................................................................16 | 4.3 Network Configuration for User Authentication.....................................................................16 | | | 4.4 Network Configuration for Device Authentication and Health Monitoring....................16 | 4.4 Network Configuration for Device Authentication and Health Monitoring....................16 | | | 4.5 Network Configuration for Authorizing Application/Service Access......................................16 | 4.5 Network Configuration for Authorizing Application/Service Access......................................16 | 4.5 Network Configuration for Authorizing Application/Service Access......................................16 | | 4.6 Network Configurations for Preventing Attack Escalation.....................................................16 | 4.6 Network Configurations for Preventing Attack Escalation.....................................................16 | 4.6 Network Configurations for Preventing Attack Escalation.....................................................16 | | | Enterprise-Wide Network Security Framework - Zero Trust Network Access (ZTNA) 17 | Enterprise-Wide Network Security Framework - Zero"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body ...................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nParticipants indicated topics that their security awareness programs addressed via training courses, events, or other communications in the past 1 - 2 years. Figure 9 shows the security awareness topics and percentages of programs addressing those topics. All participants' programs covered the topic of social engineering, and over 90% addressed passwords and authentication, malware, and privacy topics. Security considerations when installing or updating software was the least covered topic but still addressed by 64% of programs.\n\n- 'I do consult with members of the SOC [Security Operations Center] to see if there's anything glaring that I need to include in my training each year.' (N09)\n- 'Also working with the help desk, just what type of problems our users encounter that are related to security issues.' (S05)\n- 'Being tied directly to the cybersecurity policy team has made it easier because the awareness team always has whatever the latest guidance is and can push that out very quickly.' (D03)\n- 'We've worked closely with the information security officials' (N08)\n- 'I'm located in the chief information security office, and there are…divisions in that office that provide a wide range of cybersecurity services to the Department. And those managers have responsibilities for things such as identity management, internet response, data loss prevention. So, within any year, I reach out to those stakeholders to ask, 'What's important for the user to understand about cybersecurity awareness? What do you want to talk to the customer about? What kind of behaviors are you seeing that you want us to help encourage them to do or not to do?.' (D01)\n- 'Build relationships with offices within your organization- Incident Response, Help Desk,…FISMA Compliance.' (Q24)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Updates to the Security Requirements and Families\n\n- It is important to identify permitted and prohibited actions regarding software installation when users have the ability to install software on organizational systems. Permitted software installations could include updates and security patches to existing software and downloading new applications from organizationapproved 'app stores.' Companies might prohibit employees from downloading certain programs, services, software versions, etc ."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nAs the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process. The baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems .\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n## Ascon-Based Lightweight Cryptography Standards for Constrained Devices\n\nAuthenticated Encryption, Hash, and Extendable Output Functions\n\n## Ascon-Based Lightweight Cryptography Standards for Constrained Devices"}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThis includes requirements from internal sources (e.g., the organization's policies, business objectives, and risk management strategy) and external sources (e.g., applicable laws and regulations). | PO.1.1 : Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. | Example 1 : Define policies for securing software development infrastructures and their components, including development endpoints, throughout the SDLC and maintaining that security. Example 2 : Define policies for securing software development processes throughout the SDLC and maintaining that security, including for open-source and other third-party software components utilized by software being developed. Example 3 : Review and update security requirements at least annually, or sooner if there are new requirements from internal or external sources, or a major security incident targeting software development infrastructure has occurred. Example 4 : Educate affected individuals on impending changes to requirements."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n....................................................................................... | 63 |\n| A.1.1.\nC-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nThe graph model, as shown in Fig. 4, represents and stores data based on relationships. It is a schemaless model, and data is structured using nodes and edges. Nodes typically store data entities, while edges represent the relationships or links between the data nodes. The model is scalable but complex as it often utilizes shortest path algorithms to optimize data queries for real-time results. In this model, the efficiency of a query depends on the number of relationships among the nodes [HI]. Graph-based databases have various applications, such as recommendation systems, social networking, identity and access management (IAM), and content management [AA WT].\n\nNoSQL systems can handle fast-paced agile development, the storage of large volumes of structured and semi-structured data, the requirements for scale-out architecture, and modern application paradigms (e.g., microservices and real-time streaming) [MO]. However, they also face many challenges with regard to access control, such as a lack of proper authentication, encryption, dynamic model support, and fine-grained authorization (as described in Sec. 3.3). Therefore, careful considerations need to be made when implementing access control on NoSQL databases to address these issues effectively.\n\n- [ZM] Zaki AK, Indiramma M (2015) A Novel Redis Security Extension for NoSQL Database Using Authentication and Encryption, 2015 IEEE International Conference on Electrical, Computer and Communication Technologies (ICECCT) . https://doi.org/10.1109/ICECCT.2015.7226101."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 7)"}, {"role": "assistant", "content": "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.\nThe 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. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## THE APPLICABILITY OF ENHANCED SECURITY REQUIREMENTS\n\nThe 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 3)"}, {"role": "assistant", "content": " Examples of data integrity attacks include unauthorized insertion, deletion, or modification of data to corporate information such as emails, employee records, financial records, and customer data.\n-  The National Cybersecurity Center of Excellence (NCCoE) at NIST built a laboratory environment to explore methods to effectively detect and respond to a data\n- integrity event in various information technology (IT) enterprise environments, to immediately react to the event in an effort to prevent a complete compromise. -  This NIST Cybersecurity Practice Guide demonstrates how organizations can develop and implement appropriate actions during a detected data integrity cybersecurity event. \n\n## CHALLENGE\n\nSome organizations have experienced systemic attacks that force operations to cease. One variant of a data integrity attack-ransomware-encrypts data, leaving it modified in an unusable state. Other data integrity attacks may be more dynamic, targeting machines, spreading laterally across networks, and\n\ncontinuing to cause damage throughout an organization. In either case, behaviors are exhibited-such as files inexplicably becoming encrypted or network activity-that provide an ability to immediately detect the occurrence and respond in a timely fashion to curtail the ramifications. ## SOLUTION\n\nNIST published version 1.1 of the Cybersecurity Framework in April 2018 to help organizations better manage and reduce cybersecurity risk to critical infrastructure and other sectors. The framework core contains five functions, listed below."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n- Management network: The management network is a dedicated network that allows system administrators to remotely control, monitor, and configure computer nodes in an HPC system. Modern computers are often equipped with the Intelligent Platform Management Interface (IPMI) [41], which provides management and monitoring capabilities that are independent of the host system's CPU, firmware (e.g., BIOS [42], Unified Extensible Firmware Interface [UEFI] [43]), and operating system. For example, IPMI allows system administrators to remotely turn unresponsive machines on or off and install custom operating systems. IPMIs are connected to the management network, which can only be accessed by authorized system administrators. Collecting logs from the HPC system and forwarding the relevant logs to the security and information event management (SIEM) system, which could be external to the HPC system, is a component of the management zone. - High-performance networks: High-performance networks offer high bandwidth and low latency to connect computer nodes inside of the high-performance zone and data storage zone. They also support features that are unique to HPC, such as remote direct memory access (RDMA) over the network and the message passing interface (MPI) [44]. High-performance networks often use special communications standards and architectures (e.g., InfiniBand, Slingshot, Omni-Path, etc.). - Auxiliary networks: Additional auxiliary networks can be added to support usability and system manageability. For instance, a user network is constructed to allow users to manipulate or share data or remotely log into and access the compute nodes. Depending on the purpose of the networks, a subset of nodes from different zones are selected to be party to the networks. As an example, a user network contains the nodes in the access zone and the computer nodes in the high-performance computing zone. Cryptographic mechanisms are an effective means of providing data integrity."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 8)"}, {"role": "assistant", "content": "Glossary ...........................................................................................................23 | Appendix A. Glossary ...........................................................................................................23 | |\n| List of Tables | List of Tables | List of Tables |\n| Table 1."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nSelect a Security Official to be Assigned Responsibility for HIPAA Security | • Identify the individual who has final responsibility for security. 46 • Select an individual who is able to assess effective security to serve as the point of contact for security policy, implementation, and monitoring. | • Who in the organization: o Oversees the development and communication of security policies and procedures? o Is responsible for conducting the risk assessment? o Is responsible for conducting risk management? o Handles the results of periodic security evaluations and continuous monitoring? o Directs IT security purchasing and investment? o Ensures that security concerns have been addressed in system implementation? • Does the security official have adequate access and communications with senior officials in the organization, such as executives, chief information officers, chief compliance officers, and in-house counsel? • Who in the organization is authorized to accept risks from systems on behalf of the organization? |\n| 2. Assign and Document the Individual's Responsibility | • Document the assignment to one individual's responsibilities in a job description. 47 • Communicate this assigned role to the entire organization. | • Is there a complete job description that accurately reflects assigned security duties and responsibilities? • Have the staff members in the organization been notified as to whom to call in the event of a security problem? 48 |"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nwhich are advantages to solving auditability, resource consumption, scalability, central authority, and trust issues - all of which are challenges for network access control by traditional mechanisms.\nThis document presents general information for blockchain access control systems from the views of blockchain system properties, components, functions, and supports for access control policy models. Considerations for implementing blockchain access control systems are also included."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n| 1. Introduction............................................................................................................................. | 1. Introduction............................................................................................................................. | 1. Introduction............................................................................................................................. |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Scope and Purpose.................................................................................................................. 1 | 2."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.2.5 ICS Patrol\n\nForescout ICS Patrol (Version 1."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nf configuration setting information from an endpoint using OVAL [19]. A NEA extension will be developed to allow for event-driven and ad-hoc OVAL-based collection of configuration setting information.\nThe OVAL and SCAP communities have requested improvements to OVAL that need to be considered to better integrate OVAL with other SCAP specifications, to improve OVAL functionality, to make OVAL content easier to create, and to increase overall OVAL adoption. These updates are expected to be worked on in an international standards organization."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\n| 1. Introduction...................................................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Workshop Sessions ........................................................................................................................3 |\n| 2.1.1. Speaker Viewpoints......................................................................................................................3 |\n| 2.1.2. Key Highlights ...............................................................................................................................4 |\n| 2.2.1. Speaker Viewpoints......................................................................................................................5 |\n| 2.2.2. Key Highlights ...............................................................................................................................6 |\n| 2.3.1. Speaker Viewpoints......................................................................................................................6 |\n| 2.3.2. Key Highlights ...............................................................................................................................8 |\n| 2.4.1. Speaker Viewpoints......................................................................................................................9 |\n| 2.4.2. Key Highlights .............................................................................................................................11 |\n| 2.5.1. Speaker Viewpoints....................................................................................................................11 |\n| 2.5.2."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.5 (NIST 3.1.5)?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\n3.1.5 does not validate and escape user input before using ..."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "nist_control": "3.1.5", "cmmc_practice_id": "AC.L2-3.1.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 8)"}, {"role": "assistant", "content": ".......................12 |\n| 4. HPC Security Posture, Challenges, and Recommendations.............................................................14 |\n| 5.\nConclusions..................................................................................................................................19 |\n\n| References.......................................................................................................................................20 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Appendix A. HPC Architecture Variants.............................................................................................24 |\n| List of Figures |\n| Fig. 1. HPC System Reference Architecture..........................................................................................3 |\n\n## 1. Introduction\n\nIn 2015, Executive Order 13702 established the National Strategic Computing Initiative (NSCI) to maximize the benefits of high-performance computing (HPC) for economic competitiveness and scientific discovery. The ability to process large volumes of data and perform complex calculations at high speeds is a key part of the Nation's vision for maintaining its global competitive edge. Security is essential to achieving the anticipated benefits of HPC. HPC systems bear some resemblance to enterprise IT computing, which allows for the effective application of traditional IT security solutions. However, they also have significant differences. An HPC system is designed to maximize performance, so its architecture, hardware components, software stacks, and working environment are very different from enterprise IT."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 6)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1. Introduction...................................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. The Fundamentals..........................................................................................................................3 |\n| 3. The Procedures ..............................................................................................................................7 |\n| B. Glossary .....................................................................................................................101 |\n| Appendix A. Acronyms...................................................................................................................100 |\n| Appendix |\n| Appendix C. Security Requirement Assessment...............................................................................103 |\n| Appendix D. Organization-Defined Parameters...............................................................................107 |\n| Appendix E."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 4)"}, {"role": "assistant", "content": "s more important than ever because of the increasing reliance on technology, but there is often a divide between business/mission owners and security/technology management about the value of patching.\nThis publication frames patching as a critical component of preventive maintenance for computing technologies - a cost of doing business, and a necessary part of what organizations need to do in order to achieve their missions. This publication also discusses common factors that affect enterprise patch management and recommends creating an enterprise strategy to simplify and operationalize patching while also improving reduction of risk. Preventive maintenance through enterprise patch management helps prevent compromises, data breaches, operational disruptions, and other adverse events. ## Keywords\n\nenterprise patch management; patch; risk management; update; upgrade; vulnerability management. ## Acknowledgments\n\nThe authors wish to thank their colleagues who reviewed the document and contributed to its technical content, especially Mark Simos from Microsoft, and Jamie Brown, Vincent Gilcreest, and Glen Pendley from Tenable. The authors also appreciate the efforts of all the individuals and organizations that provided feedback on the public comment draft, especially BlackBerry, the Cybersecurity & Infrastructure Security Agency (CISA), the National Security Agency (NSA), The SECOND Advisories, Carla Brinker, and Ron Colvin. ## Audience\n\nThe primary audience for this publication is chief information officers, chief information security officers, cybersecurity directors and managers, and others who are responsible for managing organizational risk related to the use of software. Others with an interest in the topic, including business and mission owners, security engineers and architects, system administrators, and security operations personnel, may find portions of the publication to be informative."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control.\n\n'… Effective management of cybersecurity risk requires that agencies align information security management processes with strategic, operational, and budgetary planning processes…'"}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.11. QR-UOV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.11. QR-UOV"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| ACT-IAC | American Council for Technology and Industry Advisory Council. (2019). Zero Trust Cybersecurity Current Trends . Disponible en https://www.actiac.org/zero- trust-cybersecurity-current-trends |\n|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Anderson | Anderson B., McGrew D. (2017). Machine Learning for Encrypted Malware Traffic Classification: Accounting for Noisy Labels and Non- Stationarity. Proceedings of the 23rd ACMSIGKDD International Conference on Knowledge Discovery and Data Mining (ACM, Halifax, Nova Scotia, Canada), pp. 1723-1732. https://doi.org/10.1145/3097983.3098163 |\n| BCORE | Department of Defense CIO. (2007). Department of Defense Global Information Grid Architecture Vision Version 1.0 June 2007. Disponible en http://www.acqnotes.com/Attachments/DoD%20GIG%20Architectural% 20Vision,%20June%2007.pdf |\n| CSA-SDP | Cloud Security Alliance. (2015). SDP Specification 1.0. Disponible en https://cloudsecurityalliance.org/artifacts/sdp-specification-v1-0/ |\n| FIPS199 | National Institute of Standards and Technology. (2004). Standards for Security Categorization of Federal Information and Information Systems. (U."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n3.3.1 Software and Hardware Based Methods\n\nSoftware-based methods used to break or bypass authentication mechanisms have begun to appear."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Security Assessment?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n- o ENISA : European Union Agency for Network and Information Security (ENISA), 'Baseline Security Recommendations for IoT in the context of Critical Information Infrastructures' [10]\n- o ETSI : European Telecommunications Standards Institute (ETSI), 'Cyber Security for Consumer Internet of Things' [11]\n- o GSMA : Groupe Spéciale Mobile Association (GSMA), 'GSMA IoT Security Assessment' [12]\n- o IEC : International Electrotechnical Commission (IEC), 'IEC 62443-4-2, Edition 1.0, Security for industrial automation and control systems - Part 4-2: Technical security requirements for IACS components' [13]\n- o IIC : Industrial Internet Consortium (IIC), 'Industrial Internet of Things Volume G4: Security Framework' [14]\n- o IoTSF : IoT Security Foundation (IoTSF), 'IoT Security Compliance Framework, Release 2' [15]\n- o ISOC/OTA : Internet Society/Online Trust Alliance (OTA), 'IoT Security & Privacy Trust Framework v2.5' [16]\n- o NEMA : National Electrical Manufacturers Association (NEMA), 'Cyber Hygiene Best Practices' [17]\n- o OCF : Open Connectivity Foundation (OCF) 'OCF Security Specification Version 2.1.2' [18]\n- o PSA : Platform Security Architecture (PSA) Joint Stakeholder Agreement (JSA) Members, 'PSA Certified™ Level I Questionnaire, Version 2.0 Beta' [19]\n\n- [11] European Telecommunications Standards Institute (ETSI) (2019) Cyber Security for Consumer Internet of Things. ETSI Technical Specification 103 645 V1.1.1. 2 (European Telecommunications Standards Institute [ETSI], Sophia Antipolis Cedex, France). https://www.etsi.org/deliver/etsi\\_ts/103600\\_103699/103645/01.01.01\\_60/ts\\_103645v01 0101p.pdf\n- [12] Groupe Spéciale Mobile Association (GSMA) (2017) GSMA IoT Security Assessment. (Groupe Spéciale Mobile Association [GSMA], London, UK)."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "aft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - development cost, registration time, and the application learning curve for new subjects. + Integrated system. PACS will be fully integrated with other PIV system components that perform provisioning, enrollment, and finalization. + Fewer credentials. A single PIV Card provides a small set of authentication methods that are applicable to many applications and in many contexts."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n....................................................... | 33 |\n| D.3.1.2 | Test Results.............................................................................................................\n| 33 |\n| D.3.2 | Build 2 .............................................................................................................. | 35 |\n| D.3.2.1 | Configuration.......................................................................................................... | 35 |\n| D.3.2.2 | Test Results............................................................................................................. | 35 |\n| D.3.3 | Build 3 .............................................................................................................. | 37 |\n| D.3.3.1 | Configuration.......................................................................................................... | 37 |\n| D.3.3.2 | Test Results............................................................................................................. | 37 |\n| D.3.4 | Build 4 .............................................................................................................. | 39 |\n| D.3.4.1 | Configuration.......................................................................................................... | 39 |\n| D.3.4.2 | Test Results............................................................................................................. | 39 |\n| D.4.1 | Build 1 .............................................................................................................. | 41 |\n| D.4.1.1 | Configuration.......................................................................................................... | 41 |\n| D.4.1.2 | Test Results............................................................................................................."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nSeveral different classes of storage systems may be present inside of the data storage zone. In general, storage systems within this zone cannot be effectively separated from the HPC resources that they support from an administrative privilege perspective. Typical classes of storage found within this zone include PFSs and archival file systems that support campaign storage and protect against data loss. HPC systems may have other file systems that store nonuser data. For instance, the management zone often has its own file system that stores the OS images and configuration files. In that case, the file system is included in the corresponding function zone. HPC applications' initial data, intermediate results, and results are stored in the data storage zone and can be accessed during the application runtime and after the application's completion. External HPC users can also access user data through the login nodes and/or data transfer nodes in the access zone. The storage capacity of these file systems is often measured in petabytes and can reach up to exabytes. File systems within the data storage zone will generally use a transport mechanism appropriate to the tier. For example, high-bandwidth file systems may be attached to the HPC resource's high-performance network, while lower bandwidth file systems may use 10 Gbps or 100 Gbps ethernet. Access control for most HPC file systems is enforced by the operating system software of nodes on which these file systems are mounted. As such, file systems should not be mounted outside of their security boundaries. A rogue system that can mount a file system will have complete control of all file system data, can spoof packets on the highspeed network, and can possibly gain privileges elsewhere within other zones of the HPC\n\nOne important characteristic of the management zone is that it has a separate security posture because non-privileged users do not need to access the management servers or services in a direct way."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "..........................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5.\nAudit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 5)"}, {"role": "assistant", "content": "hus, the challenge of the method is to compose test cases that can comprehensively discover all faults. Alternatively, a system simulation method requires translating the policy to a simulated system.\nThe translation between systems may be difficult or impractical to implement if the policy logic is complicated or the number of policy rules is large. To answer these challenges, this report proposes an efficient and straightforward method for access control policy verification by applying a classification algorithm of machine learning, which does not require comprehensive test cases, oracle, or system translation but rather checks the logic of policy rules directly, making it more efficient and feasible compared to traditional methods. This report demonstrates an experiment for the proposed method with an example that uses current available machine learning tools to facilitate the random forest classification algorithm. The result illustrates its capabilities as well as parameter settings for performing the verification steps. Ultimately, three general applications are provided: enhancement of existing verification methods, verification of access control policies with numerical attributes, and policy enforcement that can be supported by the proposed machine learning policy verification method."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n| Focus Group Design...................................................................................................\n| 3 |\n| 2.1.2 | Focus Group Recruitment........................................................................................... | 3 |\n| 2.1.3 | Focus Group Data Collection..................................................................................... | 3 |\n| 2.1.4 | Focus Group Data Analysis........................................................................................ | 4 |\n| 2.2 SURVEY METHODOLOGY ..................................................................................................... 4 | 2.2 SURVEY METHODOLOGY ..................................................................................................... 4 | 2.2 SURVEY METHODOLOGY ....................................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 9)"}, {"role": "assistant", "content": "rdless of the incident response life cycle framework or model used, every organization should take incident response into consideration throughout their cybersecurity risk management activities. ## 1.\nIntroduction\n\nWithin this document, an event is any observable occurrence that involves computing assets, including physical and virtual platforms, networks, services, and cloud environments. Examples of events are user login attempts, the installation of software updates, and an application responding to a transaction request. Many events focus on security or have security implications. Adverse events are any events associated with a negative consequence regardless of cause, including natural disasters, power failures, or cybersecurity attacks. This guide addresses only adverse cybersecurity events . Additional analysis is often needed to determine whether adverse cybersecurity events indicate that a cybersecurity incident has occurred. ## A cybersecurity incident (or simply incident ) is\n\n…an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.04.05[01]: physical access restrictions associated with changes to the system are defined and documented."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n- Securely Provision (SP): Risk Management (RSK), Software Development (DEV), Systems Requirements Planning (SRP), Test and Evaluation (TST), Systems Development (SYS) - Operate and Maintain (OM): Systems Analysis (ANA) - Oversee and Govern (OV): Training, Education, and Awareness (TEA); Cybersecurity Management (MGT); Executive Cyber Leadership (EXL); Program/Project Management (PMA) and Acquisition - Protect and Defend (PR): Incident Response (CIR), Vulnerability Assessment and Management (VAM) - Analyze (AN): Threat Analysis (TWA), Exploitation Analysis (EXP) | Practices | Tasks | Notional Implementation Examples | References | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2) : Help ensure that the software will meet the security requirements and satisfactorily address the identified risk information."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\npart of a layered security approach to mitigating supply chain risk, this might be helpful at detecting, responding to, and recovering from situations where the installed patch was itself compromised.\n- CM-2, Baseline Configuration\n- CM-3, Configuration Change Control\n- CM-8, System Component Inventory\n- RA-7, Risk Response\n- SI-2, Flaw Remediation\n- SR-2, Supply Chain Risk Management Plan\n- SR-3, Supply Chain Controls and Processes\n- SR-5, Acquisition Strategies, Tools, and Methods\n\n- ID.AM-1: Physical devices and systems within the organization are inventoried\n- ID.AM-2: Software platforms and applications within the organization are inventoried\n- ID.AM-4: External information systems are catalogued\n- ID.AM-5: Resources (e.g., hardware, devices, data, time, personnel, and software) are prioritized based on their classification, criticality, and business value\n- ID.BE-3: Priorities for organizational mission, objectives, and activities are established and communicated\n- ID.BE-5: Resilience requirements to support delivery of critical services are established for all operating states (e.g., under duress/attack, during recovery, normal operations)\n- ID.GV-3: Legal and regulatory requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed\n- ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk\n- ID.RA-6: Risk responses are identified and prioritized\n- ID.SC-1: Cyber supply chain risk management processes are identified, established, assessed, managed, and agreed to by organizational stakeholders\n- PR.IP-1: A baseline configuration of information technology/industrial control systems is created and maintained incorporating security principles (e.g., concept of least functionality)\n- PR.IP-3: Configuration change control processes are in place\n- PR.IP-12: A vulnerability management plan is developed and implemented"}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| | | 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThis includes requirements from internal sources (e.g., the organization's policies, business objectives, and risk management strategy) and external sources (e.g., applicable laws and regulations). | PO.1.1 : Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. | Example 1 : Define policies for securing software development infrastructures and their components, including development endpoints, throughout the SDLC and maintaining that security. Example 2 : Define policies for securing software development processes throughout the SDLC and maintaining that security, including for open-source and other third-party software components utilized by software being developed. Example 3 : Review and update security requirements at least annually, or sooner if there are new requirements from internal or external sources, or a major security incident targeting software development infrastructure has occurred. Example 4 : Educate affected individuals on impending changes to requirements."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-218\n\n## Secure Software Development Framework (SSDF) Version 1.1:\n\nRecommendations for Mitigating the Risk of Software Vulnerabilities\n\nMurugiah Souppaya Karen Scarfone Donna Dodson\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-218\n\n\n\n## NIST Special Publication 800-218\n\n## Secure Software Development Framework (SSDF) Version 1.1:\n\nRecommendations for Mitigating the Risk of Software Vulnerabilities\n\nMurugiah Souppaya Computer Security Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nDonna Dodson*\n\n* Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-218\n\nFebruary 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.3.4\n\nDP Operations - Input/Output Controls\n\nThere must be adequate controls to insure:\n\n1) accountability, 2) that only authorized DP jobs are\nprocessed and, 3) that the resultant output is distri-\nbuted to only the authorized recipients."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 8)"}, {"role": "assistant", "content": "| Appendix A. Document Revisions.......................................................................................\n3 |\n\nGeneration and Establishment Methods\n\n## Scope\n\nThis document specifies the Cryptographic Module Validation Program (CMVP)-approved sensitive security parameter generation and establishment methods and supersedes those specified in International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 19790 Annex D and ISO/IEC 24759 paragraph 6.16. This document also supersedes SP 800-140Dr1. ## Normative references\n\nThis section identifies the normative references cited as ISO/IEC 19790 and ISO/IEC 24759. The specific editions to be used are ISO/IEC 19790:2012 and ISO/IEC 24759:2017. Please note that the version 19790:2012 referenced here includes the corrections made in 2015. National Institute of Standards and Technology (2019) Security Requirements for Cryptographic Modules . (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 140-3. https://doi.org/10.6028/NIST.FIPS.140-3\n\n## Terms and definitions\n\nThe following terms and definitions supersede or are in addition to ISO/IEC 19790. None at this time\n\n## Symbols and abbreviated terms\n\nThe following symbols and abbreviated terms supersede or are in addition to ISO/IEC 19790 and ISO/IEC 24759 throughout this document:\n\n## CMVP\n\nCryptographic Module Validation Program\n\n## FIPS\n\nFederal Information Processing Standard\n\n## ISO/IEC\n\nInternational Organization for Standardization/International Electrotechnical Commission\n\n## Document organization\n\n## General\n\nSection 6 of this document replaces the approved sensitive security parameter generation and establishment methods of ISO/IEC 19790 Annex D and ISO/IEC 24759 paragraph 6.16."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Media Protection\n\nDescription: Protect system media, both paper and digital; limiting access to data on system media to authorized users; and sanitizing or destroying system media before disposal or release for reuse."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST.\n\nDr. Arnold previously served as a Vice-President at Lucent Technologies Bell Laboratories where he directed the company's global standards efforts. His organization played a leading role in the development of international standards for Intelligent Networks and IP-based Next Generation Networks. In previous assignments at AT&T Bell Laboratories he had responsibilities in network planning, systems engineering, and application of information technology to automate operations and maintenance of the nationwide telecommunications network."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide?"}, {"role": "assistant", "content": "## Planning for a Zero Trust Architecture:\n\nA Planning Guide for Federal Administrators\n\nScott Rose Wireless Networks Division Communications Technology Laboratory\n\nMay 6, 2022\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.CSWP.20\n\n\n\n## Abstract\n\nNIST Special Publication 800-207 defines zero trust as a set of cybersecurity principles used when planning and implementing an enterprise architecture. These principles apply to endpoints, services, and data flows. Input and cooperation from various stakeholders in an enterprise is needed for a zero trust architecture to succeed in improving the enterprise security posture. Some of these stakeholders may not be familiar with risk analysis and management. This document provides an overview of the NIST Risk Management Framework (NIST RMF) and how the NIST RMF can be applied when developing and implementing a zero trust architecture. ## Keywords\n\narchitecture; cybersecurity; enterprise; network security; risk management; Risk Management Framework; zero trust. ## Disclaimer\n\nAny 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\n\nFor additional information on NIST's Cybersecurity programs, projects, and publications, visit the Computer Security Resource Center. Information on other efforts at NIST, the Information Technology Laboratory (ITL) and Communications Technology Laboratory (CTL) is also available. Zero trust related information is also found on the zero trust topic page."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n1. Develop the contingency planning policy statement. A formal policy provides the authority and guidance necessary to develop an effective contingency plan. 2. Conduct the business impact analysis (BIA). The BIA helps identify and prioritize information systems and components critical to supporting the organization's mission/business processes. A template for developing the BIA is provided to assist the user. 3. Identify preventive controls. Measures taken to reduce the effects of system disruptions can increase system availability and reduce contingency life cycle costs. 4. Create contingency strategies. Thorough recovery strategies ensure that the system may be recovered quickly and effectively following a disruption. 5. Develop an information system contingency plan. The contingency plan should contain detailed guidance and procedures for restoring a damaged system unique to the system's security impact level and recovery requirements. 6. Ensure plan testing, training, and exercises. Testing validates recovery capabilities, whereas training prepares recovery personnel for plan activation and exercising the plan identifies planning gaps; combined, the activities improve plan effectiveness and overall organization preparedness. 7. Ensure plan maintenance. The plan should be a living document that is updated regularly to remain current with system enhancements and organizational changes. This guide presents three sample formats for developing an information system contingency plan based on low-, moderate-, or high-impact level, as defined by Federal Information Processing Standard (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems . Each format defines three phases that govern actions to be taken following a system disruption. The Activation/Notification Phase describes the process of activating the plan based on outage impacts and notifying recovery personnel."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nThe security capabilities of the example solution are mapped to the NIST Cybersecurity Framework , the National Initiative for Cybersecurity Education Framework , and NIST Special Publication 800-53 . | D.2.2.1 | Configuration.......................................................................................................... | 18 |\n|-----------|---------------------------------------------------------------------------------------------------------------------------|------|\n| D.2.2.2 | Test Results............................................................................................................. | 18 |\n| D.2.3 | Build 3 .............................................................................................................. | 24 |\n| D.2.3.1 | Configuration.......................................................................................................... | 24 |\n| D.2.3.2 | Test Results............................................................................................................. | 24 |\n| D.2.4 | Build 4 .............................................................................................................. | 28 |\n| D.2.4.1 | Configuration.......................................................................................................... | 28 |\n| D.2.4.2 | Test Results............................................................................................................. | 28 |\n| D.3.1 | Build 1 .............................................................................................................. | 33 |\n| D.3.1.1 | Configuration.......................................................................................................... | 33 |\n| D.3.1.2 | Test Results............................................................................................................."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nOrganizations currently lack the ability to cost effectively distinguish trustworthy products from others, meaning they are genuine and have not been inappropriately altered. Having this ability is a critical foundation of cyber supply chain risk management (C-SCRM). C-SCRM is the process of identifying, assessing, and mitigating risks associated with the distributed and interconnected nature of supply chains. C-SCRM presents challenges to many industries and sectors, requiring a coordinated set of technical and procedural controls to mitigate risks throughout the design, manufacturing, acquisition, provisioning, operations, and decommissioning stages of a product's life.\n\nThe authoritative source of information regarding the provenance and integrity of the components provides a strong basis for trust in a computing device. Hardware roots of trust are the foundation upon which the computing system's trust model is built, forming the basis in hardware for providing one or more security-specific functions for the system. Incorporating hardware roots of trust into acquisition and lifecycle management processes enables organizations to achieve better visibility into supply chain attacks and to detect advanced persistent threats and other attacks. By leveraging hardware roots of trust capabilities as a computing device traverses the supply chain, we can maintain trust in the computing device throughout its operational lifecycle.\n\nCollaborators participating in this project submitted their capabilities in response to an open call in the Federal Register for all sources of relevant security capabilities from academia and industry (vendors and integrators). Those respondents with relevant capabilities or product components signed a Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to build this example solution."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 4)"}, {"role": "assistant", "content": "6.16, within the context of the Cryptographic Module Validation Program (CMVP). As a validation authority, the CMVP may supersede Annex D in its entirety. This document also supersedes SP 800-140Dr1.\n## Keywords\n\nCryptographic Module Validation Program; CMVP; FIPS 140 testing; FIPS 140-3; ISO/IEC 19790; ISO/IEC 24759; sensitive security parameter establishment methods; sensitive security parameter generation; testing requirement; vendor evidence; vendor documentation. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Supplemental Content\n\nSee https://csrc.nist.gov/projects/cmvp/sp800-140-series-info for details about the SP 800-140x series publications and their relationships to ISO/IEC 19790 and ISO/IEC 24759. ## Audience\n\nThis document is intended for use by vendors, testing labs, and the CMVP."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 10)"}, {"role": "assistant", "content": "activities are implemented in the U.S. Federal Government, we conducted a study to answer the following questions:\n\n- Q1. How do federal organizations determine which employees need to take RBT? - Q2.\nHow is RBT content obtained? - Q3. What approaches do federal organizations take in their RBT activities? - Q4. How do organizations determine the effectiveness of their RBT activities? - Q5. How do organizations approach compliance to government RBT mandates? - Q6. How well are RBT activities supported within organizations? - Q7. How do organizations determine the effectiveness of RBT? - Q8. What challenges do organizations face in implementing RBT activities? ## Our study results can serve as a resource for RBT implementers, organizational decision makers, guidance developers, and policy makers. This report documenting our study results can serve as a resource for federal professionals responsible for implementing, overseeing, or enacting policies related to RBT activities. In addition, our study is informing the update to NIST SP 800-50 Building a Cybersecurity and Privacy Learning Program , which will provide guidance to federal organizations. The report may also be valuable to organizations outside the U.S. Federal Government that implement similar training programs. ## METHODOLOGYGLYPH<c=2,font=/BAAAAA+HKGrotesk-Bold>\n\nTo gain a better understanding of RBT approaches and challenges within the government, it was important to hear directly from government employees who were responsible for implementing RBT activities within their organization as well as managers who oversaw those activities. Therefore, we conducted a two-phased study consisting of focus groups and a survey that allowed these professionals to tell us about their experiences. This report synthesizes the results from both the focus groups and survey. ## Focus groups provided important insights into role-based training challenges within organizations."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Contingency Planning Guide for Federal Information Systems provide? (Part 9)"}, {"role": "assistant", "content": "Information System Contingency Planning Process................................13 | Chapter 3. Information System Contingency Planning Process................................13 | Chapter 3. Information System Contingency Planning Process................................13 | Chapter 3."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | Documentation : The ability for the manufacturer and/or the manufacturer's supporting entity, to create, gather, and store information relevant to cybersecurity of the IoT device prior to customer purchase, and throughout the development of a device and its subsequent lifecycle."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n[SELECT FROM: access control policy and procedures; procedures for least privilege; list of system-generated privileged accounts; list of system administration personnel; system audit records; system configuration settings; system security plan; list of system-generated security functions or security-relevant information assigned to system accounts or roles; other relevant documents or records]\n\nFor example, many technical security requirements are satisfied by security capabilities that are examine the security functions of products and established configuration settings. Assessments built into commercial information technology products and systems. Product assessments are typically conducted by independent, third-party testing organizations. 5 These assessments can also be conducted to demonstrate compliance with industry, national, or international security standards as well as developer and vendor claims. Since many information technology"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.4.2 Security Control Map... 3.4.2, Security Control Map, maps the security characteristics of this example solution to cybersecurity standards and best practices. 3.4.2 Security Control Map\n\nAs explained in Section 3."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n........................................................ 1 | CHAPTERONE INTRODUCTION......................................................................................................\n1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................4 |\n| 2. HIPAA Security Rule .......................................................................................................................9 |\n| 3. Risk Assessment Guidance............................................................................................................14 |\n| 4. Risk Management Guidance .........................................................................................................24 |\n| 5. Considerations When Implementing the HIPAA Security Rule........................................................28 |\n| 5.1.2. Assigned Security Responsibility (§ 164.308(a)(2)) ....................................................................35 |\n| 5.1.3. Workforce Security (§ 164.308(a)(3)).........................................................................................36 |\n| 5.1.4. Information Access Management (§ 164.308(a)(4)) ..................................................................38 |\n| 5.1.5. Security Awareness and Training (§ 164.308(a)(5)) ...................................................................41 |\n| 5.1.6. Security Incident Procedures (§ 164.308(a)(6)) .........................................................................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.2.5, 3. 3.2.5, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes making on when to escalate or elevate incident response activities."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nEach FCB member should develop the ability to receive source vulnerability reports from reporters, maintain a database of received reports, and engage in secure communications (e.g., using a report tracking system). 2 The expectation for communication with the reporter should be established, including the initial acknowledgment, status updates, and agreed-upon method of communication. The actual receipt of a source vulnerability report may take multiple forms (e.g., email, web forms, or a phone hotline) and should be stated in a public policy. It is also\n\nAfter the vulnerability remediation release, monitoring of the stability of the product or service should continue. The responsible VDPO should update remediations as appropriate until further updates are no longer needed. The information gained during the root cause analysis should be used to update development life cycle elements to prevent similar vulnerabilities in new or updated products or services.\n\nPerson or organization responsible for the development, procurement, integration, modification, operation, maintenance, and/or final disposition of an information system."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.2.3 rsakpg2-crt ... 3.2.3 rsakpg2-crt\n\nrsakpg2-crt is the generator in the RSAKPG2 family such that the private key is in the Chinese Remainder Theorem format ( n , e , d , p , q , dP , dQ , qInv )."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n-  detect and prevent unauthorized software installation\n-  protect ICS networks from potentially harmful applications\n-  determine changes made to a network using change management tools\n-  detect unauthorized use of systems\n-  continuously monitor network traffic\n-  leverage anti-malware tools\n\nThe NCCoE, in conjunction with the NIST EL, collaborated with cybersecurity technology providers to develop and implement example solutions that demonstrate how manufacturing organizations can protect the integrity of their data from destructive malware, insider threats, and unauthorized software within manufacturing environments that rely on ICS.\n\nAn organization that is interested in protecting the integrity of a manufacturing system and information from destructive malware, insider threats, and unauthorized software should first conduct a risk assessment and determine the appropriate security capabilities required to mitigate those risks. Once the security capabilities are identified, the sample architecture and solution presented in this document may be used."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nThe purpose of this publication is to provide procedures for assessing the security requirements in NIST Special Publication (SP) 800-171, Protecting Controlled Unclassified Information (CUI) in Nonfederal Systems and Organizations [3]. Organizations can use the assessment procedures to generate evidence that the security requirements have been satisfied. The scope of the security assessments conducted using the procedures described in this publication is guided and informed by the system security plans for systems that process, store, or transmit CUI. The assessment procedures offer the flexibility to customize assessments based on organizational policies and requirements, known threat and vulnerability information, system and platform dependencies, operational considerations, and tolerance for risk. 1\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.02.01.a.03[01]: security literacy training is provided to system users on recognizing indicators of insider threat."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| Chapter 1."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 2)"}, {"role": "assistant", "content": "esources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-101r1 Natl. Inst. Stand. Technol. Spec. Publ. 800-101 Revision 1, 87 pages (May 2014) http://dx.doi.org/10.6028/NIST.SP. 800-101r1 CODEN: NSPUE2\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST Computer Security Division publications, other than the ones noted above, are available at http://csrc.nist.gov/publications."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nSP 800-53A provides a process that allows organizations to tailor the assessment procedures\noutlined in the guidance. Tailoring involves customizing the assessment procedures to match\nthe characteristics of the system and its environment of operation more closely. The tailoring\nprocess described in this guidance gives organizations the flexibility needed to avoid assessment\napproaches that are unnecessarily complex or costly while simultaneously meeting the\nassessment requirements and risk management principles established in the RMF. Tailoring\ndecisions are left to the discretion of the organization to maximize flexibility in developing\nassessment plans – applying the results of risk assessments to determine the extent, rigor, and\nlevel of intensity of the assessments needed to provide sufficient assurance about the security\nand privacy posture of the system. CHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n## 5.3.2.1 Scenario\n\n## 5.3.2.2 Resolution\n\n## 5.3.2.3 Other Considerations"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process.\nThe baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . A separate guideline, SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, provides specific guidelines that facilitate periodic assessment of security controls to ensure that controls have been implemented correctly, are operating as intended, and are meeting the organization's security requirements. ## 2 NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)\n\nNIST SP 800-39, Managing Information Security Risk , defines risk management as 'the program and supporting processes to manage information security risk to organizational operations (including mission, functions, and reputation), organizational assets, individuals, other organizations, and the Nation'. To integrate the risk management process throughout an organization and to address its mission and business concerns, a three-tiered approach is employed. The process is carried out across three tiers with the objective of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## 3.1. Identify the Intent of the Adversary"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nIn addition to the responsibility to protect organizational assets from the threats that exist in today's environment, organizations have a responsibility to consider and manage the risks to individuals when information systems process personally identifiable information (PII). 6 7 The information security and privacy programs implemented by organizations have complementary objectives with respect to managing the confidentiality, integrity, and availability of PII. While many privacy risks arise from unauthorized activities that lead to the loss of confidentiality, integrity, or availability of PII, other privacy risks result from authorized activities involving the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, or disposal of PII that enables an organization to meet its mission or business objectives. For example, organizations could fail to provide appropriate notice of PII processing depriving an individual of knowledge of such processing or an individual could be embarrassed or stigmatized\n\nExecuting the RMF requires close collaboration between information security programs and privacy programs. While information security programs and privacy programs have different objectives, those objectives are overlapping and complementary. Information security programs are responsible for protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction (i.e., unauthorized system activity or behavior) in order to provide confidentiality, integrity, and availability. Privacy programs are responsible for ensuring compliance with applicable privacy requirements and for managing the risks to individuals associated with the creation, collection, use, processing, dissemination, storage, maintenance, disclosure, or disposal (collectively referred to as 'processing') of PII."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Blockchain for Access Control Systems provide? (Part 4)"}, {"role": "assistant", "content": "for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, notice of one or more such claims has been received.\nBy publication, no position is taken by ITL with respect to the validity or scope of any patent claim or of any rights in connection therewith. The known patent holder(s) has (have), however, provided to NIST a letter of assurance stating either (1) a general disclaimer to the effect that it does (they do) not hold and does (do) not currently intend holding any essential patent claim(s), or (2) that it (they) will negotiate royalty-free or royalty-bearing licenses with other parties on a demonstrably nondiscriminatory basis with reasonable terms and conditions. Details may be obtained from ir8403-comments@nist.gov\n\nNo representation is made or implied that this is the only license that may be required to avoid patent infringement in the use of this publication. ## Executive Summary\n\nAccess control is concerned with determining the allowed activities of legitimate users and mediating every attempt by a user to access a resource in the system. The objectives of an access control system are often described in terms of protecting system resources against inappropriate or undesired user access. From a business perspective, this objective could just as well be described in terms of the optimal sharing of information. As current information systems and network architectures evolve to be more lightweight, pervasive, and interactive - such as the cloud and Internet of Things (IoT) - there is need for an access control mechanism to support the requirements of decentralization, scalability, and trust for accessing objects, all of which are challenging for traditional mechanisms."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n- Applying a threat-centric approach to security requirements specification;\n- Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16\n- Implementing dual authorization controls for the most critical or sensitive operations;\n- Limiting persistent storage to isolated enclaves or domains;\n- Implementing a comply-to-connect approach for systems and networks;\n- Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components;\n- Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components;\n- Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and\n- Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 3)"}, {"role": "assistant", "content": "of the data. However, some distributed or pervasive system environments wish to avoid the public-key encryption's all-or-nothing data access limitation when considering their performance requirements.\nAttribute-based encryption incorporates access control policies and attributes with encryption and decryption functions and a one-to-many authorization scheme that requires fewer keys than public-key encryption. It also utilizes collusion-resistance, which provides a more efficient and flexible attribute-based access control mechanism that supports high-performance systems (e.g., cloud, IoT, disrupt-tolerant networks, wireless sensor networks, mobile ad-hoc networks, and public search service systems). ## Keywords\n\naccess control; attribute-based access control; attribute-based encryption; authorization; encryptions; identity-based encryption; public-key encryption. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof-of-concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide?"}, {"role": "assistant", "content": "\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nFISMA requires federal agencies to implement appropriate controls to protect federal\ninformation and information systems from unauthorized access, use, disclosure,\ndisruption, or modification. The NIST RMF [NISTRMF] provides a process that integrates\nsecurity, privacy, and cyber supply chain risk management activities into the system\ndevelopment life cycle. It is expected that federal agencies and organizations that\nprovide services under these guidelines have already implemented the controls and\nprocesses required under FISMA and associated NIST risk management processes and\npublications."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Maintenance?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n....................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10.\nIncident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nMost United States federal government organizations are required to conduct cybersecurity role-based training for federal government personnel and supporting contractors who are assigned roles having security and privacy responsibilities. Despite the training mandate, there has been little prior effort to look broadly across federal organizations to see how they are implementing these training activities and what issues they are experiencing. This lack of understanding may be hindering the development of improvements and resources for training activities. To address this gap, the Usable Cybersecurity team at the National Institute of Standards and Technology conducted a research study consisting of focus groups and a survey to gain insights into the approaches of and challenges faced by federal organizations when implementing role-based training activities. This paper reports the results of the study and suggests actions that organizations can take to improve federal role-based training activities.\n\nCybersecurity role-based training (RBT) includes specialized training on policies, procedures, and tools for individuals who are assigned roles having security and privacy responsibilities [SP800-53]. Most United States (U.S.) Federal Government organizations are required to conduct RBT for applicable federal government personnel and supporting contractors [CISA2022].\n\nCybersecurity role-based training (RBT) includes specialized training on policies, procedures, tools, and methods for individuals who are assigned management, operational, and technical roles having security and privacy responsibilities [SP800-53]. RBT is tailored to specific roles within an organization and differs from the general cybersecurity awareness training targeted at all personnel within an organization."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.13 (NIST 3.1.13)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.13. 3.1.13."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.13", "cmmc_practice_id": "AC.L2-3.1.13", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Blockchain for Access Control Systems provide? (Part 7)"}, {"role": "assistant", "content": "## Table of Contents | Introduction ...........................................................................................................1 | Introduction ...........................................................................................................1 | |------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| | Blockchain System Components and Advantages for Access Control | Blockchain System Components and Advantages for Access Control | | Systems .................................................................................................................3 | Systems .................................................................................................................3 | | Access Control Functions of Blockchain AC Systems......................................6 | Access Control Functions of Blockchain AC Systems......................................6 | | Access Control Model Support..........................................................................12 | Access Control Model Support..........................................................................12 | | Considerations....................................................................................................15 | Considerations....................................................................................................15 | | 5.1 Management Considerations ..................................................................................................15 | 5.1 Management Considerations ..................................................................................................15 | | Security Considerations ..........................................................................................................15 | Security Considerations ..........................................................................................................15 | | Privacy Considerations ...........................................................................................................16 | Privacy Considerations ...........................................................................................................16 | | 5.3 5.4 Performance Considerations...................................................................................................16 | 5.3 5.4 Performance Considerations...................................................................................................16 | | 5.5 Standardization Considerations ..............................................................................................17 | 5.5 Standardization Considerations ..............................................................................................17 | | Conclusion...........................................................................................................18 | Conclusion...........................................................................................................18 | | References ....................................................................................................................19 | References ....................................................................................................................19 | | 3 - Example 2 of access control function points implemented in a blockchain system ....................8 | 3 - Example 2 of access control function points implemented in a blockchain system ....................8 | | Figure Figure 4 - Example 3 of access control function points implemented in a blockchain system ....................8 | Figure Figure 4 - Example 3 of access control function points implemented in a"}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes assist with maintaining cross-references | |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ID.RA-09 | The authenticity and integrity of hardware and software are assessed prior to acquisition and use | Medium | N1: See the notes for ID.RA."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nWith a renewed emphasis on the use of trustworthy, secure information systems and supply\nchain security, it is essential that organizations express their security and privacy requirements\nwith clarity and specificity in order to obtain the systems, components, and services necessary\nfor mission and business success. Accordingly, this publication provides controls in the System\nand Services Acquisition (SA) and Supply Chain Risk Management (SR) families that are directed\nat developers. The scope of the controls in those families includes information system, system\ncomponent, and system service development and the associated developers whether the\ndevelopment is conducted internally by organizations or externally through the contracting and\nacquisition processes. The affected controls in the control catalog include SA-8, SA-10, SA-11,\nSA-15, SA-16, SA-17, SA-20, SA-21, SR-3, SR-4, SR-5, SR-6, SR-7, SR-8, SR-9, and SR-11. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................"}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 3)"}, {"role": "assistant", "content": "413\n\nD. Richard Kuhn: 0000-0003-0050-1596\n\nMichael Ogata: 0000-0002-8457-2430\n\nSanjay (Jay) Rekhi: 0009-0008-8711-4030\n\nKim Schaffer: 0000-0003-3073-2395\n\nMurugiah Souppaya: 0000-0002-8055-8527\n\nA.J.\nStein: 0000-0003-1092-2642\n\nNoah Waller: 0000-0002-6979-9725\n\n## Contact Information\n\nhwsec@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8532/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe National Institute of Standards and Technology (NIST) hosted an in-person, all-day workshop on February 27, 2024, to discuss existing and emerging cybersecurity threats and mitigation techniques for semiconductors throughout their life cycle. The workshop obtained valuable feedback from industry, academia, and government to inform NIST's development of cybersecurity and supply chain standards, guidance, and recommended practices. The discussion focused on semiconductor development and highlighted cybersecurity measurements and metrics that utilize reference data sets to facilitate the testing, attestation, certification, verification, and validation of semiconductor components. It also emphasized the use of automated cybersecurity tools and techniques to secure manufacturing environments throughout the development life cycle. This report summarizes the content that was presented and discussed at the workshop. ## Keywords\n\ncybersecurity; hardware security; measurement; semiconductors; supply chain; vulnerabilities."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8.\nEvaluation (§ 164.308(a)(8)).......................................................................................................51 |\n| 5.2.1. Facility Access Controls (§ 164.310(a)).......................................................................................56 |\n| 5.1.9. Business Associate Contracts and Other Arrangements (§ 164.308(b)(1))................................54 |\n| 5.2.2. Workstation Use (§ 164.310(b)).................................................................................................59 |\n| 5.2.3. Workstation Security (§ 164.310(c)) ..........................................................................................61 |"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nsemiconductor industry since 1970 and provides global advocacy and technical leadership. It currently meets the cybersecurity needs of the industry, from material and equipment suppliers to end users.\nIn November 2023, the SMCC and NIST met to identify key areas and seek volunteers for both internal leadership and action. Attendees represented all semiconductor-related industries. Starting with about 40 in-person and almost 70 online attendees, the volunteers from that group have grown to about 50+ since January 2024 and have support from several CSOs from major organizations. Jennifer Lynn continued the SEMI presentation and stated that the SMCC is gaining momentum. The two days of whiteboard sessions at the November 2023 meeting established seven working groups: 1) factory cybersecurity implementation, 2) compliance readiness, 3) supply chain cybersecurity, 4) regulation and other specs, 5) threat sharing, 6) cybersecurity pre-standards engineering, and 7) outreach. Jennifer is leading working group 4, which will co-author the industry profile to map SEMI requirements to CSF 2.0. Anyone who wishes to aid in these efforts is encouraged to email cybersecurity@semi.org to talk to the working group leads and discuss how you might help. This work will establish the requirements for moving forward as well as how the existing structure can be protected for the rest of its lifetime. The SAE G-32 is working on integrating cybersecurity assurance into a CPS systems engineering and product-focused process. The SEMI SMCC will transition the design and manufacturing floor to one that incorporates auditable cybersecurity. A comment from the audience suggested that the SEMI standards for traceability at the wafer manufacturing are a good basis for forming a liaison activity between SEMI, IPC, and SAE. NIST"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 5)"}, {"role": "assistant", "content": "s and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n## Overview\n\n## Structure of SP 800-171\n\nSP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page). | Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Understanding the Security Requirements in SP 800-171\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n\n\n## Top 5 Frequently Asked Questions\n\n## Top five questions NIST receives on SP 800-171:\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8545/final, including related content, potential updates, and document history. The fourth round began in July 2022 and involved a thorough analysis of the theoretical and empirical evidence used to justify the security of the candidates. During this time, the submitters of SIKE acknowledged its insecurity and recommended against its further use. The submission teams of the unbroken fourth-round candidates were invited to present updates for their candidate algorithms at the Fifth NIST PQC Standardization Conference in Rockville, Maryland, on April 10-12, 2024. The submitters participated in a joint panel to discuss the candidates' merits, and several researchers presented work that was relevant to the PQC standardization process. - [1] Open quantum safe (OQS) algorithm performance visualizations. Available at https: //openquantumsafe.org/benchmarking. - [2] Alagic G, Apon D, Cooper DA, Dang QH, Dang T, Kelsey JM, Lichtinger J, Liu YK, Miller CA, Moody D, Peralta R, Perlner RA, Robinson A, Smith-Tone D (2022) Status Report on the Third Round of the NIST Post-Quantum Cryptography Standardization Process. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8413-upd1, Includes updates as of September 26, 2022. https://doi.org/10.6028/NIST.IR.8413-upd1\n- [3] National Institute of Standards and Technology (2015) SHA-3 Standard: PermutationBased Hash and Extendable-Output Functions. (Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) NIST FIPS 202. https://doi.org/10.6028/NIST.FIPS.202\n- [4] National Institute of Standards and Technology (2024) Module-Lattic-Based Digital Signature Standard. (Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) NIST FIPS 204."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MP.L2-3.8.17 (NIST 3.8.17)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.8.17) appliance is installed in a rack with network connections for the Management/Query traffic on Port 1 and SPAN traffic on Port 2 of the appliance."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.8.17", "cmmc_practice_id": "MP.L2-3.8.17", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 9)"}, {"role": "assistant", "content": "i | EXECUTIVE SUMMARY.........................................................................................................\niii |\n|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|\n| 1 INTRODUCTION................................................................................................................. | 1 INTRODUCTION................................................................................................................. | 1 |\n| 2 REPORTING CONVENTIONS.......................................................................................... | 2 REPORTING CONVENTIONS.......................................................................................... | 2 |\n| 3 SECURITY AWARENESS APPROACHES..................................................................... | 3 SECURITY AWARENESS APPROACHES..................................................................... | 3 |\n| 3.1 ANNUAL REQUIRED TRAINING............................................................................................."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.5 (NIST 3.4.5)?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.4.5. 3.4.5. 3.4.5) enhances portability between compliance frameworks."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "nist_control": "3.4.5", "cmmc_practice_id": "CM.L2-3.4.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n. . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . .\n. . . | 14 |\n| 3.4. | SIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 16 |\n| 4. Conclusion . . | . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| References . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms | . | 26 |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | 2 |\n| Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | 4 |\n| Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | 6 |\n| Table 4. Performance of HQC in thousands of cycles on x86_64 [1] . . . | Table 4."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 9)"}, {"role": "assistant", "content": "across all product life cycles, and the use of machine learning in chip design and manufacturing. The second speaker for the panel was Adam Golodner, advisor to the Semiconductor Industry Association.\nAdam spoke about the importance of leveraging and adapting NIST resources, like the Cybersecurity Framework (CSF). Adam highlighted four key reasons why a similar framework for hardware security and supply chains would be useful to the semiconductor industry:\n\n1. Frameworks like the CSF enable thoughtful, flexible, and configurable approaches to security and allow enterprises to adopt the processes and maturity levels that best move security forward for them. 2. A hardware security and supply chain framework can benefit from the recognition and adoption that the CSF has already earned. 3. The CSF and NIST have global reach and acceptance. Similarly, establishing an internationally recognized set of best practices will enhance security and innovation in a global hardware and supply chain environment. 4. NIST has the pedigree for getting security 'right.'\n\nFurthermore, Adam reflected that while security is core to many company brands, quantifying its return on investment is a C-suite and Board of Directors issue. The last panel member was Matthew Areno, Senior Principal Engineer for Intel Corporation. Matthew admitted that there is no industry standard to describe the phases of the supply chain for ICs. However, his expertise and history with the industry have enabled him to develop his own conceptual model that is divided into seven stages: concept, development, integration, manufacturing, testing, provisioning, and deployment. During his time at Intel, Matthew has worked to develop a threat model for Intel's supply chain. Intel discovered that each of their teams approached the exercise of threat modeling in different ways, which made it difficult and time-consuming for them to exchange information."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\nement Concepts and Applications\", 2nd Intl Workshop on Combinatorial Testing , Luxembourg, IWCT2013, IEEE, Mar. 2013. - [27] Zamli KZ, Othman RR, Zabil MH. On sequence based interaction testing.\nIn2011 IEEE Symposium on Computers & Informatics 2011 Mar 20 (pp. 662-667). IEEE. - [28] Kuhn DR, Higdon JM, Lawrence JF, Kacker RN, Lei Y. Efficient methods for interoperability testing using event sequences. FLIGHT TEST SQUADRON (46TH) EGLIN AFB FL; 2012 Aug 1. - [29] Yilmaz C, Fouche S, Cohen MB, Porter A, Demiroz G, Koc U. Moving forward 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"}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n3.2.3 TAILOR ASSESSMENT PROCEDURES\n\nIn a manner similar to how the controls from [SP 800-53] are tailored for the organization’s\nmission, business functions, characteristics of the system, and operating environment,\norganizations tailor the assessment procedures in Chapter 4 to meet specific organizational\nneeds. 3.2.3. 3.2.3."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.4.1 | Threats... 3.4.1 Threats\n\nNIST SP 800-161 Revision 1 provides a framework of ICT supply chain threats including insertion of counterfeits, unauthorized production, tampering, theft, and insertion of malicious software and hardware, as well as poor manufacturing and development practices in the ICT supply chain. 3.4.1 PR."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 6)"}, {"role": "assistant", "content": "| 2. Scope and Purpose..................................................................................................................\n1 | 2. Scope and Purpose.................................................................................................................. 1 |\n| 3. Definitions, Symbols and Abbreviations............................................................................... 2 | 3. Definitions, Symbols and Abbreviations............................................................................... 2 | 3. Definitions, Symbols and Abbreviations..............................................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nIn an open-ended question, we also asked what other job functions or roles the participants had in addition to their security awareness responsibilities. All but two participants had other substantial cybersecurity duties beyond awareness training, for example, incident response, supply chain risk management, audits and compliance, policy, information systems security management, privacy awareness and training, cybersecurity role-based training, and project management."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 7)"}, {"role": "assistant", "content": "s . . . . . . . . . . . . . . . . . . . . . . . . 3.1.4. Single-Factor OTP . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5. Multi-Factor OTPs\n\n. . . . . . . . . . . . . . . . . . . . . . . . .\n1\n\n2\n\n3\n\n4\n\n4\n\n5\n\n5\n\n5\n\n6\n\n6\n\n7\n\n7\n\n8\n\n8\n\n8\n\n9\n\n9\n\n9\n\n9\n\n9\n\n10\n\n11\n\n12\n\n13\n\n13\n\n17\n\n18\n\n23\n\n25\n\niii\n\n\fNIST SP 800-63B-4\nJuly 2025\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\n3.1.6. Single-Factor Cryptographic Authentication . . . . . . . . . . . . 3.1.7. Multi-Factor Cryptographic Authentication . . . . . . . . . . . . 3.2. General Authenticator Requirements . . . . . . . . . . . . . . . . . . . 3.2.1. Physical Authenticators\n\n. . . . . . . . . . . . . . . . . . . . . . 3.2.2. Rate Limiting (Throttling)\n\n. . . . . . . . . . . . . . . . . . . . . 3.2.3. Use of Biometrics\n\n. . . . . . . . . . . . . . . . . . . . . . . . . 3.2.4. Attestation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.5. Phishing Resistance . . . . . . . . . . . . . . . . . . . . . . . . 3.2.6. Verifier-CSP or IdP Communications . . . . . . . . . . . . . . . . 3.2.7. Replay Resistance . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.8. Authentication Intent\n\n. . . . . . . . . . . . . . . . . . . . . . . 3.2.9. Restricted Authenticators . . . . . . . . . . . . . . . . . . . . . 3.2.10. Activation Secrets\n\n. . . . . . . . . . . . . . . . . . . . . . . . . 3.2.11. Connected Authenticators . . . . . . . . . . . . . . . . . . . . . 3.2.12. Random Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.13. Exportability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. Authenticator Event Management . . . . . . . . . . . . . . . . . . . . . . . . 4.1. Authenticator Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1. Binding at Enrollment\n\n. . . . . . . . . . . . . . . . . . . . . . . 4.1.2. Post-Enrollment Binding . . . . . . . . . . . . . . . . . . . . . . 4.1.3. Binding to a Subscriber-Provided Authenticator . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Profile of the IoT Core Baseline for Consumer IoT Products support CMMC certification?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nmay wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2022-09-08\n\n## How to Cite this NIST Technical Series Publication:\n\nFagan M, Megas KN, Watrobski P, Marron J, Cuthill B (2022) Profile of the IoT Core Baseline for Consumer IoT Products. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8425. https://doi.org/10.6028/NIST.IR.8425\n\n## Author ORCID iDs\n\nMichael Fagan: 0000-0002-1861-2609\n\nKaterina N. Megas: 0000-0002-2815-5448\n\nPaul Watrobski: 0000-0002-6449-3030\n\nJeffrey Marron: 0000-0002-7871-683X\n\nBarbara B. Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecuirty@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 4)"}, {"role": "assistant", "content": "0Cr1. ## Keywords\n\nCryptographic Module Validation Program; CMVP; FIPS 140 testing; FIPS 140; ISO/IEC 19790; ISO/IEC 24759; testing requirement; vendor evidence; vendor documentation; security policy.\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Supplemental Content\n\nSee https://csrc.nist.gov/projects/cmvp/sp800-140-series-info for details about the NIST Special Publication (SP) 800-140x series publications and their relationships to ISO/IEC 19790 and ISO/IEC 24759. ## Audience\n\nThis document is intended for use by vendors, testing labs, and the CMVP. ## Table of Contents\n\nScope ................................................................................................................................ 1\n\nNormative references ....................................................................................................... 1\n\nTerms and definitions ...................................................................................................... 1\n\nSymbols and abbreviated terms......................................................................................"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 9)"}, {"role": "assistant", "content": "ating violations of the tree structure [SND13]. Model proof and data structure methods initially accept the policy under verification as faultless until tested against specified cases or requirements.\nFaults are then claimed if the policy model or data structure cannot hold. Therefore, in order to detect all possible faults embedded in a policy, the challenge is to compose test cases or requirements that can discover them. Other similar methods, however, may rely on a test oracle that contains all possible access control requests and access permissions as input to verify if requests' permissions conflict with expected permissions assigned to rules. Thus, excessive computing time or resources are required for large numbers of policy attributes. For example, given n, 2 n+1 access requests (1 for permission states) are required for the test oracle. Most of today's access control policies can easily have hundreds of attributes. Hence, test oracles will be too large to be practically performed. In addition to model proof and structured data, a simulated system is built to simulate the access control policy rules for verification. In such systems, each policy rule is represented by simulated system components such that faults can be detected by triggering the system functions that cause errors. For example, the access control Rule Logic Circuit Simulation (ACRLCS) system [ACRLCS] detects faults when rule circuits are added that conflict with existing logic circuits. ACRLCS allows error detecting and fixing to be performed in real time before adding rule circuits that further complicate the detecting effort. In other words, instead of checking by retracing the interrelations between rules after the policy is completed, it only checks the new added rule against previous 'correct' ones."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nProtecting the confidentiality, integrity, and availability (CIA) of user data is essential for the data storage zone. Data integrity can be compromised by malicious data deletion, corruption, pollution, or false data injection. Legitimate users may also mishandle sensitive data, leading to confidentiality breakdown. File metadata (e.g., file name, author, size, creation date) can also leak sensitive information about the files. - Environmental and physical threats: Physical or cyber attacks against facilities (e.g., power, cooling, water), unauthorized physical access, and natural disasters (e.g., fire, flood, earthquake, hurricane, etc.) are all potential threats to an HPC system. - Vulnerabilities introduced by prioritizing performance in HPC design and operation: HPC is designed to process large volumes of data and perform complex computations at very high speeds. Achieving the highest performance possible is a priority in HPC design and operation. Such prioritization, however, has its security implications. For instance, designers often make conscious decisions to build a less redundant system to achieve high performance, making the system less robust and potentially more vulnerable to attacks, such as DoS attacks. As another example, using a backup system to improve system robustness and high availability is a proven technology. However, building a spare or backup HPC system is often too costly. HPC systems can often lack storage backup due to the vast size of the data stored. Similarly, most HPC missions do not have a service-level agreement to justify the need for a full backup system at a backup location. All resources are poured into building the single best HPC system possible. - Supply chain threats: The HPC supply chain faces a variety of threats, from the theft of proprietary information to attacks on critical hardware components and software manipulation to gain unauthorized access."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n## Approaches and Challenges of Federal Cybersecurity Awareness Programs\n\n## Approaches and Challenges of Federal Cybersecurity Awareness Programs\n\nOrganizational security awareness programs experience a number of challenges, including lack of resources, difficulty measuring the impact of the program, and perceptions among the workforce that training is a boring, 'check-the-box' activity. While prior surveys and research have examined programs in the private sector, there is little understanding of whether these findings also apply within the U.S. government. To address this gap and better understand the needs, challenges, practices, and necessary competencies of federal security awareness teams and programs, NIST conducted a research study that leveraged both qualitative and quantitative methodologies. This companion document to NISTIR 8420 'Federal Cybersecurity Awareness Programs: A Mixed Methods Research Study' reports on a subset of study results focused on identifying the current approaches and challenges of security awareness programs within the federal government. Insights gained from these results are informing guidance and other initiatives to aid federal organizations in building effective security awareness programs. While focused on the U.S. government, findings may also have implications for organizational security awareness programs in other sectors."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "e\nMatthew A. Kozma\nChief Information Officer\n\nJohn Sherman\nPrincipal Deputy CIO\n\nMichael E. Waschull\nDeputy Chief Information Officer\n\nMark Hakun\nDeputy CIO for Cybersecurity and DoD SISO\n\nClifford M.\nConner\nCybersecurity Group and IC CISO\n\nKevin Dulany\nDirector, Cybersecurity Policy and Partnerships\n\nVacant\nDirector, Security Coordination Center\n\nNational Institute of Standards\nand Technology\nCharles H. Romine\nDirector, Information Technology Laboratory\n\nKevin Stine\nActing Cybersecurity Advisor, ITL\n\nMatthew Scholl\nChief, Computer Security Division\n\nKevin Stine\nChief, Applied Cybersecurity Division\n\nRon Ross\nFISMA Implementation Project Leader\n\nCommittee on National Security\nSystems\nMark G. Hakun\nChair\n\nSusan Dorr\nCo-Chair\n\nKevin Dulany\nTri-Chair—Defense Community\n\nChris Johnson\nTri-Chair—Intelligence Community\n\nVicki Michetti\nTri-Chair—Civil Agencies\n\nJoint Task Force Working Group\n\nVictoria Pillitteri\nNIST, JTF Leader\n\n McKay Tolboe\n DoD\n\nDorian Pappas\nIntelligence Community\n\nKelley Dempsey\nNIST\n\nEhijele Olumese\nThe MITRE Corporation\n\n Lydia Humphries\n Booz Allen Hamilton\n\nDaniel Faigin\nAerospace Corporation\n\nNaomi Lefkovitz\nNIST\n\nEsten Porter\nThe MITRE Corporation\n\n Julie Nethery Snyder\n The MITRE Corporation\n\nChristina Sames\nThe MITRE Corporation\n\nChristian Enloe\nNIST\n\nDavid Black\nThe MITRE Corporation\n\n Rich Graubart\n The MITRE Corporation\n\nPeter Duspiva\nIntelligence Community\n\nKaitlin Boeckl\nNIST\n\nEduardo Takamura\nNIST\n\n Ned Goren\n NIST\n\nAndrew Regenscheid\nNIST\n\nJon Boyens\nNIST\n\niii\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications"}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 10)"}, {"role": "assistant", "content": ". . 6.1. 6.2. Threat Mitigation Strategies . . . . . . . . . . . . . . . . . . . . . . . . Collaboration With Adjacent Programs\n\n. . . . . . . . . . . . . . . . . . 7. Privacy Considerations . . . . .\n. . . . . . . . . . . . . . . . . . . . . . . . . 7.1. Collection and Data Minimization . . . . . . . . . . . . . . . . . . . . . 7.1.1. Social Security Numbers . . . . . . . . . . . . . . . . . . . . . . 7.2. Notice and Consent\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3. Use Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4. 7.5. Redress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Privacy Risk Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6. Agency-Specific Privacy Compliance . . . . . . . . . . . . . . . . . . . . 8. Customer Experience Considerations\n\n. . . . . . . . . . . . . . . . . . . . . . 8.1. Usability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60\n\n60\n\n62\n\n63\n\n65\n\n66\n\n66\n\n66\n\n67\n\n67\n\n68\n\n68\n\n69\n\n70\n\n70\n\n8.1.1. General User Considerations During Identity Proofing and Enrollment 71\n\n8.1.2. Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.3. Identity Proofing and Enrollment\n\n. . . . . . . . . . . . . . . . . 8.1.4. Post-Enrollment\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . 8.2. Customer Success Considerations . . . . . . . . . . . . . . . . . . . . . 8.2.1. Support Multiple Types of Identity Proofing . . . . . . . . . . . . 8.2.2. Partner With Multiple Credible and Authoritative Sources . . . . 8.2.3. Offer Robust and Responsive Exception Handling Processes. . . . References\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A. Identity Evidence Examples by Strength . . . . . . . . . . . . . . . A.1. Fair Evidence Examples\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . A.2. Strong Evidence Examples . . . . . . . . . . . . . . . . . . . . . . . . . A.3."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Access Control\n\n## Getting Started with Access Control"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n5 There are four families in [SP 800-171] that do not contain enhanced security requirements: Audit and Accountability, Maintenance, Media Protection, and Physical Protection. | 3.1.1e | ENHANCED SECURITY REQUIREMENT Employ dual authorization to execute critical or sensitive system and organizational operations. | ENHANCED SECURITY REQUIREMENT Employ dual authorization to execute critical or sensitive system and organizational operations."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 6)"}, {"role": "assistant", "content": ", Naval Sea Systems Command (NAVSEA), NIST, Northrop Grumman, the Office of the Undersecretary of Defense for Research and Engineering, Red Hat, SAFECode, and the Software Engineering Institute (SEI).\n## Audience\n\nThere are two primary audiences for this document. The first is software producers (e.g., commercial-off-the-shelf [COTS] product vendors, government-off-the-shelf [GOTS] software developers, custom software developers, internal development teams) regardless of size, sector, or level of maturity. The second is software acquirers - both federal agencies and other organizations. Readers of this document are not expected to be experts in secure software development in order to understand it, but such expertise is required to implement its recommended practices. Personnel within the following Workforce Categories and Specialty Areas from the National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework [SP800181] are most likely to find this publication of interest:\n\n- Securely Provision (SP): Risk Management (RSK), Software Development (DEV), Systems Requirements Planning (SRP), Test and Evaluation (TST), Systems Development (SYS)\n- Operate and Maintain (OM): Systems Analysis (ANA)\n- Oversee and Govern (OV): Training, Education, and Awareness (TEA); Cybersecurity Management (MGT); Executive Cyber Leadership (EXL); Program/Project Management (PMA) and Acquisition\n- Protect and Defend (PR): Incident Response (CIR), Vulnerability Assessment and Management (VAM)\n- Analyze (AN): Threat Analysis (TWA), Exploitation Analysis (EXP)\n\n## Note to Readers\n\nWe encourage you to provide feedback on the SSDF at any time, especially as you implement the SSDF within your own organization and software development efforts. Having inputs from a variety of software producers will be particularly helpful to us in refining and revising the SSDF. The publication will be updated periodically to reflect your inputs and feedback."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nand security for wireless implantable medical devices,' Proceedings of the 28th international conference on Human factors in computing systems, ACM New York, NY, USA, 2010, pp 917-926.\n- [7] National Institute of Standards and Technology 'FIPS Pub 199: Standards for Security Categorization of Federal Information and Information Systems,' FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION, February 2004. - [8] S. Fischer and M. Zitterbart, 'Security in Sensor Networks,' Information Technology: Vol. 52, No. 6, 2010, pp. 311-312."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nECURITY AWARENESS APPROACHES..................................................................... | 3 SECURITY AWARENESS APPROACHES.....................................................................\n| 3 |\n| 3.1 ANNUAL REQUIRED TRAINING............................................................................................. | 3.1 ANNUAL REQUIRED TRAINING............................................................................................. | |\n| .................................................................................... | .................................................................................... | 3 |\n| 3.1.1 | Required Training Fulfillment | 3 |\n| 3.1.2 | Obtaining Training Content........................................................................................"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.4.1. 3.4.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| Practices | Tasks | Notional Implementation Examples | References | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | Example 4 : Require third parties to provide provenance 5 data and integrity verification mechanisms for all components of their software."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.2.1. 3.2.1 provides guidance on the creation of vulnerability disclosure acceptance policies. 3.2.1."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n- Applying a threat-centric approach to security requirements specification;\n- Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16\n- Implementing dual authorization controls for the most critical or sensitive operations;\n- Limiting persistent storage to isolated enclaves or domains;\n- Implementing a comply-to-connect approach for systems and networks;\n- Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components;\n- Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components;\n- Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and\n- Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 2. Preliminaries.......................................................................... | 3 |\n| 2.1. Auxiliary Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 7 |\n| 3. Ascon Permutations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.1. Internal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.2. Constant-Addition Layer 𝑝 𝐶 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.3. Substitution Layer 𝑝 𝑆 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 9 |\n| 3.4. Linear Diffusion Layer 𝑝 𝐿 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 4. Authenticated Encryption Scheme: Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1. Specification of Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.1. Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.2. Decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nMany of the management and operational controls (e.g., contingency planning controls, incident response controls, security awareness and training controls, personnel security controls, and physical security controls) needed to protect an information system may be excellent candidates for common security control status. The objective is to reduce security costs by centrally managing the development, implementation, and assessment of the common security controls designated by the agency-and subsequently, sharing assessment results with the owners of information systems where those common security controls are applied. Security controls not designated as common controls are considered system-specific controls and are the responsibility of the information system owner. System security plans should clearly identify which security controls have been designated as common security controls and which controls have been designated as system-specific controls. An agency may also assign a hybrid status to security controls in situations where one part of the control is deemed to be common, while another part of the control is deemed to be system-specific. For example, an agency may view the IR-1 (Incident Response Policy and Procedures) security control as a hybrid control with the policy portion of the control deemed to be common and the procedures portion of the control deemed to be system-specific. Hybrid security controls may also serve as templates for further control refinement. An agency may choose, for example, to implement the CP-2 (Contingency Plan) security control as a master template for a generalized contingency plan for all agency information systems with individual information system owners tailoring the plan, where appropriate, for system-specific issues."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "n before the\ncompletion of such companion publications. Thus, until each publication is completed, current\nrequirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and\ntransition purposes, federal agencies may wish to closely follow the development of these new\npublications by NIST. Organizations are encouraged to review draft publications during the designated public comment\nperiods and provide feedback to NIST. Many NIST publications, other than the ones noted above,\nare available at https://csrc.nist.gov/publications. Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology\nAttn: Computer Security Division, Information Technology Laboratory\n100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. i\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nReports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory\n(ITL) promotes the U.S. economy and public welfare by providing technical leadership for the\nNation’s measurement and standards infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT)."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nHAE-NCF-5: Network configuration for microservices-based applications (on-premises or in cloud) should include capabilities such as service discovery, encryption, service authentication, load balancing, observability (visibility of network traffic at layers 3-7), and canary rollouts. Further, visibility into microservices runtime behavior (and the ability to provide more dynamic security controls) can be enabled by attaching eBPF programs [52] to tracepoint events (the entry to or exit from any function in kernel or user space).\n\n- It should deliver common operational visibility and control across native network access provided by multiple cloud providers. The primary challenge is that public cloud providers have different proprietary architectures using their own 'constructs'. In order to provide a networking architecture that can 'cross clouds', one needs to leverage the cloud-native functionality (especially native cloud networking constructs) of each cloud; abstract that functionality with APIs; add advanced data plane features for highavailability, security, and operational visibility/control; and provide the tools to manage these features dynamically or automatically [42].\n- It should deliver a common ingress and egress security policy for application environments (e.g., VPCs, VNETs, VCNs) across clouds.\n- It should enable end-to-end encryption inside of the cloud as well as high-performance encryption from the data center to the cloud.\n- It should support automation for deployment and configuration."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Media Protection?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| | Information and Query Reception : The ability for the manufacturer and/or supporting entity to receive information and queries from the customer and others related to cybersecurity of the IoT device."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\ndent [13] information are currently being developed in the IETF Managed Incident Lightweight Exchange (MILE) [14] and the IETF Security Automation and Continuous Monitoring (SACM) [15] working groups.\nA ROLIE repository discovery mechanism [16] and a JSON-based version of ROLIE are also being developed in IETF MILE. Once completed, these solutions will be implemented in the NVD, and can be implemented by vendors to support SCAP content discovery and exchange. - NIST IR 8085: In support of the transition from CPE to SWID, an automated method is needed to support the generation of a CPE Name from a SWID tag to support legacy SCAP v1 tools. Draft NISTIR 8085 [17] is a start to support generation of CPE names from SWIDs, but more work is needed to complete this specification."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 5)"}, {"role": "assistant", "content": "n the topic, including business and mission owners, security engineers and architects, system administrators, and security operations personnel, may find portions of the publication to be informative.\n## Trademark Information\n\nAll names are registered trademarks or trademarks of their respective companies. ## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Executive Summary\n\nSoftware used for computing technologies must be maintained because there are many in the world who continuously search for and exploit flaws in software. Software maintenance includes patching , which is the act of applying a change to installed software - such as firmware, operating systems, or applications - that corrects security or functionality problems or adds new capabilities. Enterprise patch management is the process of identifying, prioritizing, acquiring, installing, and verifying the installation of patches, updates, and upgrades throughout an organization. In past perimeter-based security architectures, most software was operated on internal networks protected by several layers of network security controls."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 7)"}, {"role": "assistant", "content": "mers, end-users) use the cybersecurity capabilities of IoT devices, and support the on-going cybersecurity of the IoT device and the system and networks the device connects to (the digital ecosystem).\nProviding such non-technical cybersecurity support through educational materials or other types of non-technical tools and actions can benefit the entire IoT device ecosystem and allow manufacturers to better support the cybersecurity of devices throughout the entire device lifecycle. Both device cybersecurity capabilities and non-technical supporting capabilities are vital to customers' abilities to achieve their needs and goals. Similar to the IoT device cybersecurity capability core baseline in NISTIR 8259A, this IoT non-technical supporting capability core baseline is intended to give organizations a starting point for establishing nontechnical actions to support IoT device cybersecurity risk management. Specifically, this publication describes four recommended non-technical supporting capabilities related to the full lifecycle of cybersecurity management that manufacturers should implement to support the IoT devices they make for the full length of life: 1) Documentation; 2) Information and Query Reception; 3) Information Dissemination; and 4) Education and Awareness. A manufacturer's choice of non-technical supporting capabilities considers the purpose of the IoT device and the intended uses. Such actions make it easier for customers to understand and identify how IoT devices are built to meet their cybersecurity needs as well as the manufacturers' expectations for how the IoT device should be securely used. Figure 1 shows the four nontechnical supporting capabilities included in this baseline. Figure 1: How customers and others in the IoT device ecosystem will use the capabilities in the baseline if provided by IoT device manufacturers and supporting entities."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 6)"}, {"role": "assistant", "content": "nced challenges customizing security awareness information to a diverse workforce, and 40% struggle with ensuring materials are Section 508 compliant, especially when utilizing interactive approaches.\n- 85% of programs performed phishing simulations, which were often described as being one of the successful aspects of the security awareness program. While many focused on phishing click rates to gauge learning, others were more interested in reporting rates to demonstrate positive impacts on employee behavior. - 44% of surveyed programs recognized employees for practicing good security behaviors via a variety of means, such as virtual awards, personal thank-yous, and formal recognitions. Several focus group participants described several successful incentive initiatives related to phishing simulations. ## Informing the Security Awareness Program\n\n- Participants frequently collaborated with other groups in the organization to augment and inform their programs, most commonly other cybersecurity and IT teams, but also with others such as human resources and communications. - Programs used a variety of government and non-government resources to inform security awareness topics and approaches, e.g., workforce feedback, organizational security incident trends, news stories, and security mailing lists. - While only 27% of survey participants expressed challenges collaborating or sharing information with other federal security awareness professionals, focus group participants frequently highlighted their desire for increased collaboration. For example, they suggested the creation of a central repository of awareness materials, ongoing working groups, or realtime online forums. ## Program Success and Support\n\n- Training completion rates were the most common way programs try to determine their effectiveness (84%). Behavior based measures (e.g., phishing click rates, reporting of phishing emails or other incidents) were utilized by over half."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n\nExternal attackers may include foreign adversaries, criminal organizations, and cyber-activists who target an SSC for various reasons, such as espionage or sabotage. Internal attackers pose a significant risk, as they may have insider access to sensitive information - often using legitimate access rights - that allow them to launch attacks or steal confidential information. Additionally, both categories of threat actors may use a variety of techniques to compromise the SDLC environment and steal or manipulate software, such as phishing, malware, social engineering, and physical access. Therefore, companies should be aware of these risks and take appropriate measures (see Sec. 3.2) to secure their SSC.\n\n- Malware\n- Code reuse or the ingest of libraries and dependencies\n- Social engineering\n- Network-based attacks\n- Physical attacks"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n- Organizational computing devices lifecycle phases for technology include (among others) the following activities described in NIST SP 800-161 Revision 1, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations [3]: integration (including acceptance testing as described in this demonstration), operations, and disposal."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.3.1 | The Invitational Workshop | The Invitational Workshop | 49 |\n| | 3. 3.3.1 | Survey | 80 |\n| | | Study the Initiation Phase Environment | 80 |\n| | 4. 3.3.1 The Invitational Workshop\n\nThe PCIE Work Group, in the course of its activities, decided that an essential component of their final product."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n| RSA Key Pairs....................................................................................................................... | RSA Key Pairs....................................................................................................................... | RSA Key Pairs....................................................................................................................... | 36 |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|\n| | 6.1 General Requirements....................................................................................................... | 6.1 General Requirements....................................................................................................... | 36 |\n| | 6.2 Criteria for RSA Key Pairs for Key Establishment .......................................................... | 6.2 Criteria for RSA Key Pairs for Key Establishment .........................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n.......................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................\n7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................. 18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................"}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 10)"}, {"role": "assistant", "content": "| ..................................................................................................................\n4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS........................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nThe IoT product developer creates, gathers, and stores 15 information relevant to cybersecurity of the IoT product and its product components prior to customer purchase, and throughout the development of a product and its subsequent lifecycle."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nted with the chronology of the origin, development, ownership, location, and changes to a system or system component, including the personnel and processes that enabled those changes or modifications.\nThe generation of these data should be accompanied by corresponding mechanisms to validate, authenticate, and leverage them in policy decisions. From the above description of CI/CD pipelines and associated activities, one can identify the set of security assurance measures that need to be added:"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 8)"}, {"role": "assistant", "content": "s/usecases/manufacturing/integrity-ics. Once the example implementation is developed, you can adopt this solution for your own organization. If you do, please share your experience and advice with us.\nWe recognize that technical solutions alone\n\nwill not fully enable the benefits of our solution, so we encourage organizations to share lessons learned and best practices for transforming the processes associated with implementing this guide. To provide comments, join the community of interest, or to learn more about the project and example implementation, contact the NCCoE at manufacturing\\_nccoe@nist.gov. ## COLLABORATORS\n\nCollaborators participating in this project submitted their capabilities in response to an open call in the Federal Register for all sources of relevant security capabilities from academia and industry (vendors and integrators). Those respondents with relevant capabilities or product components signed a Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to build this example solution. Certain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 10)"}, {"role": "assistant", "content": "and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance.\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement. Tailoring: The process by which control baselines are modified to achieve certain organizational goals and objectives. Definitions provided are intended as plain language. Review the NIST Glossary for official NIST definitions. Determine if your business has CUI. ## General Tips for Getting Started with NIST SP 800-171\n\nEveryone will have different approaches to getting started, but here are a few tips to get you started down the right path:\n\nUnderstand current (or future) legal, regulatory, or contractual requirements for protecting CUI. The federal agency is responsible for communicating what CUI the business is responsible for protecting as part of the contractual arrangement. If there are questions, reach out to the contracting officer. The business may also have additional compliance requirements beyond SP 800-171. If so, an initial task might be to understand where the requirements overlap and where they differ. With that information, the business can begin addressing requirements that meet multiple compliance requirements. Understand how CUI flows into, within, and out of the business. \n\nInventorying what systems or components the business has, and how the data flows into, within, and out of those systems or components, helps practitioners understand the scope of applicability of SP 800-171 security requirements to business systems. \n\nScope and Applicability of SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nOver half of survey participants (55%) indicated that their organization updates RBT content every year (Figure 3). Almost 18% noted that their organization updates their training less often than once a year."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. | | multiple key-establishment transactions. Contrast with an ephemeral key pair. |\n|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Store-and- forward | A telecommunications technique in which information is sent to an intermediate station where it is kept and later sent to the final destination or to another intermediate station."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "ibed in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs.\nOrganizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control. - Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities. ## 4 Documenting the Control Selection Process\n\nTo aid in review activities, security planning, and risk assessments, organizations document the relevant decisions taken during the security control selection process, providing a sound rationale for those decisions. This documentation is essential when examining the security considerations for organizational information systems with respect to the potential impact on an organization's mission and business."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Configuration Management?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n## IoT Device Cybersecurity Capability Core Baseline\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nDevice cybersecurity capabilities are cybersecurity features or functions that computing devices provide through their own technical means (i.e., device hardware and software). This publication defines an Internet of Things (IoT) device cybersecurity capability core baseline, which is a set of device capabilities generally needed to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems. The purpose of this publication is to provide organizations a starting point to use in identifying the device cybersecurity capabilities for new IoT devices they will manufacture, integrate, or acquire. This publication can be used in conjunction with NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers ."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nSelect Initial Assurance Levels and Baseline Controls . . . . . . . . . . .\n\n3.3.4.\n\nIdentify Baseline Controls . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| 4.3.6 Audit Results/Reporting | 4.3.6 Audit Results/Reporting | 4.3.6 Audit Results/Reporting | 88 |\n|-------------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------|--------|\n| 4.3.6.1 | Potential Deficiencies | Potential Deficiencies | 88 |\n| 4.3.6.2 | Potential Effects of Deficiencies on Meeting System Mission | Potential Effects of Deficiencies on Meeting System Mission | ... 89 |\n| 4.3.7 | Reassess Audit Strategy | Reassess Audit Strategy | 89 |\n| AUDIT PARTICIPATION IN THE DEFINITION PHASE - PHASE II .... | AUDIT PARTICIPATION IN THE DEFINITION PHASE - PHASE II .... | AUDIT PARTICIPATION IN THE DEFINITION PHASE - PHASE II ...."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\nTHE INSTITUTE FOR COMPUTER SCIENCES AND TECHNOLOGY conducts research and provides scientific and technical services to aid Federal agencies in the selection, acquisition, application, and use of computer technology to improve effectiveness and economy in Government operations in accordance with Public Law 89-306 (40 U.S.C. 759), relevant Executive Orders, and other directives; carries out this mission by managing the Federal Information Processing Standards Program, developing Federal ADP standards guidelines, and managing Federal participation in ADP voluntary standardization activities; provides scientific and technological advisory services and assistance to Federal agencies; and provides the technical foundation for computer-related policies of the Federal Government. The Institute consists of the following centers:\n\nThe National Bureau of Standards has a special responsibility within the Federal Government for computer science and technology activities. The programs of the NBS Institute for Computer Sciences and Technology are designed to provide ADP standards, guidelines, and technical advisory services to improve the effectiveness of computer utilization in the Federal sector, and to perform appropriate research and development efforts as foundation for such activities and programs. This publication series will report these NBS efforts to the Federal computer community as well as to interested specialists in the academic and private sectors. Those wishing to receive notices of publications in this series should complete and return the form at the end of this publicaton. | 3."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n, September 2014. https://doi.org/10.6028/NIST.SP.800-56Br1\n- [SP 800-56C] Special Publication 800-56C Revision 1, Recommendation for Key Derivation Methods in Key Establishment Schemes , April 2018.\nhttps://doi.org/10.6028/NIST.SP.800-56Cr1\n- [SP 800-57] Special Publication 800-57 Part 1 Revision 4, Recommendation for Key Management , January 2016. https://doi.org/10.6028/NIST.SP.800-57pt1r4\n- [SP 800-89] Special Publication (SP) 800-89, Recommendation for Obtaining Assurances for Digital Signature Applications , November 2006. https://doi.org/10.6028/NIST.SP.800-89\n- [SP 800-90] Special Publication 800-90 series: Special Publication 800-90A Revision 1, Recommendation for Random Number Generation Using Deterministic Random Bit Generators , June 2015. https://doi.org/10.6028/NIST.SP.800-90Ar1"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 7)"}, {"role": "assistant", "content": ".......................................................24 | |\n| 4.7.1.\nProgram Managers/Agency Heads.............................................................................................27 | |\n| 4.7.2. Chief Information Officer (CIO) ..................................................................................................27 | |\n| 4.7.3. Information System Owner........................................................................................................27 | |\n| 4.7.4. Information Owner/Steward......................................................................................................27 | |\n| 4.7.5. Senior Agency Information Security Officer (SAISO)..................................................................27 | |\n| 4.7.6. System Security Manager/Officer ..............................................................................................27 | |\n| 4.7.7."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 7)"}, {"role": "assistant", "content": "...........38 |\n| 5.1.5. Security Awareness and Training (§ 164.308(a)(5)) ...................................................................41 |\n| 5.1.6.\nSecurity Incident Procedures (§ 164.308(a)(6)) .........................................................................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8. Evaluation (§ 164.308(a)(8)).......................................................................................................51 |\n| 5.2.1. Facility Access Controls (§ 164.310(a)).......................................................................................56 |\n| 5.1.9. Business Associate Contracts and Other Arrangements (§ 164.308(b)(1))................................54 |\n| 5.2.2. Workstation Use (§ 164.310(b)).................................................................................................59 |\n| 5.2.3. Workstation Security (§ 164.310(c)) ..........................................................................................61 |\n\n| 5.2.4. Device and Media Controls (§ 164.310(d)).................................................................................63 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 5.3.1."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.6 (NIST 3.3.6)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.3.6\n\nBulk Data Transmission\n\nData is often transmitted in bulk by mail or\n\nDepending on the data sensitivity and/or\n\nelectronically."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.3.6", "cmmc_practice_id": "AU.L2-3.3.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nd to implement security baselines. This collaboration between federal agencies minimizes duplicate effort that would otherwise be needed for these agencies to administer individual security baselines.\nAdditionally, the secure baseline content provided is easily extensible by other parties to implement their own security requirements."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nTechnology professionals who want to implement an approach like this can make use of NIST SP 180010C: How-To Guides . It provides specific product installation, configuration, and integration instructions for building the example implementation, allowing you to replicate all or parts of this project.\n\nNIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors. They are practical, user-friendly guides that facilitate the adoption of standards-based approaches to cybersecurity. They show members of the information security community how to implement example solutions that help them align more easily with relevant standards and best practices, and provide users with the materials lists, configuration files, and other information they need to implement a similar approach.\n\nintegrity-checking, change control management, and user authentication and authorization. The solution was tested in two distinct lab settings: a discrete manufacturing workcell, which represents an assembly line production, and a continuous process control system (PCS), which represents chemical manufacturing industries."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n3.5.2 Maintenance Plans for Scenario 2, Emergency Patching... 3.5.2 Maintenance Plans for Scenario 2, Emergency Patching\n\nOrganizations should consider using the same general approach for emergency patching as for routine patching, except with a highly accelerated schedule."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| | | C1: Consider periodic risk modeling updates for future AI model versions and derivatives after AI model release. C2: During risk modeling, consider checking that the AI model is not in a critical path to make significant security decisions without a human in the loop. | LLM07, LLM08, LLM09, LLM10 |\n| security requirements and risks during software design (secure by design) is key for improving software security and also helps improve development efficiency. | PW.1.2: Track and maintain the software's security requirements, risks, and design decisions. | Medium | No additions to SSDF 1.1 | AI RMF: Govern 4.1, 4.2; Map 2.1, 2.2, 2.3, 3.2, 3.3, 4.1, 4.2, 5.2; Manage 1.2, 1.3, 1.4 |\n| security requirements and risks during software design (secure by design) is key for improving software security and also helps improve development efficiency. | PW.1.3: Where appropriate, build in support for using standardized security features and services (e.g., enabling software to integrate with existing log management, identity management, access control, and vulnerability management systems) instead of creating proprietary implementations of security features and services."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\n|\n| [SP800-56A] | Barker EB, Chen L, Roginsky AL, Vassilev A, Davis R (2018) Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-56A, Rev. 3. https://doi.org/10.6028/NIST.SP.800-56Ar3 |\n| [ST] | Tahat N, Shatnawi S (2022) New Signature Scheme Based on Elliptic Curve and Factoring Problems Using Chaotic Map, Journal of Applied Security Research. Available at |\n| [SW] | https://www.tandfonline.com/doi/full/10.1080/19361610.2022.2041157 Sahai A, Waters B (2005) Fuzzy Identity-Based Encryption Cryptology, Proceedings of the 24th annual international conference on Theory and Applications of Cryptographic Techniques 2005. Pages 457-473. https://doi.org/10.1007/11426639_27 |\n| [TDN] | Ţiplea FL, Dragan C, Nica A (2017) Key-Policy Attribute-Based Encryption from Bilinear Maps, International Conference for Information Technology and Communications. https://doi.org/10.1007/978-3-319-69284-5_3 |\n| [TKN] | Tomida J, Kawahara Y, and Nishimaki R (2021) Fast, Compact, and Expressive Attribute-Based Encryption, Designs, Codes and Cryptography (2021) 89:2577- 2626. https://doi.org/10.1007/s10623-021-00939-8 |\n| [UMAS] | Umashankar SKA (2016) A Review on Attribute-Based Encryption (ABE) and ABE Types, Semantic Scholar - Computer Science."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nRisk assessments are also conducted to determine the potential that the use of an external provider for the development, implementation, maintenance, management, operation, or disposition of a system, system element, or service could create a loss, and the potential impact of that loss. The impact may be immediate (e.g., physical theft) or on-going (e.g., the ability of adversaries to replicate critical equipment because of theft). The impact may be endemic (e.g., limited to a single system) or systemic (e.g., including any system that uses a specific type of system component). Supply chain risk assessments consider vulnerabilities which may arise related to the disposition of a system or system element and from the use of external providers. Vulnerabilities in the supply chain may include a lack of traceability or accountability leading to the potential use of counterfeits, insertion of malware, or poor-quality systems. The use of external providers may result in a loss of visibility and control over how systems, system elements, and services are developed, deployed, and maintained. A clear understanding of the threats, vulnerabilities, and potential impacts of an adverse supply chain event can help organizations appropriately balance supply chain risk with risk tolerance. Supply chain risk assessments can include information from supplier audits, reviews, and supply chain intelligence. Organizations develop a strategy for collecting information, including a strategy for collaborating with providers on supply chain risk assessments. Such collaboration helps organizations leverage information from providers, reduce redundancy, identify potential courses of action for risk responses, and reduce the burden on providers."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n3.3.1 | Program Size... 3.3.1 Program Size\n\nParticipants in both the focus groups and survey were asked how many people (including federal employees and contractors) were covered by the organization's security awareness program (i."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| | security requirements and risks during software design (secure by design) is key for improving software security and also helps improve development efficiency."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 6)"}, {"role": "assistant", "content": "chnology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## HOW TO USE THIS PUBLICATION\n\nThis publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.2.1. 3.2.1. 3.2.1)."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nCybersecurity is a critical cross-cutting discipline that provides confidence that cyber-physical systems, their information, and supporting communications and information infrastructures are adequately safeguarded. CPS are increasingly being utilized in critical infrastructures and other settings. However, CPS have many unique characteristics, including the need for real-time response and extremely high availability, predictability, and reliability, which impacts cybersecurity decisions.\n\nDr. Arnold joined the National Institute of Standards and Technology (NIST) in September 2006 as Deputy Director, Technology Services, after a 33-year career in the telecommunications and information technology industry. He was appointed National Coordinator for Smart Grid Interoperability at in April 2009. He has been responsible for leading the development of standards underpinning the nation's Smart Grid. In October 2011, Dr. Arnold added an additional role as Director of Cyber Physical Systems within NIST's Engineering Laboratory (EL). Anticipating and meeting the measurement science and standards needs for technology-intensive manufacturing construction, and cyber-physical systems in ways that enhance economic prosperity and improve the quality of life , EL promotes U.S. innovation and industrial competitiveness in areas of critical national priority.\n\nDr. Arnold previously served as a Vice-President at Lucent Technologies Bell Laboratories where he directed the company's global standards efforts. His organization played a leading role in the development of international standards for Intelligent Networks and IP-based Next Generation Networks. In previous assignments at AT&T Bell Laboratories he had responsibilities in network planning, systems engineering, and application of information technology to automate operations and maintenance of the nationwide telecommunications network."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.11.01.a: the risk (including supply chain risk) of unauthorized disclosure resulting from the processing, storage, or transmission of CUI is assessed.\n\n[SELECT FROM: risk assessment policy and procedures; security planning policy and procedures; procedures for organizational assessments of risk; risk assessment; risk assessment results; risk assessment reviews; risk assessment updates; SCRM policy and procedures; inventory of critical systems, system components, and system services; procedures for organizational assessments of supply chain risk; acquisition policy; SCRM plan; system security plan; other relevant documents or records]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication contains comprehensive updates to the Risk Management Framework . The updates include an alignment with the constructs in the NIST Cybersecurity Framework; the integration of privacy risk management processes; an alignment with system life cycle security engineering processes; and the incorporation of supply chain risk management processes. Organizations can use the frameworks and processes in a complementary manner within the RMF to effectively manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. Revision 2 includes a set of organization-wide RMF tasks that are designed to prepare information system owners to conduct system-level risk management activities. The intent is to increase the effectiveness, efficiency, and cost-effectiveness of the RMF by establishing a closer connection to the organization's missions and business functions and improving the communications among senior leaders, managers, and operational personnel. 1 An information system is a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information [44 USC 3502]. The term information system includes, for example, general-purpose computing systems; industrial/process control systems; cyber-physical systems; weapons systems; super computers; command, control, and communications systems; devices such as smart phones and tablets; environmental control systems; embedded devices/sensors; and paper-based systems. 32 Different controls may need to be selected to mitigate the privacy risks associated with authorized processing of PII. For example, there may be a risk that individuals would be embarrassed or stigmatized if certain information is disclosed about them."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.6 (NIST 3.1.6)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.6. 3.1.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.6", "cmmc_practice_id": "AC.L2-3.1.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of information other than national security-related information in federal information systems.\n\nSection 3 of this document details MFA design principles, agency stakeholders that should be part of MFA requirements development, considerations for a phased MFA rollout, and examples of where agencies might choose to implement MFA."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nThe authors wish to thank Jason Blake and Stephanie Roberts from NIST; Gary Gapinski, Elyse Anderson, and Joshua Glemza from NASA; and Jamie Richardson and Chris Stone from Apple for their contributions to the mSCP. The authors appreciate Bob McSulla and Ryan Jaynes from Tenable for developing audit files based on the mSCP, testing the baselines for different macOS versions, and contributing to Appendix C. The authors also thank Isabel Van Wyk from NIST for editing the document. Finally, portions of this document are based on content from the mSCP Wiki, so the work of all Wiki contributors is appreciated.\n\nOrganizations using any baseline example should take a risk-based approach for selecting the appropriate settings and organizationally defined values depending on the context under which the baseline will be applied. Organizations can tailor any of the baselines to include controls specific to their needs and to produce evidence of control enforcement. Additional information on baseline customization can be found in SP 800-70 [2], which discusses the importance of customizing and testing baselines before applying them to a production system."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n2.3.1. Permitted Authenticator Types\n\n3.1.\n\n3.1.1. Passwords"}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 9)"}, {"role": "assistant", "content": "ents to be included in the core baseline. - The last column lists IoT reference examples that indicate existing sources of IoT device cybersecurity guidance specifying a similar or related capability.\nBecause the table only covers the basics of the capabilities, the references can be invaluable for understanding each capability in more detail and learning how to implement each capability in a reasonable manner."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n| A representative cohort of general users can help test the MFA solution before a general user rollout. | • Take volunteers or a selection of the general cohort to test the MFA solution.\n• Test IT support and help desk procedures. • Hold user feedback sessions. • Update communications and/or policy based on feedback. |\n| 4 | General user rollout | Once agencies are satisfied with testing from phases 1-3, it is time to proceed to a general rollout. This may not include some user populations that fall into corner cases. | • Provide multiple waves of communication around the MFA transition. • Allow for questions, answers, and feedback. • Provide a clear deadline for making the transition. • Update communications and/or policy based on feedback. • Monitor and grow adoption over time. |\n| 5 | Corner case users | Corner case requirements may require alternate MFA solutions. | • Enumerate requirements and potential solutions for corner cases. • Test potential solutions with phases 1-3 before rolling out to corner case users. |"}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n| Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | |\n|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ...................................................................................................................... | 1. Introduction ...................................................................................................................... | 1. Introduction ......................................................................................................................"}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 7)"}, {"role": "assistant", "content": "| Relevance to NIST SP 800-70 and the National Checklist Program ...........................\n| 2 |\n| | Document Structure.................................................................................................... | 2 |\n| Project Description .......................................................................................................... | Project Description .......................................................................................................... | 3 |\n| | Project Goals.............................................................................................................. | 3 |\n| | mSCP Content Use | ...................................................................................................."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 2)"}, {"role": "assistant", "content": "cludes other third parties such as business partners and various data and digital service providers. Practices in this QSG can be applied to manage cybersecurity risks from such relationships as well.\n## C-SCRM Overview\n\nAll types of technology rely on a complex, globally distributed, extensive, and interconnected supply chain ecosystem. Cybersecurity Supply Chain Risk Management (C-SCRM) is a systematic process for managing exposure to cybersecurity risk throughout supply chains and developing appropriate response strategies, policies, processes, and procedures. C-SCRM practitioners identify, assess, and mitigate cybersecurity risks throughout the supply chain at all levels of their organizations associated with information and communications technology (ICT) products and services. Potential risks include malicious functionality, counterfeit devices, or vulnerabilities derived from poor manufacturing and development practices within the supply chain. Effective C-SCRM requires stakeholders across the enterprise to actively collaborate, communicate, and take actions to secure favorable C-SCRM outcomes. ## NIST CSF 2.0: CYBERSECURITY SUPPLY CHAIN RISK MANAGEMENT (C-SCRM)\n\nA QUICK-START GUIDE\n\n## HOW TO USE THE CSF TO ESTABLISH AND OPERATE A C-SCRM CAPABILITY\n\n\n\n## Establishing a C-SCRM Capability\n\nThe CSF has a Category within its Govern Function dedicated to C-SCRM: the Cybersecurity Supply Chain Risk Management (GV.SC) Category. GV.SC contains the key outcomes that every organization should achieve through its C-SCRM capability. Additionally, many of the subcategories within the remainder of the CSF can be used to identify and communicate C- SCRM-related requirements internally for organizations and for their vendors. ## Perform these activities to establish your organization's C-SCRM capability:\n\nActivity 1: Create a C-SCRM strategy, objectives, policies, and processes."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| | 2.5.1.2 | 2.5.1.2 | Differences in Audit Approach | 34 | |-------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------|-----------| | | 2.5.2 Off-The-Shelf SoftwareATurnkey Systems | 2.5.2 Off-The-Shelf SoftwareATurnkey Systems | 2.5.2 Off-The-Shelf SoftwareATurnkey Systems | 35 | | | 2.5.2.1 | 2.5.2.1 | Differences from the AIS Life Cycle Matrix | 36 | | | 2.5.2.2 | 2.5.2.2 | Differences in Audit Approach | 37 | | | AIS | AIS | AIS | | | 2.6 | LIFE CYCLE DOCUMENTATION | LIFE CYCLE DOCUMENTATION | LIFE CYCLE DOCUMENTATION | 37 | | | 2.6.1 Needs Statement | 2.6.1 Needs Statement | 2.6.1 Needs Statement | 38 | | | 2.6.2 | Feasibility Study Document | Feasibility Study Document | 38 | | | 2.6.3 | Risk Analysis | Risk Analysis | 38 | | | 2.6.4 | Cost/Benefit Analysis | Cost/Benefit Analysis | 40 | | | 2.6.5 | System Decision Paper | System Decision Paper | 40 | | | 2.6.6 | Audit Plan | Audit Plan | 40 | | | 2.6.7 | Project Plan | Project Plan | 41 | | | 2.6.8 | Requirements Documents | Requirements Documents | 41 | | | | Functional Requirements Document | Functional"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n2 OT refers to 'programmable systems or devices that interact with the physical environment (or manage devices that interact with the physical environment). These systems/devices detect or cause a direct change through the monitoring and/or control of devices, processes, and events. Examples include industrial control systems, building management systems, fire control systems, and physical access control mechanisms.' [from NIST SP 800-37 Rev. 2]\n\n- Harden software, such as enforcing the principles of least privilege and least functionality (e.g., deactivating or uninstalling software services, features, and other components that are not needed). For additional information on hardening assets, especially those considered critical, see the NIST publication Security Measures for 'EO-Critical Software' Use Under Executive Order (EO) 14028 (July 9, 2021).\n- Acquire software that is likely to have fewer vulnerabilities over time compared to other software.\n- Work with software development partners that are likely to introduce fewer vulnerabilities into software over time, taking into consideration factors such as how rigorous their secure software development practices are, how quickly they address issues and release patches, how often problems are associated with their patches, and how transparent they are in their security-related communications.\n- Use managed services instead of software when feasible."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 9)"}, {"role": "assistant", "content": "| Key-Establishment Schemes Overview...............................................................................\n16 |\n| 4.1 Key-Establishment Preparations....................................................................................... 17 | 4.1 Key-Establishment Preparations....................................................................................... 17 | 4.1 Key-Establishment Preparations....................................................................................... 17 |\n| 4.2 Key-Agreement Process...................................................................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 10)"}, {"role": "assistant", "content": "|\n| 3.1 ANNUAL REQUIRED TRAINING.............................................................................................\n| 3.1 ANNUAL REQUIRED TRAINING............................................................................................. | |\n| .................................................................................... | .................................................................................... | 3 |\n| 3.1.1 | Required Training Fulfillment | 3 |\n| 3.1.2 | Obtaining Training Content........................................................................................ | 4 |\n| 3.1.3 | Update Frequency......................................................................................................."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| 3.11.6e | ENHANCED SECURITY REQUIREMENT Assess, respond to, and monitor supply chain risks associated with organizational systems and system components. | ENHANCED SECURITY REQUIREMENT Assess, respond to, and monitor supply chain risks associated with organizational systems and system components."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\nrd 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.\nIn 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"}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nThis section describes the installation of the Archer IRM system for this demonstration. Our instantiation of Archer IRM is viable for a lab environment, but the reader is encouraged to refer to the architecture planning guide on the Archer IRM website for specific guidance for your environment. We elected to install the Archer IRM system across two virtual machines -one hosting a Microsoft SQL database and the other hosting the remainder of the Archer IRM services. Note that the screenshots below are from our original installation of Archer IRM 6.9. During the course of the project, we updated our Archer IRM instance to version 6.10. As a result, some screenshots may differ in your implementation from what is presented in this document.\n\nThis section describes the installation of the IBM QRadar system for this demonstration. Our instantiation of IBM QRadar is viable for a lab environment, but the reader is encouraged to refer to the architecture planning guide on the IBM website for specific guidance for your environment."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\ngement, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems.\nThe Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\n- I. All data sources and computing services are considered resources. An enterprise relies on different resources to perform its mission: mobile devices, data stores, compute resources (including virtual), remote sensors/actuators, etc. All these components are resources and need to be considered in a ZTA. Some components (e.g., IoT sensors) may not be able to support some solutions such as configuration agents, application sandboxing, etc. so compensating technologies or alternative mitigations may be needed. If the resource lacks certain security capabilities, the enterprise may need to add a PEP component to provide that functionality. - II. The enterprise monitors and measures the integrity and security posture of all owned and associated resources. This tenet deals with the aspects of cyber hygiene for both enterprise-owned resources and those that may not be owned, but used in an enterprise workflow such as configuration, patching, application loading, etc. The state of resources should be monitored, and appropriate action taken when new information such as a new vulnerability or attack is reported or observed. The confidentiality and integrity of data on the resource should be protected. This requires enterprise admins to know how resources are configured, maintained, and monitored. - I. All communication is secured regardless of network location. In zero trust, the network is always considered contested. A ZTA should be designed with the assumption that an attacker is present on the network and could observe/modify communications. Appropriate safeguards should be in place to protect the confidentiality and integrity of data in transit. If a resource cannot provide this functionality natively, a separate PEP component may be necessary. - II. Access to individual enterprise resources is granted on a per -session basis. In an ideal zero trust architecture, every unique operation would undergo authentication and authorization before the operation is performed."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.5.1 3. 3.5.1 BIOS Protection\n\nUnauthorized modification of BIOS firmware by malicious software constitutes a significant threat because of the BIOS's unique and privileged position within the PC architecture."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 7)"}, {"role": "assistant", "content": "...103 |\n| Appendix D. Organization-Defined Parameters...............................................................................107 |\n| Appendix E.\nChange Log .................................................................................................................112 |\n\n## List of Tables\n\n| Table 1. Security Requirement Families ..............................................................................................3 |\n|------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Summary of Assessment Preparation Phase.......................................................................104 |\n| Table 3. Summary of Assessment Plan Development Phase.............................................................105 |\n| Table 4. Summary of Assessment Execution Phase..........................................................................106 |\n| Table 5. Summary of Assessment Analysis, Documentation, and Reporting Phase ...........................106 |\n| Table 6. Organization-Defined Parameters......................................................................................107 |\n\nTable 7. Change Log ....................................................................................................................... 113\n\n## Acknowledgments\n\nThe authors gratefully acknowledge and appreciate the significant contributions from individuals and organizations in the public and private sectors whose constructive comments improved the overall quality, thoroughness, and usefulness of this publication."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nin threats: The HPC supply chain faces a variety of threats, from the theft of proprietary information to attacks on critical hardware components and software manipulation to gain unauthorized access.\nSome HPC software (e.g., OS, applications), firmware, and hardware components have limited manufacturers, suppliers, and integrators, which makes diversification difficult. Limited suppliers also lead to shortages in the qualified workforce who can provide required technical support. - Insider threats: Insider threats come from people within the organization who have internal information and may have the privileges needed to access the HPC system. Insider threats can be classified into accidental/unintentional threats and malicious/intentional threats. Unintentional threats come from the unintended side effects of normal actions and activity. In contrast, a malicious insider may intentionally upload malicious code into the HPC system."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 5)"}, {"role": "assistant", "content": "GOVERNMENT PRINTING OFFICE WASHINGTON: 1988 ^ ## Table of Contents | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | xiii | |-------------------------|------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|--------| | CHAPTER 1 | CHAPTER 1 | CHAPTER 1 | CHAPTER 1 | | | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | 1 | | 1.1 | INTRODUCTION | INTRODUCTION | INTRODUCTION | 1 | | | 1.1.1 | Scope of the Audit Guide | Scope of the Audit Guide | 1 | | | 1.1.2 | How to Use the Audit Guide | How to Use the Audit Guide | 2 | | | 1.1.3 | Auditor Skills Needed | Auditor Skills Needed | 2 | | | 1.1.4 | Auditing in a Computerized Environment | Auditing in a Computerized Environment | 3 | | | 1.1.4.1 | 1.1.4.1 | The Need | 3 | | | 1.1.4.2 | 1.1.4.2 | The Scope of Audit in a Computerized Environment | 3 | | | 1.1.4.3 | 1.1.4.3 | Relationship Between Systems Development Audits and | | | | Operational Audits of Automated Information Systems (AISs) | Operational Audits of Automated Information Systems (AISs) |"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-03-25 Supersedes NIST SP 800-61r2 (August 2012) https://doi.org/10.6028/NIST.SP.800-61r2\n\n## How to Cite this NIST Technical Series Publication\n\nNelson A, Rekhi S, Souppaya M, Scarfone K (2025) Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-61r3. https://doi.org/10.6028/NIST.SP.800-61r3\n\n## Author ORCID iDs\n\nAlex Nelson: 0000-0002-3771-570X\n\nSanjay Rekhi: 0009-0008-8711-4030\n\nMurugiah Souppaya: 0000-0002-8055-8527\n\nKaren Scarfone: 0000-0001-6334-9486\n\n## Contact Information\n\n800-61-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory\n\n100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/61/r3/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis publication seeks to assist organizations with incorporating cybersecurity incident response recommendations and considerations throughout their cybersecurity risk management activities as described by the NIST Cybersecurity Framework (CSF) 2.0."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\ncontract language requires changes to secure programming practices, or changing a legacy protocol to Hypertext Transfer Protocol Secure (HTTPS) requires new communications acknowledgements.\nStoring AC data and logs on the blockchain raises questions of privacy as all subjects can see all entries, and auditable access history in the blockchain can violate user privacy. The exposed information may also provide information for attacking systems or users. If regulations require AC data owners who are accountable for all data privacy, then instead of storing private data on the blockchain, consider storing index numbers that are tied to private data in an off-the-chain system. Thus, subjects can own, secure, and even delete their privacy data. Otherwise, methods or tools facilitating cryptography need to be considered for privacy protection [GT]."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.0 (NIST 3.3.0)?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n3.3.0, GSM Association, Permanent Reference Document TW."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "nist_control": "3.3.0", "cmmc_practice_id": "AU.L2-3.3.0", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "sions. This documentation is essential when examining the security considerations for organizational information systems with respect to the potential impact on an organization's mission and business.\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3. Figure 3: Security Control Selection Process\n\n\n\n## 5 Assurance\n\nAppendix E in SP 800-53 Revision 4 provides an update to guidance regarding security assurance. This section outlines methods for agencies to establish measures of confidence that the implemented security controls provide the security capability required to protect critical missions and business operations. The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 9)"}, {"role": "assistant", "content": "ip with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose.\n## NIST SPECIAL PUBLICATION 1800-10B\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Protecting Information and System Integrity in Industrial Control System Environments:\n\nCybersecurity for the Manufacturing Sector\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Volume B:\n\nApproach, Architecture, and Security Characteristics\n\n## Michael Powell\n\nNational Cybersecurity Center of Excellence National Institute of Standards and Technology\n\nMichael Pease Keith Stouffer CheeYee Tang Timothy Zimmerman\n\nEngineering Laboratory National Institute of Standards and Technology\n\n## Matthew Zopf\n\nStrativia Largo, Maryland\n\nFINAL\n\nMarch 2022\n\nThis publication is available free of charge from https://doi.org/10.6028/NIST.SP.1800-10\n\nThe first draft of this publication is available free of charge from https://www.nccoe.nist.gov/publications/practice-guide/protecting-information-and-systemintegrity-industrial-control-system-draft\n\n\n\nJoseph Brule Chelsea Deane John Hoyt Mary Raguso Aslam Sherule Kangmin Zheng\n\nThe MITRE Corporation McLean, Virginia\n\n## DISCLAIMER\n\nCertain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n```\nid: sysprefs_screensaver_timeout_enforce title: \"Enforce Screen Saver Timeout\" discussion: | The screen saver timeout _MUST_ be set to $ODV seconds or a shorter length of time. This rule ensures that a full session lock is triggered within no more than $ODV seconds of inactivity. check: | /usr/bin/osascript -l JavaScript << EOS function run() { let timeout = ObjC.unwrap($.NSUserDefaults.alloc.initWithSuiteName('com.apple.screensaver') \\ .objectForKey('idleTime')) if ( timeout <= $ODV ) { return(\"true\") } else { return(\"false\") } } EOS result: string: \"true\" fix: | This is implemented by a Configuration Profile. references: cce: -CCE-91074-5 cci: -CCI-000057 800-53r5: -AC-11 -IA-11 800-53r4: -AC-11 srg: -SRG-OS-000029-GPOS-00010 disa_stig: -APPL-12-000004 800-171r2: -3.1.10 cis: benchmark: - 2.3.1 (level 1) controls v8: - 4.3 macOS: - \"12.0\" odv: hint: \"Number of seconds.\" default: 1200 stig: 900 cis_lvl1: 1200 cis_lvl2: 1200\n```"}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide? (Part 4)"}, {"role": "assistant", "content": "introduce and discuss potential areas to update as the NIST Cybersecurity for Internet of Things (IoT) program revises Foundational Cybersecurity Activities for IoT Device Manufacturers, NIST IR 8259.\nThe workshop was structured into two portions: a morning colloquium of plenary speakers and afternoon discussion sessions to dive deeper into the topics highlighted in the morning. The workshop yielded many discussions and significant feedback for NIST. This report summarizes what was discussed at the workshop and provides these insights to the broader public. The table of takeaways below illustrates the takeaways from the workshop from Section 3. Table 1 - Table of Takeaways\n\n| 1. | Government actions to support strengthening IoT cybersecurity need to be coordinated with industry. |\n|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | The use of robust frameworks and the adoption of open standards are crucial for effectively managing risks across heterogeneous environments. |\n| 3 | The dynamic nature of threats requires more context aware inputs, more proactive tracking and mitigation measures, and more examination into the inputs of the threat modeling approach. |\n| 4 | There are market opportunities to securely design the next wave of products with cybersecurity through end of life and instill incentives into the maintenance of existing products. |\n| 5 | The balance of shared responsibility between manufacturers and users for improving security varies by sector and needs the right incentives for both. |\n| 6 | There are broad challenges to integrating privacy objectives into IoT cybersecurity risk management. |\n| 7 | There is an increased awareness for evolving cybersecurity responsibilities across the players of the IoT ecosystem from manufacturers to users of the ecosystem."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 7)"}, {"role": "assistant", "content": "....7 |\n| 2.1.12. HPC Software..............................................................................................................................8 |\n| 2.1.13.\nUser Software.............................................................................................................................8 |\n| 2.1.14. Site-Provided Software and Vendor Software ...........................................................................8 |\n| 2.1.15. Containerized Software in HPC ..................................................................................................9 |\n| 3. HPC Threat Analysis......................................................................................................................10 |\n| 3.2.1. Access Zone Threats...................................................................................................................11 |\n| 3.2.2. Management Zone Threats........................................................................................................11 |\n| 3.2.3. High-Performance Computing Zone Threats..............................................................................12 |\n| 3.2.4. Data Storage Zone Threats.........................................................................................................12 |\n| 4. HPC Security Posture, Challenges, and Recommendations.............................................................14 |\n| 5."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nfunction of the adverse impacts that arise if the circumstance or event occurs, and the likelihood of occurrence. Types security and privacy risk (including supply chain risk); project risk; reputational risk; safety risk; strategic planning risk. 6 [OMB A-130] defines PII as 'information that can be used to distinguish or trace an individual's identity, either alone\n\nThe authorization boundary defines the system 36 for RMF execution to facilitate risk management and accountability. The system may be supported by one or more enabling systems that provide support during the system life cycle. Enabling systems are not contained within the authorization boundary of the system and do not necessarily exist in the system's environment of operation. An enabling system may provide common (i.e., inherited) controls for the system or may include any type of service or functionality used by the system such as identification and authentication services, network services, or monitoring functionality. Finally, there are other systems the system interacts with in the operational environment. The other systems are also outside of the authorization boundary and may be the beneficiaries of services provided by the system or may simply have some general interaction. 37\n\nDiscussion: Common controls are controls that can be inherited by one or more information systems. 60 Common controls can include controls from any [SP 800-53] control family, for example, physical and environmental protection controls, system boundary and monitoring controls, personnel security controls, policies and procedures, acquisition controls, account and identity management controls, audit log and accountability controls, or complaint management controls for receiving privacy inquiries from the public. Organizations identify and select the set of common controls and allocate those controls to the organizational entities designated as common control providers."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n| Figure 1: Memory Configurations...................................... | 6 |\n|-------------------------------------------------------------------------|-----|\n| Figure 2: SIM Card Size Formats [Orm09] ....................... | 8 |\n| Figure 3: SIM File System (GSM)..................................... | 9 |\n| Figure 4: Cellular Network Organization......................... | 12 |\n| Figure 5: Satellite Phone Network.................................... | 13 |\n| Figure 6: Mobile Device Tool Classification System...... | 17 |\n| Figure 7: Generic Triage Decision Tree........................... | 36 |\n\nMemory configurations among mobile devices have evolved over time. Feature phones were among the first types of devices that contained NOR flash and RAM memory. System and user data are stored in NOR and copied to RAM upon booting for faster code execution and access. This is known as the first generation of mobile device memory configurations.\n\nAs smartphones were introduced, memory configurations evolved, adding NAND flash memory. This arrangement of NOR, NAND and RAM memory is referred to as the second generation. This generation of memory configurations stores system files in NOR flash, user files in NAND and RAM is used for code execution."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 9)"}, {"role": "assistant", "content": "| Purpose and Scope ........................................................................................\n| 1 |\n| | 1.2 | Changes from Previous Versions.................................................................... | 1 |\n| | 1.3 | Publication Structure......................................................................................."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nscovered recently [7], show that industrial control systems are evolving, bringing powerful capabilities into the critical infrastructure environment along with new and yet undiscovered threats.\nAdditionally, incidents witnessed in the recent years have underlined an unprecedented level of sophistication in the threats targeting ICS environments. A prime example of this sophistication is the Stuxnet infection, which used four distinct and previously unknown zero-day exploits, and leveraged multiple stolen certificates for the injection of its rootkit: when the certificate used for the installation of the rootkit was reported stolen, and consequently revoked by the Symantec (Verisign) Certification Authority, the malware was immediately patched remotely to utilize a second stolen certificate. Stuxnet was not an isolated incident: in 2011, a threat sharing similar characteristics to Stuxnet was discovered and was shown to have been generated by the same authors, or those who have access to the Stuxnet source code [7]."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n.............6 |\n| 2.1.9. Basic Services................................................................................................................................7 |\n| 2.1.10.\nConfiguration Management.......................................................................................................7 |\n| 2.1.11. HPC Scheduler and Workflow Management..............................................................................7 |\n| 2.1.12. HPC Software..............................................................................................................................8 |\n| 2.1.13. User Software.............................................................................................................................8 |\n| 2.1.14. Site-Provided Software and Vendor Software ...........................................................................8 |\n| 2.1.15. Containerized Software in HPC ..................................................................................................9 |\n| 3. HPC Threat Analysis......................................................................................................................10 |\n| 3.2.1. Access Zone Threats...................................................................................................................11 |\n| 3.2.2. Management Zone Threats........................................................................................................11 |\n| 3.2.3. High-Performance Computing Zone Threats..............................................................................12 |\n| 3.2.4. Data Storage Zone Threats.........................................................................................................12 |\n| 4."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n- Securely Provision (SP): Risk Management (RSK), Software Development (DEV), Systems Requirements Planning (SRP), Test and Evaluation (TST), Systems Development (SYS)\n- Operate and Maintain (OM): Systems Analysis (ANA)\n- Oversee and Govern (OV): Training, Education, and Awareness (TEA); Cybersecurity Management (MGT); Executive Cyber Leadership (EXL); Program/Project Management (PMA) and Acquisition\n- Protect and Defend (PR): Incident Response (CIR), Vulnerability Assessment and Management (VAM)\n- Analyze (AN): Threat Analysis (TWA), Exploitation Analysis (EXP)\n\nThe SSDF defines only a high-level subset of what organizations may need to do, so organizations should consult the references and other resources for additional information on implementing the practices. Not all practices are applicable to all use cases; organizations should adopt a risk-based approach to determine what practices are relevant, appropriate, and effective to mitigate the threats to their software development practices."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## 03.01.06 Least Privilege - Privileged Accounts\n\n[SELECT FROM: access control policy and procedures; procedures for least privilege; list of system-generated privileged accounts; list of system administration personnel; system audit records; system configuration settings; system security plan; list of system-generated security functions or security-relevant information assigned to system accounts or roles; other relevant documents or records]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nance. 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.\nThe 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.2.3 | Scenario 3: Verification of Components During Use... 3.2.3 Scenario 3: Verification of Components During Use\n\nIn this scenario, the computing device has been accepted by the organization (Scenario 2) and has been provisioned for the end user. 3.2.3 | Platform Integrity Incident Management ..."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 4)"}, {"role": "assistant", "content": "ed as independent, third-party assessments or as government-sponsored assessments. The assessments can be applied with various degrees of rigor based on customer-defined depth and coverage attributes.\n## Keywords\n\nassessment; assessment method; assessment object; assessment procedure; assurance; Controlled Unclassified Information; coverage; FISMA; NIST Special Publication 800-171; NIST Special Publication 800-53A; nonfederal organization; nonfederal system; security assessment; security requirement. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 6)"}, {"role": "assistant", "content": "................................14 |\n| 3.2.3. Other Agencies ...........................................................................................................................14 |\n| 3.2.4.\nProcurement Teams...................................................................................................................14 |\n| 3.2.5. Compliance Teams .....................................................................................................................15 |\n| 3.2.6. Legal Teams................................................................................................................................15 |\n| 3.2.7. Technology Vendors...................................................................................................................15 |\n| 3.4.1. Local Agency MFA Architectures................................................................................................17 |\n| 3.4.2. State MFA Deployments.............................................................................................................21 |\n| 3.4.3. Implementing MFA with VPNs ...................................................................................................25 |\n| 4. Key Takeaways.............................................................................................................................29 |\n| References.......................................................................................................................................31 |\n| Appendix A. Technology Components Relevant to MFA for CJIS Access .............................................32 |\n\n| Appendix B."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Incident Response?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\noperations, exercising an incident response plan, and monitoring network traffic). Individuals are the people applying the specifications, mechanisms, or activities described above.\n\n## 3.6. Incident Response"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.1. 3.2.10. 3.2.11."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nScope and Applicability of SP 800-171. The security requirements in NIST SP 800-171 are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. Appropriately scoping requirements is an important factor in determining protection-related investment decisions and managing security risks for your business. You may limit the scope of the security requirements by isolating the system components in a separate security domain. Isolation can be achieved by implementing subnetworks with firewalls or other boundary protection devices. Security domains may employ physical separation, logical separation, or a combination of both. This approach can provide adequate security for CUI and avoid increasing the organization's security posture beyond what it requires for protecting its missions, operations, and assets.\n\n- Permit only qualified and authorized individuals to access the system for the purpose of initiating changes. Access restrictions include physical and logical access controls, software libraries, workflow automation, media libraries, abstract layers (i.e., changes implemented into external interfaces rather than directly into the system), and change windows (i.e., changes occur only during specified times)."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nTechnical Contingency Planning Considerations.....................................43 | Chapter 5. Technical Contingency Planning Considerations.....................................43 | Chapter 5."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Validating the Integrity of Computing Devices provide?"}, {"role": "assistant", "content": "\n\n## NIST SPECIAL PUBLICATION 1800-34\n\n## Validating the Integrity of Computing Devices\n\nIncludes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C)\n\nJon Boyens Christopher Brown Chelsea Deane Tyler Diamond* Nakia Grayson Jason Hurlburt Celia Paulsen William T. Polk Andrew Regenscheid Karen Scarfone Murugiah Souppaya\n\n*Former employee; all work for this publication was done while at employer\n\nDECEMBER 2022\n\nFINAL\n\nThis publication is available free of charge from https://doi.org/10.6028/NIST.SP.1800-34\n\n\n\nNIST SPECIAL PUBLICATION 1800-34\n\n## Validating the Integrity of Computing Devices\n\nIncludes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C)\n\nJon Boyens\n\nTyler Diamond* Nakia Grayson Celia Paulsen William T. Polk Andrew Regenscheid Murugiah Souppaya National Cybersecurity Center of Excellence Information Technology Laboratory\n\nChristopher Brown Chelsea Deane Jason Hurlburt The MITRE Corporation McLean, Virginia\n\nKaren Scarfone Scarfone Cybersecurity Clifton, Virginia\n\n*Former employee; all work for this publication was done while at employer\n\nFINAL\n\nDecember 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## NIST SPECIAL PUBLICATION 1800-34A\n\n## Validating the Integrity of Computing Devices\n\nVolume A: Executive Summary\n\nJon Boyens Tyler Diamond* Nakia Grayson Celia Paulsen William T."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nThe Organization for the Advancement of Structured Information Standards (OASIS) standard XACML proposes basic processing entities for AC systems. Each entity handles a different stage of processing a user's access request, as shown in Figure 1. These functional components may be physically and logically separated and distributed rather than centralized, such as several functional 'points' that are the service node for the retrieval and management of the policy, along with some logical components for handling the context or workflow of AC data retrieval and assessment."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nDescription: Ensuring personnel are made aware of the security risks associated with their activities and of the applicable laws, directives, policies, standards, regulations, or procedures related to the security of organizational systems; and ensuring that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.\n\nRegularly provide basic and advanced security literacy training to new and existing staff. Customize the content to make it relevant -based on the systems that personnel have authorized access to, contextualized to the work environments of personnel (e.g., telework, shop floor), and tailored to the specific roles of personnel. The content should include:"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\n.g., encryption) which require limited human interaction, particularly with users, education and awareness addresses the human-in-the-loop and so depends, in large part, on human-factors for efficacy.\nAll three teams specifically considered how their designs could be 'easiest' for users to use, understand, and be most accessible. Teams 1 and 3 incorporated gamification and other interactive elements to encourage users to pursue cybersecurity topics. For example, Team 3 attempted to gamify the pursuit of cybersecurity knowledge relative to the product by building out 'levels' of concepts that build upon each other so that users could 'level up' at their pace. Understanding and encouraging cybersecurity engagement has been a focus of research for the SOUPS community [8][9][10][11][12][13], and so the teams brought the insights from that research to the practical tasks of the Design-A-Thon. The contextual nature of cybersecurity education and awareness approaches was apparent when two teams (i.e., Teams 2 and 3) selected the same product but developed different approaches and focused on different aspects of the design. Teams 2 and 3 homed in on different information that may be useful at different times during the product's lifecycle. In one case, Team 2 focused on ensuring information was at users' fingertips, particularly when support was needed. In the other case, Team 3 considered how individuals could be encouraged to engage on cybersecurity education and awareness outside of times they needed support, landing on gamification elements. Research shows that gamification of cybersecurity education and awareness can drive engagement for individuals around the subject [14], but for IoT products, gamification elements should not get in the way when users need support or specific information."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nTemoshok D, Abruzzi C, Choong YY, Fenton JL, Galluzzo R, LaSalle C, Lefkovitz N,\nRegenscheid A, Vachino M (2025) Digital Identity Guidelines: Identity Proofing and\nEnrollment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST\nSpecial Publication (SP) NIST SP 800-63A-4. https://doi.org/10.6028/NIST.SP.800-63A-4"}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 3)"}, {"role": "assistant", "content": "a software test, access control policy verification relies on methods such as model proof, data structure, system simulation, and test oracle to verify that the policy logic functions as expected.\nHowever, these methods have capability and performance issues related to inaccuracy and complexity limited by applied technologies. For instance, model proof, test oracle, and data structure methods initially assume that the policy under verification is faultless unless the policy model cannot hold for test cases. Thus, the challenge of the method is to compose test cases that can comprehensively discover all faults. Alternatively, a system simulation method requires translating the policy to a simulated system. The translation between systems may be difficult or impractical to implement if the policy logic is complicated or the number of policy rules is large. To answer these challenges, this internal report (IR) proposes an efficient and straightforward method for access control policy verification by applying a classification algorithm of machine learning, which does not require comprehensive test cases, oracle, or system translation but rather checks the logic of policy rules directly, making it more efficient and feasible compared to traditional methods. ## Keywords\n\nattribute based access control; access control; access control test; access control verification; AI; authorization; machine learning; policy. ## Acknowledgments\n\nThe author, Vincent C. Hu of the National Institute of Standards and Technology (NIST), wishes to thank Isabel Van Wyk and Jim Foti (NIST) who reviewed drafts of this document. The author also gratefully acknowledges and appreciates the comments and contributions made by government agencies, private organizations, and individuals in providing direction and assistance in the development of this document."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 9)"}, {"role": "assistant", "content": "| .......................................................................................................................32 |\n| Appendix B.\nDevice-Specific Characteristics of Interest......................................................................35 | |\n| Appendix C. Sample 'Certificate of Sanitization' Form......................................................................36 | |\n| Appendix D. Change Log...................................................................................................................38 | |\n| List of Tables | |\n| Table 1. CE considerations................................................................................................................12 | |\n| List of Figures | |\n| Fig. 1."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 8)"}, {"role": "assistant", "content": "| Audience ......................................................................................................................\n4 |\n| | 2.2 How to use this Guide.................................................................................................. 4 | 2.2 How to use this Guide.................................................................................................. 4 |\n| 3 | Project Overview ................................................................................4 | Project Overview ................................................................................4 |\n| | 3.1 | Background .................................................................................................................. 4 |\n| | 3.2 Solution | ........................................................................................................................"}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.2.1 ADP Audits/Security Reviews - A Form of Control | 3. 3.2.1 ADP Audits/Security Reviews - A Form of Control | 48 |\n\n| ^ | 3. 3.2.1 Participants and Their Tasks | 4."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nValue/Organization | 3.4.5.1.1 Mission Impact/Strategic Value/Organization | 3.4.5.1.1 Mission Impact/Strategic Value/Organization | 55 | | | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | | | | | | | 56 | | | 3.4.5.2.1 | 3.4.5.2.1 | System Size/Scale/Complexity | 56 | | | 3.4.5.2.2 | 3.4.5.2.2 | System Environment/Stability | 57 | | | 3.4.5.2.3 | 3.4.5.2.3 | Reliability/Integrity | 58 | | | 3.4.5.2.4 | 3.4.5.2.4 | Technology Integration | 59 | | 3.5 | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | 59 | | | 3.5.1 Implementation of the Scheme | 3.5.1 Implementation of the Scheme | 3.5.1 Implementation of the Scheme | 59 | | | 3.5.2 | A Simple Scoring Approach | A Simple Scoring Approach | 60 | | | 3.5.3 | A Detailed Scoring Approach | A Detailed Scoring Approach | 60 | | | 3.5.4 | Discretionary Audits | Discretionary Audits | 60 | | 3.6 | USES OF"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.2.\n\n3.2. LESS"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 8)"}, {"role": "assistant", "content": "or services that process, store, or transmit CUI or that provide security protections for those components or services as mandated by a federal agency in a contract, grant, or other agreement.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nForensic software tools strive to handle conventional investigative needs by addressing a wide range of applicable devices. More difficult situations, such as the recovery of deleted data from the memory of a device, may require more specialized tools and expertise and disassembly of the device. The range of support provided, including mobile device cables and drivers, product documentation, PC/SC readers, and the frequency of updates, may vary significantly among products. The features offered such as searching, bookmarking, and reporting capabilities may also vary considerably.\n\nDiscrepancies in recovering and reporting the data residing on a device have been noted in previous testing of tools. They include the inability to recover resident data, inconsistencies between the data displayed on workstation and that generated in output reports, truncated data in reported or displayed output, errors in the decoding and translation of recovered data, and the inability to recover all relevant data. On occasion, updates or new versions of a tool were also found to be less capable in some aspects than a previous version was [Aye11, Jan09].\n\nTools should be validated to ensure their acceptability and reapplied when updates or new versions of the tool become available. These results play a factor in deciding the appropriateness of the tool, how to compensate for any noted shortcomings, and whether to consider using a different version or update of the tool. Validating a tool entails defining and identifying a comprehensive set of test data, following acquisition procedures to recover the test data, and assessing the results [Aye11, Jan09]. Present-day tools seldom provide the means"}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| | Introduction ....................................................................................................1 | | |-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | 1.1 | | Purpose.......................................................................................................................1 | | | 1.2 | | Scope..........................................................................................................................2 | | | 1.3 | | Audience.....................................................................................................................3 | | | 1.4 | Document | Structure....................................................................................................4 | | | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - Illustrative diagram, schematic, or photograph of the module. A photograph included for hardware modules. If the security policy encompasses multiple versions of the module, each version is represented separately or annotated that the representation is illustrated for all versions. For a software or , firmware, hybrid, or sub-chip cryptographic module, the security policy includes a block diagram that illustrates:\n- o The location of the logical object of the software or firmware module with respect to the operating system, other supporting applications, and the cryptographic boundary so that all of the logical and physical layers between the logical object and the cryptographic boundary are clearly defined and\n- o The interactions of the logical object of the software or firmware module with the operating system and other supporting applications resident within the cryptographic boundary."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 10)"}, {"role": "assistant", "content": "| | 2.4.2.1 | 2.4.2.1 | Sponsor/User | 30 | | | 2.4.2.2 Project Manager/Contracting Officer's Technical | 2.4.2.2 Project Manager/Contracting Officer's Technical | 2.4.2.2 Project Manager/Contracting Officer's Technical | | | | | | Representative (COTR) | 30 | | | 2.4.2.3 System Security Specialist (SSS) | 2.4.2.3 System Security Specialist (SSS) | 2.4.2.3 System Security Specialist (SSS) | 31 | | | 2.4.2.4 Internal Control Specialist (ICS) | 2.4.2.4 Internal Control Specialist (ICS) | 2.4.2.4 Internal Control Specialist (ICS) | 31 | | | 2.4.2.5 | 2.4.2.5 | Contracting Officer | 31 | | | 2.4.2.6 | 2.4.2.6 | ADP Manager | 32 | | | 2.4.2.7 | 2.4.2.7 | QuaHty Assurance (QA) Specialist | 32 | | 2.5 | USE OF EXTERNAL DEVELOPMENl^ SERVICES | USE OF EXTERNAL DEVELOPMENl^ SERVICES | USE OF EXTERNAL DEVELOPMENl^ SERVICES | 32 | | | 2.5.1 Contractor Services | 2.5.1 Contractor Services | 2.5.1 Contractor Services | 32 | | | 2.5,1.1 Differences from the AIS Life Cycle Matrix | 2.5,1.1 Differences from the AIS Life Cycle Matrix | 2.5,1.1 Differences from the AIS Life Cycle Matrix | 33 | ( ^ p 9 I | | 2.5.1.2 | 2.5.1.2 |"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.2.4. 3.2.4."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| Practices | Tasks | Notional Implementation Examples | References | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | PO.2.3 : Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development- related roles and responsibilities."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n- Identity Management, Authentication, and Access Control: Identities and credentials for authorized users, services, and hardware are managed by the organization [PR.AA-01]\n- Awareness and Training: Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind [PR.AT-02]"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThis includes requirements from internal sources (e.g., the organization's policies, business objectives, and risk management strategy) and external sources (e.g., applicable laws and regulations). | PO.1.1 : Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. | Example 1 : Define policies for securing software development infrastructures and their components, including development endpoints, throughout the SDLC and maintaining that security. Example 2 : Define policies for securing software development processes throughout the SDLC and maintaining that security, including for open-source and other third-party software components utilized by software being developed. Example 3 : Review and update security requirements at least annually, or sooner if there are new requirements from internal or external sources, or a major security incident targeting software development infrastructure has occurred. Example 4 : Educate affected individuals on impending changes to requirements."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 9)"}, {"role": "assistant", "content": "NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Introductory Tips for Implementers\n\n\n\n## What's New in SP 800 -171, Revision 3? ## SP 800-171, Revision 3 was published in May 2024. Significant changes include:\n\n## Updates to the Security Requirements and Families\n\n- Based on NIST SP 800-53, Revision 5 and the NIST SP 800-53B moderate impact control baseline. - Applies updated tailoring criteria addressing stakeholder feedback (adding new, consolidating, and withdrawing requirements). - Includes increased specificity in security requirements. - Introduces organization-defined parameters (ODP) to increase flexibility to better manage organizationspecific risks. ## Additional Revision 3 Resources\n\n- A CUI overlay (.xlsx) showing the direct link between SP 800-53 and SP 800171, including NIST's tailoring decisions. - Transitioning your organization from implementation of Revision 2 to Revision 3? Review this detailed analysis of the changes between Revision 2 and Revision 3 (.xlsx). - The SP 800-171 security requirements in multiple formats (Excel, JSON, and online) through the NIST Cybersecurity and Privacy Reference Tool. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Key Terms\n\n\n\n\n\nControl Baseline: A set of controls you can implement to meet strategic, legal, regulatory, or contractual security and privacy requirements and manage risk. Organization-Defined Parameters (ODPs) are included in certain security requirements. ODPs provide the flexibility and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nAlmost two-thirds (65%) of survey participants measure RBT effectiveness by using training completion rates, and just under half evaluate success via audit reports or evaluations (Figure 14). Less than half (46%) gauge effectiveness from informal employee feedback (e.g., inperson discussions, emails), and 34% use employee surveys to determine training success. Just under a quarter (24%) examine behaviors (e.g., security incident trends and incident reporting) as evidence that employees are applying what they have learned through RBT. 9% of participants do not attempt to measure the effectiveness of their RBT activities at all.\n\nOver half of survey participants rated their RBT activities as moderately or very successful. However, there is great variation in how organizations determine that success, and determining RBT effectiveness was viewed as challenging by close to 60% of survey participants. Many rely on compliance metrics, such as training completion rates or FISMA evaluations, that do not necessarily reflect impact on employee learning or behaviors, which is the goal of RBT. The lack of meaningful metrics may also place RBT staff at a disadvantage in trying to gain leadership support for training activities.\n\n□ Audit reports or FISMA (Federal Information Security Modernization Act of 2014) evaluations"}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 4)"}, {"role": "assistant", "content": "ards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology.\nITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nTo include bilateral key confirmation, two instances of unilateral key confirmation (as specified in Section 5.6.1, subject to the modifications listed below) shall be incorporated into the KAS2 scheme, once with party U as the key-confirmation provider (i.e., P = U and R = V) and once with party V as the key-confirmation provider (i.e., P = V and R = U). Additional details will be provided in Section 8.3.3.4."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 4)"}, {"role": "assistant", "content": "ares y Tecnología (NIST) promueve la economía y el bienestar público de Estados Unidos a través de su liderazgo técnico en la infraestructura de medición y normalización del país.\nEl ITL desarrolla pruebas, métodos de prueba, datos de referencia, implementaciones de pruebas de concepto y análisis técnicos para avanzar en el desarrollo y el uso productivo de la tecnología de la información. Las responsabilidades del ITL incluyen el desarrollo de normas y directrices de gestión, administrativas, técnicas y físicas para la seguridad rentable y la privacidad de la información no relacionada con la seguridad nacional en los sistemas de información federales. La serie de publicaciones especiales 800 informa sobre las investigaciones, directrices y actividades de divulgación del ITL en materia de seguridad de los sistemas de información, así como sobre sus actividades de colaboración con organizaciones industriales, gubernamentales y académicas. ## Resumen\n\nLa confianza cero (ZT) es el término que designa un conjunto de paradigmas de ciberseguridad en evolución que desplazan las defensas de los perímetros estáticos basados en la red para centrarse en los usuarios, los activos y los recursos. Una arquitectura de confianza cero (ZTA) utiliza principios de confianza cero para planificar la infraestructura y los flujos de trabajo industriales y empresariales. La confianza cero asume que no hay confianza implícita concedida a activos o cuentas de usuario basada únicamente en su ubicación física o de red (es decir, redes de área local frente a Internet) o basada en la propiedad de los activos (propiedad de la empresa o personal). La autenticación y la autorización (tanto del sujeto como del dispositivo) son funciones discretas que se realizan antes de establecer una sesión con un recurso de la empresa."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Blockchain for Access Control Systems provide?"}, {"role": "assistant", "content": "## NIST IR 8403\n\n## Blockchain for Access Control Systems\n\nVincent C. Hu\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8403\n\n\n\n## NIST IR 8403\n\n## Blockchain for Access Control Systems\n\nVincent C. Hu\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8403\n\nMay 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\n## National Institute of Standards and Technology Interagency or Internal Report 8403 28 pages (May 2022)\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8403\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n|\n| [INDEED] | Indeed (2021) 15 Professional Skills (Plus Definition and Tips).\nAvailable at https://www.indeed.com/career-advice/career-development/professional-skills |\n| [OPM] | U.S. Office of Personnel Management (2018) Guidance for Identifying, Addressing and Reporting Cybersecurity Work Roles of Critical Need. (U.S. Office of Personnel Management, Washington, DC). Available at https://chcoc.gov/content/guidance-identifying-addressing-and-reporting- cybersecurity-work-roles-critical-need |\n| [SANS] | SANS (2021). 2021 SANS Security Awareness Report: Managing Human Cyber Risk. Available at https://www.sans.org/security-awareness- training/resources/reports/sareport-2021/ |\n| [STEWART] | Stewart, G, Lacey, D (2012) Death by a Thousand Facts: Criticising the Technocratic Approach to Information Security Awareness. Information Management &Computer Security 20(1):29-38. |\n| [WILSON] | Wilson M, Hash J (2003) Building an Information Technology Security Awareness and Training Program. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-50. https://doi.org/10.6028/NIST.SP.800-50 |\n| [WOELK] | Woelk, B (2015) The Successful Security Awareness Professional: Foundational Skills and Continuing Education Strategies. EDUCAUSE Center for Analysis and Research . Available at https://library.educause.edu/~/media/files/library/2016/8/ erb1608.pdf |"}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n5.3.3 | Accidental VMDeletion via Maintenance Script ........................................................23 | | | 5.3.4 | Backdoor Creation via Email Vector ...........................................................................24 Insider..............................................................25 | | | 5.3.5 | Database Modification via Malicious |"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nguarantees, assessment results, formal certifications) that the ISM vendor should provide for the sanitization capabilities\n\nVarying data protection policies may be established within an organization.\nFor example, an organization can have an engineering department and a sales department, where the sales personnel do not need to access detailed proprietary technical data (e.g., source code, schematics), and the engineers do not need to access the PII of the organization's customers. Both might be within the same confidentiality categorization but are contextually different and have different internal and external rules regarding necessary controls. As such, the data protection level is a complementary consideration to organizational control. When identifying whether sanitization is necessary, both organizational control and the data protection level should be considered."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nFor organizations to have appropriate controls on the information for which they are responsible, they must properly safeguard used media. Potential misuse of information collection can result from improperly disposed hard copy media, the acquisition of improperly sanitized ISM, or laboratory reconstruction of ISM sanitized in a manner that is not commensurate with the confidentiality of information stored on that media. Media flows in and out of organizational control through recycle bins, out to vendors for equipment repairs, and swapped into other systems in response to hardware or software failures. This potential vulnerability can be mitigated by properly understanding where information is located and how to protect it.\n\n- Hard copy. Hard copy media refers to physical representations of information, typically paper printouts, film, microfiche, etc. However, printer and facsimile ribbons, drums, and platens are also examples of hard copy media. The supplies associated with producing paper printouts are often the most uncontrolled. Hard copy materials containing sensitive data that leave an organization without effective sanitization expose a significant vulnerability to 'dumpster divers' and overcurious employees.\n- Information storage media (ISM). ISM commonly 2 takes the form of:\n- o Devices that contain bits and bytes, such as hard disk drives (HDDs), solid state drives (SSDs), random access memory (RAM), read-only memory (ROM), optical disks, magnetic tape, flash memory, memory devices, phones, mobile computing devices, networking devices, and office equipment\n- o Systems that provide 'virtual' or 'logical' storage that abstracts the underlying electronic media (e.g., cloud storage, object storage)"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Getting Started with Awareness and Training\n\n## Family: Awareness and Training"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.12. Requirements for Visual Facial Image Comparison . . . . . . . . . . . .\n\ntranscription, or accessibility support) to assist the applicant in the identity\nproofing process but does not support decision-making or risk-based evaluation.\n\n13. The CSP’s policy for assessing customer experience, including the testing methods\nemployed, timing of its periodic reviews, and any specific conditions that will\ntrigger an out-of-cycle review (see Sec. 3.4)"}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.6.\n\n3.6. Redress\nDesigning services that support a wide range of populations requires processes to\nadjudicate issues and provide redress4\n as warranted. Service failures, disputes, and\nother issues tend to arise as part of normal operations, and their impacts can vary\nbroadly, from minor inconveniences to major disruptions or damage. Furthermore,\nthe same issue experienced by one person or community as an inconvenience can have\ndisproportionately damaging impacts on other individuals and communities.\n\nauthentication intent\nThe process of confirming the claimant’s intent to authenticate or reauthenticate by\nrequiring user intervention in the authentication flow. Some authenticators (e.g., OTPs)\nestablish authentication intent as part of their operation. Others require a specific step\nto establish intent, such as pressing a button. Authentication intent is a countermeasure\nagainst malware at the endpoint as a proxy for authenticating an attacker without the\nsubscriber’s knowledge."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\nThere may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities. The information in this publication, including\nconcepts and methodologies, may be used by federal agencies even before the completion of such\ncompanion publications. Thus, until each publication is completed, current requirements, guidelines, and\nprocedures, where they exist, remain operative. For planning and transition purposes, federal agencies\nmay wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops tests,\ntest methods, reference data, proof of concept implementations, and technical analyses\nto advance the development and productive use of information technology. ITL’s respon-\nsibilities include the development of management, administrative, technical, and physical\nstandards and guidelines for the cost-effective security and privacy of other than national\nsecurity-related information in federal information systems."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 7)"}, {"role": "assistant", "content": "..................................................................... | Summary ........................................................................................................................\n| 28 |\n| References.............................................................................................................................. | References.............................................................................................................................. | 28 |\n| Appendix: Interview Questions ........................................................................................... | Appendix: Interview Questions ........................................................................................... | 30 |\n| List of Tables | List of Tables | List of Tables |\n\n## Introduction\n\nCryptography is an essential component of modern computing."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n1.3.2. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n2.3.2. Authentication Process\n\n3.2."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 10)"}, {"role": "assistant", "content": "Note that it may not be possible to perform all checks at the time of each access request, some policy check may be performed on an independent schedule (e.g., daily software versioning checks). - IV.\nThe enterprise collects as much information as possible about the current state of assets, network infrastructure and communications and uses it to improve its security posture. Zero trust adds a dynamic response factor that was typically lacking (or not possible) in previous perimeter-based architectures. This requires the enterprise to monitor all traffic to the extent feasible and restricted (or required) by policy, regulation or legal requirement. System logs and threat intelligence are used to refine or change policy in response to new information. For example, a new vulnerability in a software component in use in the enterprise is announced. A zero trust enterprise could move quickly to quarantine the affected resources until they can be patched or modified to mitigate the newly discovered vulnerability. Administrators will need to set up and maintain a comprehensive monitoring and patching program for the enterprise and should consider how automated tools could assist in responding to newly discovered threats. ## 2 Getting Started on the Journey\n\nMoving to a zero trust architecture will likely never start from scratch but will involve a series of upgrades and changes over time. Some changes may be simple configuration changes, and some may involve the purchase and deployment of new infrastructure; it all depends on what tools are currently used and available to the enterprise. The process of migrating to a ZTA is not a unique process and is similar to other cybersecurity upgrades or improvements but guided by zero trust principles in the planning and implementation. Existing frameworks such as the NIST Risk Management Framework (RMF) [2] and Cybersecurity Framework (CSF) [3] can help an enterprise discuss, develop, and implement a ZTA."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nSupport for Streamlined SCAP Content Creation, Acquisition, and Reuse: SCAP v2 will develop and incorporate simpler formats for use in content creation, including updates to the Extensible Configuration Checklist Description Format (XCCDF) and the\n\nOpen Vulnerability and Assessment Language (OVAL), and will develop ways to use system artifacts in posture assessments that do not require deep system expertise. Additionally, by using standardized interfaces and protocols to discover and retrieve SCAP content, SCAP v2 products will be able to detect when new SCAP content is available and automatically acquire suitable content updates based on organizational policies. These same interfaces can be used to discover content for reuse. - Posture Evaluator Protocol : To support the separation of collection and evaluation, SCAP v2 will need to define a remote evaluation protocol to enable Posture Evaluators to be plugged into the architecture. This protocol will need to define how to request an evaluation and how a Posture Evaluator can request Endpoint posture to be collected from a Posture Collection Server. - XCCDF Language Improvements: XCCDF currently uses the CPE Applicability language. XCCDF [18] needs to be updated to support the Endpoint Applicability Language and SWID tags. There are also several extensibility enhancements requested by the SCAP community that need to be addressed. These updates are expected to be worked in an international standards organization. - OVAL-Based Collection and Language Improvements: A messaging model is needed to allow for the collection of configuration setting information from an endpoint using OVAL [19]. A NEA extension will be developed to allow for event-driven and ad-hoc OVAL-based collection of configuration setting information."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n3.4.2. 3.4.2. 3.4.2."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\nLaw enforcement and other personnel accessing CJI already manage multiple user identities and may already manage multiple MFA tokens for those identities. To the greatest extent feasible, agencies should consider MFA architectures that minimize the number of separate MFA credentials that need to be issued to users and managed. For instance, if a user has an MFA credential to access a state CJIS portal and another MFA credential to get access to their CAD/RMS system, there may be opportunities to avoid the user having to manage two sets of credentials. Moreover, each MFA implementation requires a management system, a support staff to assist users with obtaining, registering, and using their MFA credentials, and administrative processes that drive costs in both time and money. Agencies should consider integrating CJI applications and/or services with existing IdPs that can or already support MFA. This might include leveraging SSO services, as mentioned in Sec. 2.4.2.\n\nBecause the average agency user may not be familiar with MFA systems, agency personnel responsible for MFA deployment should conduct market research on potentially viable MFA solutions and present them to a representative portion of the user base to facilitate feedback and to enumerate requirements.\n\nImplementing any MFA solution likely requires users to change the way they conduct daily interactions with their IT systems. Because of this, it is important that once an MFA solution is selected, agencies educate users with clear instructions on how to obtain and use any new authenticators, as well as provide easy access to help desk or support personnel who can assist users in setting up and using the new MFA solution. Section 3.3 provides a notional plan for a phased MFA rollout to different user bases."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 5)"}, {"role": "assistant", "content": "nd assessment; system and common control authorizations; and continuous monitoring. The RMF includes activities to prepare organizations to execute the framework at appropriate risk management levels.\nThe RMF also promotes near real-time risk management and ongoing information system and common control authorization through the implementation of continuous monitoring processes; provides senior leaders and executives with the necessary information to make efficient, cost-effective, risk management decisions about the systems supporting their missions and business functions; and incorporates security and privacy into the system development life cycle. Executing the RMF tasks links essential risk management processes at the system level to risk management processes at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems. ## Keywords\n\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n4. Management controls to ensure that security objectives are\nachieved fit into three categories— policies that are formulated\nat the top, procedures for administrative, physical, and technical\nsecurity measures, and practices for the standard management ac-\ntivities .\n5. ADP security controls should include a) administrative safe-\nguards in the form of contingency plans, security documentation,\nauthorization control lists, program access controls, personnel\nrules; b) physical security safeguards such as area restrictions,\ndisaster back-up, storage libraries, disposal procedures; and c)\ntechnical security in the form of a security system to handle data\nand files, program libraries, operating system(s), teleprocessing,\nand encryption.\n6. Training is needed for systems people as well as users.\n\nData Handling and Disposal\n\nIt is also necessary that appropriate disposal techniques"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-09-08\n\n## How to Cite this NIST Technical Series Publication:\n\nChandramouli R, Butcher Z (2023) A Zero-Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Location Environments. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-207A. https://doi.org/10.6028/NIST.SP.800-207A\n\n## Author ORCID iDs\n\nRamaswamy Chandramouli: 0000-0002-7387-5858\n\n## Contact Information\n\nsp800-207A-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nOne of the basic tenets of zero trust is to remove the implicit trust in users, services, and devices based only on their network location, affiliation, and ownership. NIST Special Publication 800207 has laid out a comprehensive set of zero trust principles and referenced zero trust architectures (ZTA) for turning those concepts into reality. A key paradigm shift in ZTAs is the change in focus from security controls based on segmentation and isolation using network parameters (e.g., Internet Protocol (IP) addresses, subnets, perimeter) to identities. From an application security point of view, this requires authentication and authorization policies based on application and service identities in addition to the underlying network parameters and user identities."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. This publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n8 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products).\nSince many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.2.5. 3.2.5. 3.2.5."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n[Not part of SSDF 1.1] | purposes, and mitigate the risks as necessary. [Not part of SSDF 1.1] | | R2: Select and apply appropriate methods for analyzing and altering the training, testing, fine- tuning, and aligning data for an AI model. Examples of methods include anomaly detection, bias detection, data cleaning, data curation, data filtering, data sanitization, fact- checking, and noise reduction. C1: Consider using a human-in-the-loop to examine data, such as with exploratory data analysis techniques [18]. | OWASP: LLM03, LLM06 |\n| being consumed as part of AI model training, testing, fine-tuning, and aligning. [Not part of SSDF 1.1] | PW.3.2: Track the provenance, when known, of all training, testing, fine-tuning, and aligning data used for an AI model, and document which data do not have known provenance. [Not part of SSDF 1.1] | Medium | N1: Provenance verification is not possible in all cases because provenance is not always known."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n| RSA Key Pairs....................................................................................................................... | RSA Key Pairs....................................................................................................................... | RSA Key Pairs....................................................................................................................... | 36 |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|\n| | 6.1 General Requirements....................................................................................................... | 6.1 General Requirements....................................................................................................... | 36 |\n| | 6.2 Criteria for RSA Key Pairs for Key Establishment .......................................................... | 6.2 Criteria for RSA Key Pairs for Key Establishment .........................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n- 3.2.1 Data Entry . For all data received manually, either in source document form for conversion to media or directly in media form, procedures should be developed (in conjunction with submitting departments) to ensure that the data is complete, accurate, authorized, not duplicated, and timely. Where data conversion is required, it should be validated to ensure that the above characteristics are retained. - 3.2.2 Machine Operation . To ensure that the correct data and programs are used, that records are not improperly destroyed, and that the installation can survive system failures, appropriate policies with respect to the human operation of computer and communications equipment should be established regarding:\n- The content and use of machine operator instructions (e.g., run books). - File label checking\n- The use of restart/recovery capabilities\n- The preparation of error logs\n- The use of protective devices (e.g., tape rings)\n- Permissible operator intervention\n- Backup arrangements (and when they should be employed)\n- Rotating and/or dual operators\n- Validation and authorization of remote terminals accessing the system, and\n- Validation procedures to be included in powering up and enabling the computer and communications equipment. - 3.2.3 Library Operation . To prevent the loss, destruction, or disabling of files and/or software, appropriate policies with respect to the maintenance of program, data, and job control libraries, and the use and movement of media should be established. These should include:\n- Identification of media\n- Identification of files and programs (to the version level)\n- Retention back-up and destruction\n- Usage logs\n- Cleaning of media\n- Storage and custody of supplies and media, and\n- Disposal of sensitive media remnants. - 3.2.4 Machine Uti 1 ization ."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n|\n| Appendix A. C-SCRM Security Controls...............................................................................................\n| 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 9)"}, {"role": "assistant", "content": "NTRODUCTION | PART T: INTRODUCTION | 1-] |\n| 1.\nHOST WELCOIING ADDRESS | 1. HOST WELCOIING ADDRESS | 1. HOST WELCOIING ADDRESS | 1-1 1-3 |\n| 2. | THE CHARGE TO ALL THE SESSIONS COMMENTS ON THE SESSIONS AND THE REPORTS | THE CHARGE TO ALL THE SESSIONS COMMENTS ON THE SESSIONS AND THE REPORTS | 1-10 |\n| 3. EDITOR'S | 3. EDITOR'S | 3. EDITOR'S | |\n| | | | 1-10 |\n| 3.1 Definitions of Terms | 3.1 Definitions of Terms | 3.1 Definitions of Terms | T-11 |\n| 3.2 Materials Distributed at the Workshop 3.3 Reading the Report 3.4 References | 3.2 Materials Distributed at the Workshop 3.3 Reading the Report 3.4 References | 3.2 Materials Distributed at the Workshop 3.3 Reading the Report 3.4 References | |\n| PART II: 1."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759:\n\nCryptographic Module Validation Program; CMVP; FIPS 140 testing; FIPS 140; ISO/IEC 19790; ISO/IEC 24759; testing requirement; vendor evidence; vendor documentation; security policy.\n\nThis document is intended for use by vendors, testing labs, and the CMVP."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\ncks. This guide addresses only adverse cybersecurity events . Additional analysis is often needed to determine whether adverse cybersecurity events indicate that a cybersecurity incident has occurred.\n- Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state"}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nAC systems are basically categorized as Discretionary AC (DAC), which leaves a certain amount of AC to the discretion of the object's owner or anyone else who is authorized to control the object's access. In general, all AC policies other than DAC are grouped under the category of nondiscretionary AC (NDAC). As the name implies, policies in this category have rules that are not established at the discretion of the user. NDAC establishes controls that can only be changed through administrative action, not by subjects. For example, a capability list is a popular model of DAC, and Identity based AC (IBAC) [IR7316], RBAC, ABAC, and CBAC models are popular examples of NDAC. In general, permissionless blockchains are suitable for DAC implementations, and permissioned blockchains are preferred for NDAC implementations for their control mechanisms. | References | |\n|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [BXANL] | Bouras MA, Xia B, Abuassba AO, Ning H, Lu Q (2021) IoT-CCAC: A Blockchain-Based Consortium Capability Access Control Approach for IoT. PeerJ Computer Science 7:e455."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST.\n\n3.15. Exception and Error Handling . . . . . . . . . . . . . . . . . . . . . . .\n\n3.15.1. Requirements for Trusted Referees . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 10)"}, {"role": "assistant", "content": "| ..................................................................................................................\n4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS........................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines provide? (Part 10)"}, {"role": "assistant", "content": "exist along a continuum. Consequently, a digital\nidentity risk management approach should seek to manage risks using outcome-based\napproaches that are designed to meet the organization’s unique needs.\nThese guidelines\ndefine specific assurance levels that operate as baseline control sets. These assurance\nlevels provide multiple benefits, including a starting point for organizations in their\nrisk management journey and a common structure for supporting interoperability\nbetween different entities. It is, however, impractical to create assurance levels that\ncan comprehensively address the entire spectrum of risks, threats, or considerations\nthat an organization will face when deploying an identity solution. For this reason, these\nguidelines promote a risk-based approach to digital identity solution implementation\nrather than a compliance-oriented approach, and organizations are encouraged to tailor\ntheir control implementations based on the processes defined in these guidelines. Additionally, risks associated with digital identity stretch beyond the potential impacts\nto the organization providing online services. These guidelines endeavor to robustly\nand explicitly account for risks to individuals, communities, and other organizations. Organizations should also consider how digital identity decisions might affect, or need\nto accommodate, the individuals who interact with the organization’s programs and\nservices. Privacy and customer experience for individuals should be considered along\nwith security. Additionally, organizations should consider their digital identity approach\nalongside other mechanisms for identity management, such as those used in call centers\nand in-person interactions."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n3.2.1 | Organization Type ... 3.2.1 Organization Type\n\n## Focus Groups\n\nTwenty-eight unique organizations were represented in the focus groups."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 4)"}, {"role": "assistant", "content": "es and appreciates the comments and contributions made by government agencies, private organizations, and individuals in providing direction and assistance in the development of this document.\n## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents, and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Executive Summary\n\nAccess control policy verification ensures that there are no faults within the policy that leak or block access privileges. As a software test, access control policy verification relies on methods such as model proof, data structure, system simulation, and test oracle to verify that the policy logic functions as expected. However, these methods have capability and performance issues related to inaccuracy and complexity limited by applied technologies. For instance, model proof, test oracle, and data structure methods initially assume that the policy under verification is faultless unless the policy model cannot hold for test cases. Thus, the challenge of the method is to compose test cases that can comprehensively discover all faults. Alternatively, a system simulation method requires translating the policy to a simulated system."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 8)"}, {"role": "assistant", "content": "as endpoint and environmental factors impact authentication and authorization policies. ## 1.1.2 Tenets that Deal with Endpoints\n\n- I. All data sources and computing services are considered resources.\nAn enterprise relies on different resources to perform its mission: mobile devices, data stores, compute resources (including virtual), remote sensors/actuators, etc. All these components are resources and need to be considered in a ZTA. Some components (e.g., IoT sensors) may not be able to support some solutions such as configuration agents, application sandboxing, etc. so compensating technologies or alternative mitigations may be needed. If the resource lacks certain security capabilities, the enterprise may need to add a PEP component to provide that functionality. - II. The enterprise monitors and measures the integrity and security posture of all owned and associated resources. This tenet deals with the aspects of cyber hygiene for both enterprise-owned resources and those that may not be owned, but used in an enterprise workflow such as configuration, patching, application loading, etc. The state of resources should be monitored, and appropriate action taken when new information such as a new vulnerability or attack is reported or observed. The confidentiality and integrity of data on the resource should be protected. This requires enterprise admins to know how resources are configured, maintained, and monitored. ## 1.1.3 Tenets that Apply to Data Flows\n\n- I. All communication is secured regardless of network location. In zero trust, the network is always considered contested. A ZTA should be designed with the assumption that an attacker is present on the network and could observe/modify communications. Appropriate safeguards should be in place to protect the confidentiality and integrity of data in transit. If a resource cannot provide this functionality natively, a separate PEP component may be necessary. - II."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Data Structure for Integrity Protection with Erasure Capability provide? (Part 4)"}, {"role": "assistant", "content": "Algorithm 1 Data block matrix construction\n\nFigure 2. Block matrix with numbered cells\n\n\n\n## III. PROPERTIES\n\nCertain desirable properties are maintained with this data structure.\nThese features allow for the efficient storage and retrieval of data blocks (results originally introduced in [1]). Theorem 1 (Balance property) . Cells are filled in a balanced manner so that the upper half (above diagonal) contains at most one additional cell more than the lower half. Proof. The following invariant implies the property, and for each iteration of the loop, the invariant is maintained, ( i = j ∨ i < j ) ∧ u = l ∨ i > j ∧ u = l +1\n\nwhere u = number of cells above diagonal, and l = number of cells below diagonal. Initially, i = j = 0 and u = l = 0 . If i = j , then u, l are unchanged, so the invariant remains true. If i < j , then u = l . A ′ block is then added to the upper half and u = l + 1\n\nand i ′ = j, j ′ = i so that i ′ > j ′ and the invariant is maintained. If i > j , then u = l +1 and a block is added ′ to the lower half such that u = l ′ and i ′ = j +1 , j ′ = i , so that i ′ < j ′ , maintaining the invariant. Theorem 2 (Hash chain length) . The number of blocks in a row or column hash chain is proportional to N for a matrix with N blocks. Proof. The balance property ensures filling in a square form. Theorem 3 (Block numbering) . All even-numbered blocks are placed below the diagonal and all oddnumbered blocks are placed above the diagonal. Proof. The following invariant implies the property. i < j ∧ odd ( B i,j ) ∨ i > j ∧ even ( B i,j )\n\nInitially, i < j and B = 1 , so the invariant holds, and for each iteration of the loop, the invariant is maintained. ̸\n\nTheorem 4 (Block dispersal) . No consecutive blocks appear in the same row or column."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nating systems and hardware configurations prevailed. JTAG - Many manufacturers support the JTAG standard, which defines a common test interface for processor, memory, and other semiconductor chips.\nForensic examiners can communicate with a JTAG-compliant component by utilizing special purpose standalone programmer devices to probe defined test points [Wil05]. The JTAG testing unit can be used to request memory addresses from the JTAGcompliant component and accept the response for storage and rendition [Bre06]. JTAG gives specialists another avenue for imaging devices that are locked or devices that may have minor damage and cannot be properly interfaced otherwise. This method involves attaching a cable (or wiring harness) from a workstation to the mobile device's JTAG interface and access memory via the device's microprocessor to produce an image [Bre07]. JTAG extractions differ mainly from Hex Dumping in that it is invasive as access to the connections frequently require that the examiner dismantle some (or most) of a mobile device to obtain access to establish the wiring connections."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 9)"}, {"role": "assistant", "content": "ework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53].\nThe security control mappings can be useful to organizations that wish to demonstrate compliance to the security requirements in the context of their established information security programs when such programs have been built using the NIST security controls. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "ability provided by the\ncontrols). Addressing functionality and assurance helps to ensure that information technology\nproducts and the systems that rely on those products are sufficiently trustworthy.\nKeywords\n\nAssurance; availability; computer security; confidentiality; control; cybersecurity; FISMA;\ninformation security; information system; integrity; personally identifiable information; Privacy\nAct; privacy controls; privacy functions; privacy requirements; Risk Management Framework;\nsecurity controls; security functions; security requirements; system; system security. ii\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\nI\n\n. NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nAcknowledgements\n\nThis publication was developed by the Joint Task Force Interagency Working Group. The group\nincludes representatives from the civil, defense, and intelligence communities. The National\nInstitute of Standards and Technology wishes to acknowledge and thank the senior leaders from\nthe Department of Commerce, Department of Defense, the Office of the Director of National\nIntelligence, the Committee on National Security Systems, and the members of the interagency\nworking group whose dedicated efforts contributed significantly to this publication. Department of Defense\n\nDana Deasy\nChief Information Officer\n\nOffice of the Director of National\nIntelligence\nMatthew A. Kozma\nChief Information Officer\n\nJohn Sherman\nPrincipal Deputy CIO\n\nMichael E. Waschull\nDeputy Chief Information Officer\n\nMark Hakun\nDeputy CIO for Cybersecurity and DoD SISO\n\nClifford M."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nThis document presents analyses of blockchain AC systems from the perspectives of properties, components, architectures, and model supports, as well as discussions on considerations for implementation. It should not be deemed comprehensive due to the diverse applications of business and mission requirements. Before selecting and deploying a blockchain AC product or technology, the host organization should augment considerations in this document with testing and independent product reviews. 1. Policy Administration Point (PAP): Provides a user interface for creating, testing, and debugging policies, as well as storing these policies in the appropriate repository. PAP can be created and maintained by AC nodes or smart contracts that are coded to access AC policies, depending on where the source of the AC data is maintained. 2. Policy Information Point (PIP): Serves as the source of subject/object attributes or environment condition data required for policy evaluation to provide the information needed by the PDP to make the authorization decisions. PIP can be performed in AC nodes,\n\nBlockchain AC system management needs to coordinate with the business and resource requirements of the system. For instance, a federated AC system may spread over multiple organizations for cooperation and communication between participating organizations. Hence, AC policies needs to be flexible and fine-grained. A blockchain AC system can transform the policy evaluation process to executable smart contracts so that each organization can control its own system while communicating with other federated organizations. Optionally, some federation schemes may use the blockchain as a database for storing only the policies but not use the blockchain for access enforcement, such that PDP and PEP functions are performed off-the-chain."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.5.1 Scenario\n\nThe following scenario was simulated to test the architecture's defense against unwanted database modification."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 10)"}, {"role": "assistant", "content": "| Publication Structure.......................................................................................\n| 2 |\n| 2 | Risk Response Approaches for Software Vulnerabilities ..................................3 | Risk Response Approaches for Software Vulnerabilities ..................................3 | |\n| | 2.1 | Risk Responses.............................................................................................. | 3 |\n| | 2.2 | Software Vulnerability Management Life Cycle..............................................."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.4.2. 3.4.2 and\nSec. 3.4.2 and\nSec."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Security Incident Procedures | 164.308(a)(6) | Response and Reporting (R) | | Contingency Plan | 164.308(a)(7) | Data Backup Plan (R) | | Contingency Plan | 164.308(a)(7) | Disaster Recovery Plan (R) | | Contingency Plan | 164.308(a)(7) | Emergency Mode Operation Plan (R) | | Contingency Plan | 164.308(a)(7) | Testing and Revision Procedure (A) | | Contingency Plan | 164.308(a)(7) | Applications and Data Criticality Analysis (A) | | Evaluation | 164.308(a)(8) | (R) | | Business Associate Contracts and Other Arrangements | 164.308(b)(1) | Written Contract or Other Arrangement (R) | | Physical Safeguards | Physical Safeguards | Physical Safeguards | | Facility Access Controls | 164.310(a)(1) | Contingency Operations (A) | | Facility Access Controls | 164.310(a)(1) | Facility Security Plan (A) | | Facility Access Controls | 164.310(a)(1) | Access Control and Validation Procedures (A) | | Facility Access Controls | 164.310(a)(1) | Maintenance Records (A) | | Workstation Use | 164.310(b) | (R) | | Workstation Security | 164.310(c) | (R) | | Device and Media Controls | 164.310(d)(1) | Disposal (R) | | Device and Media Controls | 164.310(d)(1) | Media Re-use (R) | | Device and Media Controls | 164.310(d)(1) |"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-56B\n\n## Revision 2\n\n## Recommendation for Pair-Wise Key Establishment Using Integer Factorization Cryptography\n\nElaine Barker Lily Chen Allen Roginsky Apostol Vassilev Richard Davis Scott Simon\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-56Br2\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-56B Revision 2\n\n## Recommendation for Pair-Wise Key Establishment Using Integer Factorization Cryptography\n\nElaine Barker Lily Chen Allen Roginsky Apostol Vassilev Computer Security Division Information Technology Laboratory\n\nRichard Davis Scott Simon National Security Agency\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-56Br2\n\nMarch 2019\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 2)"}, {"role": "assistant", "content": "lar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172A Natl. Inst. Stand. Technol. Spec. Publ. 800-172A, 62 pages (March 2022)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.8.\n\n3.8. SDitH"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe enhanced security requirements are organized into 14 families consistent with the families for basic and derived requirements. Each family contains the requirements related to the general security topic of the family. The families are closely aligned with the minimum security requirements for federal information and information systems in [FIPS 200]. The security requirements for contingency planning , system and services acquisition , and planning are not included within the scope of this publication due to the tailoring criteria in [SP 800-171]. Table 1 lists the security requirement families addressed in this publication. 17\n\n- 3.11.4e Document or reference in the system security plan the security solution selected, the rationale for the security solution, and the risk determination."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - Hard copy. Hard copy media refers to physical representations of information, typically paper printouts, film, microfiche, etc. However, printer and facsimile ribbons, drums, and platens are also examples of hard copy media. The supplies associated with producing paper printouts are often the most uncontrolled. Hard copy materials containing sensitive data that leave an organization without effective sanitization expose a significant vulnerability to 'dumpster divers' and overcurious employees. - Information storage media (ISM)."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nmay wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2022-09-08\n\n## How to Cite this NIST Technical Series Publication:\n\nFagan M, Megas KN, Watrobski P, Marron J, Cuthill B (2022) Profile of the IoT Core Baseline for Consumer IoT Products. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8425. https://doi.org/10.6028/NIST.IR.8425\n\n## Author ORCID iDs\n\nMichael Fagan: 0000-0002-1861-2609\n\nKaterina N. Megas: 0000-0002-2815-5448\n\nPaul Watrobski: 0000-0002-6449-3030\n\nJeffrey Marron: 0000-0002-7871-683X\n\nBarbara B. Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecuirty@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nIn this approach, device vendors create an artifact within each device that securely binds the device's attributes to the device's identity. The customer who acquires the device can validate the artifact's source and authenticity, then check the attributes stored in the artifact against the device's actual attributes to ensure they match. A similar process can be used to periodically verify the integrity of computing devices while they are in use. | Technology Partner/Collaborator | Build Involvement |\n|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Eclypsium | Eclypsium Analytics Service, Eclypsium Device Scanner |\n| HP Inc. | (2) Elitebook 840 G7, HP Sure Start, HP Sure Recover, Sure Admin, HP Client Management Script Library (CMSL), HP Tamperlock |\n| Hewlett Packard Enterprise | Proliant DL360 Gen 10, Platform Certificate Verification Tool (PCVT) |\n| IBM | QRadar SIEM |\n| Intel | HP Inc."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nIn working with the Office of Management and Budget to develop standards and guidelines\nrequired by FISMA, NIST consults with federal agencies, state, local, and tribal governments, and\nprivate sector organizations to improve information security and privacy, avoid unnecessary and\ncostly duplication of effort, and help ensure that its publications are complementary with the\nstandards and guidelines used for the protection of national security systems. In addition to a\ncomprehensive and transparent public review and comment process, NIST is engaged in a\ncollaborative partnership with the Office of Management and Budget, Office of the Director of\nNational Intelligence, Department of Defense, Committee on National Security Systems, Federal\nCIO Council, and Federal Privacy Council to establish a Risk Management Framework (RMF) for\ninformation security and privacy for the Federal Government. This common foundation provides\nthe Federal Government and their contractors with cost-effective, flexible, and consistent ways\nto manage security and privacy risks to organizational operations and assets, individuals, other\norganizations, and the Nation. The framework provides a basis for the reciprocal acceptance of\nsecurity and privacy control assessment evidence and authorization decisions and facilitates\ninformation sharing and collaboration. NIST continues to work with public and private sector\nentities to establish mappings and relationships between the standards and guidelines\ndeveloped by NIST and those developed by other organizations. NIST anticipates using these\nmappings and the gaps they identify to improve the control catalog. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ..................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Medium | N1: An artifact is 'a piece of evidence' [16]. Evidence is 'grounds for belief or disbelief; data on which to base proof or to establish truth or falsehood' [17]. Artifacts provide records of secure software development practices. Examples of artifacts specific to AI model development include attestations of the integrity and provenance of training datasets. | AI RMF: Measure 2.1 |\n| Define and Use Criteria for Software Security Checks (PO.4): Help ensure that the software resulting from the SDLC meets the organization's expectations by defining and using criteria for checking the software's security during development. | PO.4.1: Define criteria for software security checks and track throughout the SDLC. | Medium | R1: Implement guardrails and other controls throughout the AI development life cycle, extending beyond the traditional SDLC. C1: Consider requiring review and approval from a human-in-the-loop for software security checks beyond risk-based thresholds. | AI RMF: Measure 2.3, 2.7; Manage 1.1 OWASP: LLM01-2 |\n| Define and Use Criteria for Software Security Checks (PO.4): Help ensure that the software resulting from the SDLC meets the organization's expectations by defining and using criteria for checking the software's security during development. | PO.4.2: Implement processes, mechanisms, etc. to gather and safeguard the necessary information in support of the criteria."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nd their connected resource consumers are the primary concerns of an RM. 3. Resource consumers (RCs) are client applications that accept user requests for resources and forward those requests to an RM.\nIdeally, an RP should only have to communicate with one RM because the dissemination of shared resources is achieved by the RM. Only one connection between an RM and an RC is expected as well because the discovery of resource locations should be done by an RM, as illustrated in Fig. 11."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.1.4 | Vulnerability of Services | 6-9 |\n| 3. 3.1.4 Vulnerability of Services : The working group concluded that one of the vulnerabilities to the system that results from remote processing is the conversion of service or capacity from the use of the owners to the use of another person."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.5.2\n\nDetermine if Computer Assisted Techniques Will Be Used\n\nUse of the computer will depend on:\n-The nature of the control."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.70 (NIST 3.1.70)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.1.70 appears to be infected but not have any idea where that machine resides or who uses it."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.1.70", "cmmc_practice_id": "AC.L2-3.1.70", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ordered t-way Combinations for Testing State-based Systems provide? (Part 8)"}, {"role": "assistant", "content": "m modeled with a finite state machine diagram in Fig. 5, and tests are run in the order 1..6. If condition A = 'p1 ∧ p2' and condition B = 'p1 ∧ ~p2', then the error in state 2 will not be discovered.\nThe system returns to state 0 for tests 1 through 3, then enters state 1 with test 4 and moves to state 3 with test 5. Because the test array does not include the ordered combinations p1, p2 = 11 *→ p1, p2 = 10, the error is not exposed. However, if the tests are run in the order [1, 2, 4, 3, 5, 6], then the error in state 2 will be discovered because the third test (row 4 in Fig. 4) leads to state 1, the fourth test (row 3) causes condition B to evaluate to true, and the system enters state 2, exposing the error. Fig. 5. Example Finite State Machine. \n\nNote that the definition includes the repetition of a value combination in the OCC. The possibility of repeated occurrences of a value combination in an order is allowed based on the assumption that a particular combination may occur in multiple tests, and this sequence may be relevant to the system or software under test (SUT). For example, a function call to create a new file ' f1 ' followed by a duplicate call to create ' f1 ' may trigger some behavior other than an expected error message. So the 3-way combination (create, f1, 256 ) may be desirable to include more than once in a series of test inputs. Returning to the example in Fig. 4 and Fig. 5, suppose that a file system is being tested, where p 1 is function with values {0 = read, 1 = write}, and p 2 is rewind , which indicates if the pointer to the starting block is reset to 0 {0 = start from last position, 1 = start from block 0}. A read or write test processes from the starting block indicated by p 2 and continues to the end of the file."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- Based on NIST SP 800-53, Revision 5 and the NIST SP 800-53B moderate impact control baseline.\n- Applies updated tailoring criteria addressing stakeholder feedback (adding new, consolidating, and withdrawing requirements).\n- Includes increased specificity in security requirements.\n- Introduces organization-defined parameters (ODP) to increase flexibility to better manage organizationspecific risks.\n\nControl Baseline: A set of controls you can implement to meet strategic, legal, regulatory, or contractual security and privacy requirements and manage risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.4.3. 3.4.3. 3.4.3)."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 6)"}, {"role": "assistant", "content": "Introduction\n\nCyber-Physical Systems (CPS) are hybrid networked cyber and engineered physical elements codesigned to create adaptive and predictive systems for enhanced performance. 1, 2 These smart systems present a key opportunity to create a competitive advantage for U.S. industrial innovation and to improve the performance and reliability of new and existing systems. From smart manufacturing and the electric smart grid, to smart structures and transportation systems, CPS will pervasively impact the economy and society. Cybersecurity is a critical cross-cutting discipline that provides confidence that cyber-physical systems, their information, and supporting communications and information infrastructures are adequately safeguarded. CPS are increasingly being utilized in critical infrastructures and other settings. However, CPS have many unique characteristics, including the need for real-time response and extremely high availability, predictability, and reliability, which impacts cybersecurity decisions. NIST is currently working in several CPS areas, including the electric smart grid, smart manufacturing, smart buildings, and networked automobiles. This work is being led by the Engineering Laboratory (EL), but also includes the Physical Measurement Laboratory (PML) and the Information Technology Laboratory (ITL). ITL has a number of key areas of expertise that are important to the evolution of CPS -interoperability, usability, reliability, and security. Since 2009, NIST has been very active in the area of the smart grid. ITL has been very active, providing leadership and expertise in a number of relevant areas, including communication networks, timing, and cybersecurity. ITL's Computer Security Division (CSD) has provided leadership and expertise to the Smart Grid Interoperability Panel's Cyber Security Working Group."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide for Developing Security Plans for Federal Information Systems provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-18 Revision 1\n\n\n\n## Guide for Developing Security Plans for Federal Information Systems\n\nMarianne Swanson Joan Hash Pauline Bowen\n\n## I N F O R M A T I O N S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nFebruary 2006\n\n\n\nU.S. Department of Commerce Carlos M.Gutierrez, Secretary\n\nNational Institute of Standards and Technology William Jeffrey, Director\n\n## Reports on Information Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology promotes the United States economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof-of-concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of non-national-security-related information in federal information systems. This Special Publication 800 series reports on ITL's research, guidelines, and outreach efforts in information system security and its collaborative activities with industry, government, and academic organizations. ii\n\n## Authority\n\nThis document has been developed by the National Institute of Standards and Technology (NIST) in furtherance of its statutory responsibilities under the Federal Information Security Management Act of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 4)"}, {"role": "assistant", "content": "| 2.1 The Process....................................................................................................\n5 |\n| 3 | Conclusion ...........................................................................................................12 |\n| References...................................................................................................................13 | References...................................................................................................................13 |\n\n## 1 Zero Trust\n\nZero trust provides a collection of concepts designed to minimize uncertainty in enforcing accurate, least privilege per-request access decisions in information systems and services in the face of a network viewed as contested. That is, there may be a malicious actor on the network that can intercept or initiate communication. Zero trust is fundamentally comprised of a set of principles upon which information technology architectures are planned, deployed, and operated [1]. Zero trust uses a holistic view that considers potential risks to a given mission or business process and how they are mitigated. As such, there is no single specific zero trust infrastructure implementation or architecture. zero trust solutions depend on the workflow (i.e., part of the enterprise mission) being analyzed and the resources that are used in performing that workflow. zero trust strategic thinking can be used to plan and implement an enterprise IT infrastructure, this plan is called a zero trust architecture (ZTA). Enterprise administrators and system operators need to be involved in the planning and deployment for a ZTA to be successful."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\narchitecture; configuration; endpoint; endpoint security; SCAP; security automation; security content automation; Security Content Automation Protocol; software identification; SWID; vulnerability\n\n| 1 | Introduction ............................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| 2 Gaps in SCAP | v1....................................................................................................2 |\n| 3 SCAP | v2..................................................................................................................3 |\n| 3.1 Design Goals for SCAP v2.............................................................................. | 3 |\n| 3.2 The SCAP v2 | Architecture.............................................................................. 4 |\n| 3.3 Adoption of International Standards | in SCAP v2 ............................................"}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\ney can hide software. By decoupling operating system dependencies from the host system, a container image may contain unknown vulnerable or insecure software, which poses a software supply chain risk.\nAdditionally, container contents may not be observable by some security auditing tools. In a well-managed HPC system, most software has already been installed as a baseline system environment. The applications developed using native libraries often run faster than a container. Hence, training users to develop programs in the HPC programming environment is one way to reduce exposure to container vulnerabilities. Additionally, many container ecosystems include the ability to attest that a container and its dependencies are supplied by a trusted provider, and there are tools (e.g., Qualys [49], Anchore [50], etc.) designed to audit container contents that provide supply chain and software audit management for HPC applications. Containers, container runtimes, and container orchestrators all increase the security attack surface for HPC systems, but carefully implemented container environments may potentially improve the overall security posture. Vulnerable or poorly configured container runtimes or container orchestrators can lead to exploitable environments and, in some cases, even privilege"}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\n| Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1. | Introduction ...................................................................................................................... | 2 |\n| 2. | Fundamental Theories ..................................................................................................... | 4 |\n| 2.1. | Elliptic Curve | .............................................................................................................. 4 |\n| 2.2. | Elliptic-Curve Cryptography ........................................................................................ | 5 |\n| 2.3."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Device Identification : The IoT device can be uniquely identified logically and physically."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\ncks. This guide addresses only adverse cybersecurity events . Additional analysis is often needed to determine whether adverse cybersecurity events indicate that a cybersecurity incident has occurred.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes R2: Tune the continuous monitoring |\n|---------------|------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| DE.CM-01 | Networks and network services are monitored to find potentially adverse events | High | false negatives to acceptable levels."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n15. https://doi.org/10.6028/NIST.SP.800-78-4. |\n| [SP800-87] | NIST Special Publication 800-87 Revision 2, Codes for the Identification of Federal and Federally-Assisted Organizations , April 2018.\nhttps://doi.org/10.6028/NIST.SP.800-87r2 . |\n| [TIG SCEPACS] | Technical Implementation Guidance: Smart Card Enabled Physical Access Control Systems, Version 2.3 , The Government Smart Card Interagency Advisory Board's Physical Security Interagency Interoperability Working Group, December 20, 2005. http://www.idmanagement.gov/tig_scepacs_v2-3/ [accessed 5/16/18] |"}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nWithin the United States, the Food and Drug Administration (FDA) regulates the manufacturers, importers and resellers of these devices through the Center for Devices and Radiological Health (CDRH). A review of a sampling of FDA testing guidance (e.g. for implantable cardiac pacemakers) reveals that the 'tests are designed to reasonably assure safe and effective functioning of the pacemaker in the patient, according to written specifications of performance, and its survival under expected environmental conditions in the body and during storage, shipping and handling' [1]. FDA testing guidelines do not appear to address the resistance and resilience of these devices in the face of cyber attacks. - [1] 'Implantable Pacemaker Testing Guidance,' found at http://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandG uidance/GuidanceDocuments/UCM081382.pdf. - [2] D. Halperin, et al, 'Pacemakers and Implantable Cardiac Defibrillators: Software Radio Attacks and Zero-Power Defenses,' Proceedings of the 2008 IEEE Symposium on Security and Privacy, Oakland, CA, 2008. - [3] D. Halperin et al, 'Security and Privacy for Implantable Medical Devices,' in Pervasive Computing, Vol. 7, No. 1, January-March 2008. - [4] S. Capkun, 'On Secure Access to Medical Implants,' Workshop on Security and Privacy in Implantable Medical Devices, Lausanne, Switzerland, April, 2011. - [5] S. Cherukuri, K. Venkatasubramanian, and S. Gupta, 'BioSec: A Biometric Based Approach for Securing Communication in Wireless Networks of Biosensors Implanted in the Human Body,' Proc. Int'l Conf. Parallel Processing (ICPP)Workshops, IEEE CS Press, 2003, pp. 432-439. - [6] T. Denning, et al 'Patients, pacemakers, and implantable defibrillators: human values and security for wireless implantable medical devices,' Proceedings of the 28th international conference on Human factors in computing systems, ACM New York, NY, USA, 2010, pp 917-926."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 9)"}, {"role": "assistant", "content": "oosing them? This NIST Internal Report (NISTIR) is a companion to the research paper 'We make it a big deal in the company': Security Mindsets in Organizations that Develop Cryptographic Products [6].\nThe paper explored one theme identified in the study (security mindsets) while describing findings related to the use, benefits, and challenges of cryptographic resources. Although descriptions of methodology and demographics are pulled from the research paper, this NISTIR is not meant to duplicate the findings and analysis previously presented. Instead, this report is more narrowly focused on enumerating (not interpreting) comments made specifically about NIST cryptographic products and testing/validation resources and programs, most frequently those associated with the Federal Information Processing Standards Publication (FIPS) 140-2 [7]. The target audience consists of those working on NIST cryptographic standards and testing/validation programs, but the results may also be useful to others outside of NIST that are developing related standards and programs. The purpose of this NISTIR is to inform the audience of the feedback and perceptions of NIST cryptographic standards and testing/validation programs from companies that develop cryptographic products. The feedback offers a lens into the organizational needs of consumers of NIST cryptographic standards and testing and validation programs and may help to inform future decisions concerning documentation and cryptographic efforts. ## Background: NIST Cryptographic Standards and Testing/Validation Programs\n\nCryptographic algorithm standards are developed by consensus of community stakeholders (e.g. vendors, researchers, governments) to foster compatibility, interoperability, and\n\nminimum levels of security. These standards can be found in formal documents from organizations such as the Internet Engineering Task Force (IETF) [8], International Organization for Standardization (ISO) [9], and NIST [10]."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n7 |\n| | | 3.2.2 Scenario 2: | Verification of Components During Acceptance Testing........................... 7 |\n| | | 3.2.3 | Scenario 3: Verification of Components During Use...................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n## Guide to Enterprise Patch Management Planning:\n\n## Guide to Enterprise Patch Management Planning:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "three security control baselines (one for each system impact level-low-impact, moderate-impact, and high-impact), as well as a privacy baseline that is applied to systems irrespective of impact level.\nIn addition to the control baselines, this publication provides tailoring guidance and a set of working assumptions that help guide and inform the control selection process. Finally, this publication provides guidance on the development of overlays to facilitate control baseline customization for specific communities of interest, technologies, and environments of operation. ## Keywords\n\nAssurance; impact level; privacy control; privacy control baseline; security control; security control baseline; tailoring; control selection; control overlays. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThis publication was developed by the Joint Task Force Interagency Working Group. The group includes representatives from the civil, defense, and intelligence communities. The National Institute of Standards and Technology wishes to acknowledge and thank the senior leaders from the Department of Commerce, Department of Defense, the Office of the Director of National Intelligence, the Committee on National Security Systems, and the members of the interagency working group whose dedicated efforts contributed significantly to this publication. ## Department of Defense\n\n## Office of the Director of National Intelligence\n\nMatthew A. Kozma Chief Information Officer\n\nDana Deasy\n\nChief Information Officer\n\nJohn Sherman\n\nMichael E. Waschull Deputy Chief Information Officer\n\nPrincipal Deputy CIO\n\nMark Hakun\n\nClifford M."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nging the risks to individuals associated with the creation, collection, use, processing, dissemination, storage, maintenance, disclosure, or disposal (collectively referred to as 'processing') of PII.\n30 When preparing to execute the steps of the RMF, organizations consider how to best promote and institutionalize collaboration between the two programs to ensure that the objectives of both disciplines are met at every step of the process."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n..................................................................... | 5.4 Specific Details ...........................................................................................................\n| 29 |\n|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|\n| 6 | Functional Demonstrations...............................................................30 | Functional Demonstrations...............................................................30 | Functional Demonstrations...............................................................30 | |\n| | 6.1 | Usage Scenarios Supported ....................................................................................... | Usage Scenarios Supported ......................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.5.2 Resolution\n\nThe build provides several layers of defense against this use case."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 2)"}, {"role": "assistant", "content": ", Virginia\n\nMatthew Zopf Strativia Largo, Maryland\n\nFINAL\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nJames K.\nOlthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## NIST SPECIAL PUBLICATION 1800-10A\n\n## Protecting Information and System Integrity in Industrial Control System Environments:\n\n## Cybersecurity for the Manufacturing Sector\n\n## Volume A:\n\nExecutive Summary\n\n## Michael Powell\n\nNational Cybersecurity Center of Excellence National Institute of Standards and Technology\n\n## Michael Pease Keith Stouffer CheeYee Tang Timothy Zimmerman\n\nEngineering Laboratory National Institute of Standards and Technology\n\n## Matthew Zopf\n\nStrativia Largo, Maryland\n\nFINAL\n\nMarch 2022\n\nThis publication is available free of charge from https://doi.org/10.6028/NIST.SP.1800-10\n\nThe first draft of this publication is available free of charge from https://www.nccoe.nist.gov/publications/practice-guide/protecting-information-and-system-integrity- industrial-control-system-draft\n\n\n\nJoseph Brule Chelsea Deane John Hoyt Mary Raguso Aslam Sherule Kangmin Zheng\n\nThe MITRE Corporation McLean, Virginia\n\n## Executive Summary\n\nMany manufacturing organizations rely on industrial control systems (ICS) to monitor and control their machinery, production lines, and other physical processes that produce goods. To stay competitive, manufacturing organizations are increasingly connecting their operational technology (OT) systems to their information technology (IT) systems to enable and expand enterprise-wide connectivity and remote access for enhanced business processes and capabilities."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 8)"}, {"role": "assistant", "content": "---------------------------------------------------------------------|\n| 1 INTRODUCTION.................................................................................................................\n1 | 1 INTRODUCTION................................................................................................................. 1 | 1 INTRODUCTION................................................................................................................. 1 |\n| 2 REPORTING CONVENTIONS.......................................................................................... 2 | 2 REPORTING CONVENTIONS.......................................................................................... 2 | 2 REPORTING CONVENTIONS.......................................................................................... 2 |\n| 3 PROFESSIONAL DEMOGRAPHICS............................................................................... 3 | 3 PROFESSIONAL DEMOGRAPHICS..............................................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 4)"}, {"role": "assistant", "content": "-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 11.\nConclusion .................................................................................................................................26 | 11. Conclusion .................................................................................................................................26 |\n| References.......................................................................................................................................27 | References.......................................................................................................................................27 |\n| Appendix A. EPSS Documentation ....................................................................................................28 | Appendix A. EPSS Documentation ....................................................................................................28 |\n| Appendix B. List of Abbreviations and Acronyms ..............................................................................30 | Appendix B. List of Abbreviations and Acronyms ..............................................................................30 |\n| List of Tables | List of Tables |\n| Table 1. Variables for the Expected_Exploited() Equation....................................................................5 | Table 1."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nmSCP content can also be used to generate Security Content Automation Protocol (SCAP) content for automated security compliance scans. The SCAP generated follows the SCAP 1.3 specification [10]. The generation of SCAP content uses an Extensible Stylesheet Language Transformations (XSLT) file to create an Extensible Configuration Checklist Description Format (XCCDF) checklist document with an accompanying Open Vulnerability and Assessment Language (OVAL) document.\n\nOpen Vulnerability and Assessment Language"}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 5)"}, {"role": "assistant", "content": "quirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.\n## Keywords\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors also wish to recognize the scientists, engineers, and research staff from the NIST Computer Security and the Applied Cybersecurity Divisions for their exceptional contributions in helping to improve the content of the publication. A special note of thanks to Pat O'Reilly, Jim Foti, Jeff Brewer, Chris Enloe, Ned Goren, and the entire NIST web team for their outstanding administrative support. Finally, the authors also gratefully acknowledge the contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nFIPS 199 defines security categories for information systems based on potential impact on organizations, assets, or individuals should there be a breach of security-that is, a loss of confidentiality, integrity, or availability. FIPS 199 security categories can play an important part in defining information system boundaries by partitioning the agency's information systems according to the criticality or sensitivity of the information and information systems and the importance of those systems in accomplishing the agency's mission. This is particularly important when there are various FIPS 199 impact levels contained in one information system. The FIPS 199 requirement to secure an information\n\nFIPS 200 provides seventeen minimum security requirements for federal information and information systems. The requirements represent a broad-based, balanced information security program that addresses the management, operational, and technical aspects of protecting the confidentiality, integrity, and availability of federal information and information systems. An agency must meet the minimum security requirements in this standard by applying security controls selected in accordance with NIST SP 800-53 and the designated impact levels of the information systems. An agency has the flexibility to tailor the security control baseline in accordance with the terms and conditions set forth in the standard. Tailoring activities include: (i) the application of scoping guidance; (ii) the specification of compensating controls; and (iii) the specification of agency-defined parameters in the security controls, where allowed. The system security plan should document all tailoring activities."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.3.2. Presentation Attack Detection\nThe biometric system SHOULD implement PAD for iris and fingerprint modalities and\nSHALL implement PAD for facial recognition. Biometric comparison based on voice\nSHALL NOT be used. Testing the biometric system for deployment SHOULD demonstrate\nan impostor attack presentation accept rate (IAPAR) of less than 0.07. Presentation\nattack resistance SHOULD be tested in accordance with Clause 13 of [ISO/IEC30107-3]\nfollowing security evaluation methodologies in [ISO/IEC19792] or [ISO/IEC19989-1] and\n[ISO/IEC19989-3]. The PAD decision MAY be made either locally on the claimant’s device\nor by a central verifier.\n\n• First- or third-party testing against biometric performance standards\n\nTo be considered non-exportable, an authenticator SHALL either be a separate piece of\nhardware or an embedded processor or execution environment (e.g., secure element,\nTEE, TPM). These hardware authenticators and embedded processors are separate\nfrom a host processor, such as the CPU on a laptop or mobile device. A non-exportable\nauthenticator SHALL be designed to prohibit the export of the authentication secret\nto the host processor and SHALL NOT be capable of being reprogrammed by the host\nprocessor to allow the secret to be extracted. The authenticator is subject to applicable\n[FIPS140] requirements. Organizations SHOULD employ authenticators that have\nundergone independent security testing, such as authenticators validated to [FIPS140]\nsecurity level 2 overall with level 3 physical security6 or evaluated against relevant\nCommon Criteria Protection Profiles."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nIn terms of security configurations, organizations should use sound host hardening principles. For example, organizations should follow the principle of least privilege, which refers to configuring hosts to provide only the minimum necessary rights to the appropriate users, processes, and hosts. Least privilege can be helpful in preventing malware incidents, because malware often requires administrator-level privileges to exploit vulnerabilities successfully. If an incident does occur, prior application of least privilege might minimize the amount of damage that the malware can cause. Organizations should also implement other host hardening measures that can further reduce the possibility of malware incidents, such as the following:\n\nand what data sources might record the information. For example, a host's current IP address is typically needed for remote actions; of course, a host's physical location is needed for local actions. One piece of information can often be used to determine others, such as mapping an IP address to a media access control (MAC) address, which could then be mapped to a switch serving a particular group of offices. If an IP address can be mapped to a host owner or user-for example, by recording the mapping during network login-the owner or user can be contacted to provide the host's location. The difficulty in identifying the physical location of an infected host depends on several factors. In a managed environment, identifying a host's location is often relatively easy because of the standardized manner in which things are done. For example, host names might contain the user's ID or office number, or the host's serial number (which can be tied to a user ID). Also, asset inventory management tools might contain current information on host characteristics. In other environments, especially those in which users have full control over their hosts and network management is not centralized, it might be challenging to link a machine to a location."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 3)"}, {"role": "assistant", "content": "tandards and Technology (NIST), is a collabora�ve hub where industry organiza�ons, government agencies, and academic ins�tu�ons work together to address businesses' most pressing cybersecurity issues.\nThis public -private partnership enables the crea�on of prac�cal cybersecurity solu�ons for specific industries, as well as for broad, cross -sector technology challenges. Through consor�a under Coopera�ve Research and Development Agreements (CRADAs), including technology partners-from Fortune 50 market leaders to smaller companies specializing in informa�on technology securitythe NCCoE applies standards and best prac�ces to develop modular, adaptable example cybersecurity solu�ons using commercially available technology. The NCCoE documents these example solu�ons in the NIST Special Publica�on 1800 series, which maps capabili�es to the NIST Cyber security Framework and details the steps needed for another en�ty to re -create the example solu�on. The NCCoE was established in 2012 by NIST in partnership with the State of Maryland and Montgomery County, M aryland . To learn more about the NCCoE, visi t htps://www.nccoe.nist.gov/. To learn more about NIST, visit htps://www.nist.gov. ## NIST CYBERSECURITY PRACTICE GUIDES\n\nNIST Cybersecurity Prac�ce Guides (Special Publica�on 1800 series ) target specific cybersecurity challenges in the public and private sectors. They are prac�cal, user -friendly guides that facilitate the adop�on of standards -based approaches to cybersecurity. They show members of the informa�on security community how to implement example solu�ons that help them align with relevant standards and best prac�ces, and provide users with the materials lists, configura�on files, and other informa�on they need to implement a similar approach. The documents in this series describe example implementa�ons of cybersecurity prac�ces that businesses and other organiza�ons may voluntarily adopt."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.2.2 NICE Framework Work Roles ... 3.2.2 NICE Framework Work Roles ... 3.2.2 NICE Framework Work Roles ..."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 3)"}, {"role": "assistant", "content": "| help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n## Audience\n\n\n\n\n\nPages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality\n\n\n\nConfidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 \"Controlled Unclassified Information.\"\n\n## A Suite of Guidance\n\nNIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . \n\n\n\n\n\nNIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.5.3 3. 3.5.3 Exercises\n\nNIST SP 800-84 identifies the following types of exercises widely used in information system TT&E programs by single organizations:\n\n- ƒ Tabletop Exercises."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nThe terms 'shall' and 'shall not' indicate requirements to be followed strictly to conform to the publica�on and from which no devia�on is permited. The terms 'should' and 'should not' indicate that among several possibili�es, one is recommended as par�cularly suitable without men�oning or excluding others, or that a certain course of ac�on is preferred but not necessarily required, or that (in the nega�ve form) a certain possibility or course of ac�on is discouraged but not prohibited. The terms 'may' and 'need not' indicate a course of ac�on permissible within the limits of the publica�on. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical, or causal."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nar files to /lib/security/Unlimited/ and /lib/security/Limited in the Java installation directory. 6. Run install-server-windows-amd64. 7. Select the Java runtime that was just installed. 8. Click OK.\n| AD | Active Directory |\n|-------|---------------------------------------------------|\n| AMP | Advanced Malware Protection |\n| API | Application Programming Interface |\n| CEF | Common Event Format |\n| CSR | Certificate Signing Request |\n| CSV | Comma-Separated Values |\n| DNS | Domain Name System |\n| DSP | Directory Services Protector |\n| ESM | Enterprise Security Manager |\n| ICA | Information Centric Analytics |\n| IIS | Internet Information Services |\n| ISAPI | Internet Server Application Programming Interface |\n| ISE | Identity Services Engine |\n| IT | Information Technology |\n| JCE | Java Cryptography Extension |\n| JRE | Java Runtime Environment |\n| MAC | Media Access Control |\n| MMC | Microsoft Management Console |\n| MSSQL | Microsoft Structured Query Language |\n| MX | Mail Exchange |"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.4.4, which maps the security characteristics of the example solutions to cybersecurity standards and best practices\n\nIT and OT professionals who want to implement an approach like this will find the whole practice guide useful, particularly the how-to portion, NIST SP 1800-10C, which provides step-by-step details to replicate all, or parts of the example solutions created in our lab. 3.4.4 Security Control Map\n\nImplementation of cybersecurity architectures is most effective when executed in the context of an overall cybersecurity framework."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.4.4", "cmmc_practice_id": "CM.L2-3.4.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nding proactive notification to consumers, retailers, and third parties. Companies should track devices to address critical vulnerabilities and create structured options for off-ramping zombie devices.\nHigginbotham emphasized that company priorities often overlook device security. Manufacturers should implement vulnerability disclosure programs, track issues, conduct comprehensive security audits, and allocate budgets for security maintenance. Buyers must keep products updated or segmented, and legislation should clarify responsibility to ensure herd immunity. Companies should have a dedicated point of contact for security researchers and consider recalls for insecure devices. Stacey also addressed secure repairs, both before and after end of life. Good hardware should not end up in landfills, but unpatched zombie devices pose risks. Consumer Reports advocates for designing products for longevity, including features like hardware upgrades, crypto agility, and increased memory."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 9)"}, {"role": "assistant", "content": "ordinators Robert V. Jacobson, John Panagacos, and Thomas C. Lowe\nfor making things run smoothly while the Workshop was taking place; and\nDennis K. Branstad for photographing scenes from the Workshop.\nTHE EDITORS\n\nvi\n\n\fTABLE OF CONTENTS\n\nFOREWORD\n\nPREFACE\n\nEXECUTIVE SUMMARY\n\nPART I:\n\nINTRODUCTION\n\n1. 2. HOST WELCOMING ADDRESS\nEDITORS' COMMENTS ON THE SESSIONS AND THE REPORTS ... 2.1\n2.2\n2.3\n\nSome Definitions of Terms\nObservations\nReading the Proceedings\n\nPART II:\n\nKEYNOTE ADDRESS\n\n1. 2. 3. INTRODUCTION\nAN APPROACH TO THE WORKSHOP\nCOMMENTS ON PROPOSED TOPICS\n3.1\n3.2\n3.3\n3.4\n\n........ .... Internal Audit Standards\nQualifications and Training ............ ..... Security Administration\nAudit Considerations in Various System\n..... Environments\nAdministrative and Physical Controls ....... ..... Program Integrity\nData Integrity\nCommunications\nPost-Processing Audit Tools and Techniques .... Interactive Audit Tools and Techniques\n\n3.5\n3.6\n3.7\n3.8\n3.9\n3.10\n\nPART III:\n\n...... EDITORS' NOTE ....................... INTERNAL AUDIT STANDARDS\n\nSupplemental Standards for Internal Auditor's Expanded\nRole in Reviewing Computer Systems and Their Development . . 1. INTRODUCTION\n1.1\n1.2\n1.3\n\nAutomated Systems Effect on Environment ...... Computer Security Defined ............. Discussion of Audit Involvement in Computer\nChanging Auditor Requirement ........... 1.4\n\niii\n\niv\n\nxix\n\n1-1\n\n1-1\n1-3\n1-3\n1-4\n1-4\n\n2-1\n\n2-2\n2-2\n2-3\n2-3\n2-3\n2-4\n\n2-4\n2-4\n2-4\n2-4\n2-5\n2-5\n2-5\n\n3-1\n3-2\n\n3-3\n\n3-3\n3-3\n3-3\n\n3-5\n\nvi i\n\n\f. ,\n\n. . . . . o\n\n. . ,\n\n. o\n\n. o\n\n. . . 2. „\n\no\n\n. Commentary\n\nSUPPLEMENTAL STANDARDS FOR COMPUTER INTERNAL AUDIT\nWORK\n2.1\n2.2\n\nGeneral\nSupplemental Standard for Systems Development . 2. 2 J\nSupplemental Standard for Operational Systems\n(Application Controls)\n2.3.1\nSupplemental Standard for Physical Security and\nGeneral Controls\nCommentary\n2o4.1\nOther Audit Requirements\n\n2.3\n\n2.4\n\n2e5\n\nCommentary\n\n. o\n\n. . o\n\n. »\n\n„\n\n. =\n\n. „\n\no\n\n3. RECOMMENDED COURSE OF ACTION\n\no\n\n4."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 6)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2. Identity Proofing Roles . . . . . . . . . . . . . . . . . . . . . . . 2.1.3. Identity Proofing Types\n\n. . . . . . . . . . . . . . . . . . .\n. . . Core Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identity Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identity Evidence and Attributes . . . . . . . . . . . . . . . . . . . . . . 2.2. 2.3. 2.4. 2.4.1. Evidence Strength Requirements\n\n. . . . . . . . . . . . . . . . . 2.4.2. Identity Evidence and Attribute Validation . . . . . . . . . . . . 2.5. Identity Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1. Identity Verification Methods . . . . . . . . . . . . . . . . . . . 3. Identity Proofing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3.1. 3.2. Identity Service Documentation and Records . . . . . . . . . . . . . . . Fraud Management\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1. CSP Fraud Management . . . . . . . . . . . . . . . . . . . . . . 3.2.2. RP Fraud Management . . . . . . . . . . . . . . . . . . . . . . . 3.2.3. Treatment of Fraud Check Failures\n\n. . . . . . . . . . . . . . . . 3.3. General Privacy Requirements . . . . . . . . . . . . . . . . . . . . . . . 3.3.1. Privacy Risk Assessment . . . . . . . . . . . . . . . . . . . . . . 3.3.2. Additional Privacy Protective Measures . . . . . . . . . . . . . . 3.4. General Customer Experience Requirements . . . . . . . . . . . . . . . 3.5. General Security Requirements\n\n. . . . . . . . . . . . . . . . . . . . . . 3.6. Redress Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 1\n\n1\n\n2\n\n3\n\n3\n\n5\n\n5\n\n6\n\n7\n\n8\n\n9\n\n9\n\n9\n\n10\n\n12\n\n14\n\n14\n\n16\n\n16\n\n17\n\n18\n\n20\n\n21\n\n21\n\n21\n\n22\n\n23\n\n23\n\n24\n\niii\n\n\fNIST SP 800-63A-4\nJuly 2025\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\n3.7. Additional Requirements for Federal Agencies\n\n. . . . . . . . . . . . . . 3.8. 3.9."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nDespite their advantages, NoSQL databases lack a mechanism for handling and managing data consistency and maintaining integrity constraints (e.g., using foreign keys). Additionally, they often have limited support for security at the database level [OG]. NoSQL database systems offer promising features, such as flexible data models, horizontal scaling, and fast queries that allow for data analysis efficiency, improved system performance, ease of deployment, flexibility/scalability of data management, and users' availability when compared with RDBMS. However, despite these advantages, NoSQL databases lack a mechanism for handling and managing data consistency and maintaining integrity constraints. Additionally, they often have limited support for security at the database level. With an increasing number of people storing sensitive data in NoSQL databases, security issues are becoming critical concerns. Since access control is a fundamental data protection requirement for any database management system, this document discusses access control on NoSQL database systems by illustrating the NoSQL database types along with their support for access control models and describing considerations from the perspective of access control. 1. Resource providers (RPs) store information for sharing with federated members. The information is managed locally by the resource contributors or administrators of the RP. The availability and integrity of the resource is the central operation goal. 2. Resource managers (RMs) are responsible for locating the resources in response to the access request from a resource consumer. The security and accessibility of communications between the RPs and their connected resource consumers are the primary concerns of an RM. 3. Resource consumers (RCs) are client applications that accept user requests for resources and forward those requests to an RM."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nA VDPO may be an office with its own dedicated personnel or a virtual office with duties and roles assumed by members of the operating unit's ITSO. At a minimum, it will consist of staff who perform coordination and oversight duties and engagement with vulnerability disclosure reporters. However, the VDPO may extend to provide technical services to system owners to support their efforts in verifying and remediating vulnerabilities. In this case, the VDPO may include more technically oriented developers or systems administrators with security expertise.\n\nEach VDPO should develop the ability to communicate and coordinate with their FCB member to resolve vulnerability reports, which requires the development of both technical and personnel/procedural capabilities. If the FCB member provides technical mechanisms to streamline this process, the VDPO should use the provided mechanisms. It is also possible to procure commercial VDP services, particularly for reporting, tracking, and researcher communications."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\nSimilarly, assurance of forward secrecy (FS), as defined in this Recommendation, does not address problems that may arise from sources other than the compromise of static private key-agreement keys. There can be, of course, other threats to the security of derived keying material, such as the use of derived keys in cryptographic algorithms or devices that have been compromised. Improper storage or transport of keying material, the failure to prevent the leakage of sensitive information during computations involving the derived keys, and/or inadequate methods for the timely destruction of sensitive data (including ephemeral private keys and the derived keys themselves) are just a few examples of problems that could lead to an eventual compromise of keying material derived during a particular transaction."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guidelines for the Use of PIV Credentials in Facility Access provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-116 Revision 1\n\n## Guidelines for the Use of PIV Credentials in Facility Access\n\nHildegard Ferraiolo Ketan Mehta Nabil Ghadiali Jason Mohler Vincent Johnson Steven Brady\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-116r1\n\n## I N F O R M A T I O N S E C U R I T Y\n\n\n\n## NIST Special Publication 800-116\n\n## Revision 1\n\n## Guidelines for the Use of PIV Credentials in Facility Access\n\nHildegard Ferraiolo Ketan Mehta Computer Security Division Information Technology Laboratory\n\nNabil Ghadiali National Gallery of Art Washington, DC\n\nJason Mohler Vincent Johnson Steven Brady Electrosoft Services, Inc. Reston, Virginia\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-116r1\n\nJune 2018\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nThe supply chains of information and communications technologies are increasingly at risk of compromise. Additional risks causing supply chain disruptions include counterfeiting, unauthorized production, tampering, theft, and insertion of unexpected software and hardware. Managing these risks requires ensuring the integrity of the supply chain and its products and services. This project demonstrates how organizations can verify that the internal components and system firmware of the computing devices they acquire are genuine and have not been unexpectedly altered during manufacturing, distribution, or operational use. Technologies today rely on complex, globally distributed and interconnected supply chain ecosystems to provide highly refined, cost-effective, and reusable solutions. Most organizations' security processes consider only the visible state of computing devices. The provenance and integrity of a delivered device and its components are typically accepted without validating through technology that there were no unexpected modifications. A delivered device has integrity if it is genuine and all changes to the device were authorized and expected. Provenance is the comprehensive history of a device throughout the entire life cycle from creation to ownership, including changes made within the device or its components. Assuming without verification that all acquired computing devices are genuine and unmodified increases the risk that a compromise will affect products in an organization's supply chain and go unnoticed at the time, which in turn increases risks to customers and end users. Organizations currently lack the ability to cost effectively distinguish trustworthy products from others, meaning they are genuine and have not been inappropriately altered. Having this ability is a critical foundation of cyber supply chain risk management (C-SCRM)."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 8)"}, {"role": "assistant", "content": "ted, and the semiconductor supply chain stage at which mitigation is best applied. ## 3.2. Identify Hardware Threats\n\nThe second step is identifying the threats associated with the adversary's intent.\nFor example, if the intent is IP theft, then the IP to be protected must be identified. In this context, an attack on logic obfuscation can be characterized as a threat. Similarly, if the adversary intends to infiltrate hardware, then hardware Trojan insertion may need to be examined. ## 3.3. Analyze Stages of Hardware Development Life Cycle for Exploitability of the Threat\n\nAt this point, one or more significant hardware threats have been identified. The following stage involves determining which stage of the semiconductor supply chain the threat can be exploited. Questions such as how much threat an adversary in the manufacturing stage poses to logic obfuscation, or whether an adversary in the provisioning stage offers threats to hardware Trojan insertion, are raised. In light of a threat, this step determines the semiconductor supply chain's security-critical phases. In addition, this step determines if a threat is unexploitable at a specific point in the supply chain. ## 3.4. Analyze the Effect of Collusion Among Adversaries in Different Stages\n\nSince every stage of the semiconductor supply chain is distinct, adversaries have varying degrees of access to and knowledge of the system at different stages of the semiconductor\n\nsupply chain. The effectiveness of an attack depends largely on the adversary's knowledge of the system and their level of access. Different adversaries possess varying degrees of both. For example, a manufacturer may have detailed design knowledge, while an end user typically has limited access and little insight into a system's internal functions. As a result, their capabilities differ significantly."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 9)"}, {"role": "assistant", "content": "ms of the unbroken fourth-round candidates were invited to present updates for their candidate algorithms at the Fifth NIST PQC Standardization Conference in Rockville, Maryland, on April 10-12, 2024.\nThe submitters participated in a joint panel to discuss the candidates' merits, and several researchers presented work that was relevant to the PQC standardization process. Throughout the fourth round, NIST received valuable feedback from the cryptographic community. Based on this feedback and internal reviews of the fourth-round candidates, NIST announced the selection of HQC in March 2025 for standardization. Table 1 shows a timeline of major events with respect to the NIST PQC Standardization Process to date. Table 1."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.2.3 Library Operation | 4-10 4-10 |\n| | | | 4-11 |\n| | | 3. 3.2.3 Library Operation ."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n1.3.1. Security, Fraud, and Threat Prevention . . . . . . . . . . . . . .\n\n2.3.1. Authenticators . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.1. Define the Online Service . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Media Protection\n\nDescription: Protect system media, both paper and digital; limiting access to data on system media to authorized users; and sanitizing or destroying system media before disposal or release for reuse."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n- The SP 800-53, Revision 5 low baseline is a defined map of controls to secure a system defined as a low-impact information system. The loss of confidentiality, integrity, or availability could be expected to have a limited adverse effect on organizational operations, organizational assets, or individuals. - The SP 800-53, Revision 5 moderate baseline is a defined map of controls to secure a system defined as a moderate-impact information system. The loss of confidentiality, integrity, or availability could be expected to have a serious adverse effect on organizational operations, organizational assets, or individuals. - The SP 800-53, Revision 5 high baseline is a defined map of controls to secure a system defined as a high-impact information system. The loss of confidentiality, integrity, or availability could be expected to have a severe or catastrophic adverse effect on organizational operations, organizational assets, or individuals. offer a convenient, Apple-supported mechanism for applying security settings to a macOS environment. Additionally, they can be cryptographically signed to ensure integrity and authenticity. These factors make configuration profiles the preferred vehicle for configuration delivery. However, mobileconfig files cannot modify all macOS settings, so a configuration script is needed for those settings that are not supported. See the developer documentation page for an example configuration profile and brief descriptions of its properties. This example is for Tenable, Inc. They automated the conversion of mSCP YAML rules into their . audit format using Python and YAML libraries. Programmatically approaching this conversion allows for faster future releases and greater consistency, and it also maintains the integrity of the source content. Because the YAML content is all command-driven, it is converted to Tenable's CMD\\_EXEC check type for use with the Unix plugin."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 8)"}, {"role": "assistant", "content": "| .........................................................................................................\n4 |\n| | Organization of This Document .................................................................................. | 4 |\n| | The Enterprise Cloud-Native Platform and its Components......................................... | 5 |\n| | Enterprise Infrastructure Layer ..................................................................................."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n- event detection\n- integrity monitoring\n- logging\n- reporting\n- mitigation and containment\n- forensics/analytics\n\n-  detect malicious and suspicious activity generated on the network, by users, or from applications that could indicate a DI event\n-  mitigate and contain the effects of events that can cause a loss of DI\n-  monitor the integrity of the enterprise for detection of events and after-the-fact analysis\n-  utilize logging and reporting features to speed response time to DI events\n-  analyze DI events for the scope of their impact on the network, enterprise devices, and enterprise data\n-  analyze DI events to inform and improve the enterprise's defenses against future attacks\n\n- logging\n- reporting\n- mitigation and containment\n- forensics/analytics"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Developing Security Plans for Federal Information Systems provide? (Part 3)"}, {"role": "assistant", "content": "Plans for Information Technology System. The original document was used as the foundation for this revision. Additionally, thank you to all the NIST staff that reviewed and commented on the document.\niv\n\n## Table of Contents\n\n| EXECUTIVE SUMMARY.......................................................................................................... | VII |\n|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1. INTRODUCTION ........................................................................................................................ | 1 |\n| 1.1 BACKGROUND............................................................................................................................ | 1 |\n| 1.2 TARGET AUDIENCE.................................................................................................................... | 1 |\n| 1.3 ORGANIZATION OF DOCUMENT.................................................................................................. | 1 |\n| 1.4 SYSTEMS INVENTORY AND FEDERAL INFORMATION PROCESSING STANDARDS (FIPS 199) | ......"}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nIn reality, a federated community may be networked in a variety of architectures. The three basic services may be incorporated or simplified such that more than one service is managed or hosted in one physical system. However, these three services and their connections are assumed to be essential for any resource-sharing federation, and the resource-sharing protocols between them are composed by interlacing the following scenarios:"}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - Can be used by organizations in any sector or community, regardless of size or cybersecurity sophistication\n- Can be applied to software developed to support information technology (IT), industrial control systems (ICS), cyber-physical systems (CPS), or the Internet of Things (IoT)\n- Can be integrated into any existing software development workflow and automated toolchain; should not negatively affect organizations that already have robust secure software development practices in place\n- Makes the practices broadly applicable, not specific to particular technologies, platforms, programming languages, SDLC models, development environments, operating environments, tools, etc."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 6)"}, {"role": "assistant", "content": "| List of Figures |\n| Fig. 1.\nCumulative distribution of LEV probabilities (3/6/2025)..........................................................16 | Fig. 1. Cumulative distribution of LEV probabilities (3/6/2025)..........................................................16 |\n| Fig. 2. LEV distribution using binning ................................................................................................17 | Fig. 2. LEV distribution using binning ................................................................................................17 |\n| Fig. 3. LEV Distribution using binning (excluding bins of less than 0.03)..............................................17 | Fig. 3. LEV Distribution using binning (excluding bins of less than 0.03)..............................................17 |\n| Fig. 4. Recall measurements for LEV and CISA KEV ............................................................................19 | Fig. 4. Recall measurements for LEV and CISA KEV ............................................................................19 |\n| Fig. 5. EPSS Performance, graph copied from [4] ...............................................................................23 | Fig. 5. EPSS Performance, graph copied from [4] ...............................................................................23 |\n\n## 1. Introduction\n\nThis work provides a novel security metric to determine the likelihood that a vulnerability has been observed to be exploited. Only a small fraction of the tens of thousands of software and hardware vulnerabilities that are published every year will be exploited."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.5.1\n3. 3.5.1\n\nSelect the Verification Techniques\n\nIn general, two approaches can be applied in verifying controls and\n\nprocessing:\n\n-Test of results:\n\nSelect one or more key files or outputs of pro-\n\ncessing and confirm the results. 3.5.1 ."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n3.2.3. 3.2.3."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-09-25 Supersedes NIST Special Publication 800-161r1 (May 2022) https://doi.org/10.6028/NIST.SP.800-161r1\n\n## How to Cite this NIST Technical Series Publication\n\nBoyens J, Smith A, Bartol N, Winkler K, Holbrook A, Fallon M (2022) Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-161r1-upd1, Includes updates as of Novem ber 1, 2024. https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n\n## Author ORCID iDs\n\nJon Boyens: 0000-0002-5666-8750\n\n## Contact Information\n\nscrm-nist@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/161/r1/upd1/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nOrganizations are concerned about the risks associated with products and services that may potentially contain malicious functionality, are counterfeit, or are vulnerable due to poor manufacturing and development practices within the supply chain."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n| | INTRODUCTION................................................................................................................. 1 | INTRODUCTION................................................................................................................. 1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | STUDY METHODOLOGY................................................................................................. 2 | STUDY METHODOLOGY................................................................................................. 2 |\n| 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 | 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 | 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 |\n| 2.1.1 | Focus Group Design..................................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | ## 1 Introduction In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Incident Response?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 10)"}, {"role": "assistant", "content": "s that might cause some concern. This report focuses on the reasons why candidate algorithms were selected rather than\nproviding detailed justifications for why candidate algorithms were not selected.\nSection 4 describes the next steps in the Additional Digital Signatures for the NIST PQC\nStandardization Process, including provisions for allowable modifications to the second-\nround candidates and the evaluation process for selecting finalists. 2\n\n\fNIST IR 8528\nOctober 2024\n\nAdditional Digital Signatures\nFirst Round Status Report\n\n2. Evaluation Criteria and the Selection Process\n\n2.1. Acceptance of the First-Round Candidates\n\nNIST received 50 candidate algorithm submission packages by the entry deadline of June\n1, 2023. Of these, NIST accepted 40 first-round candidates that met both the submission\nrequirements and the minimum acceptability criteria for being “complete and proper sub-\nmissions,” as defined in [2]. Table 2. First-round digital signature candidates organized by category, with the\ncandidates selected to advance to the second round bolded and in blue. The starred\nsignature schemes MIRA and MiRitH merged to form a new candidate Mirath. Code-Based\nCROSS\n Enhanced pqsigRM\n FuLeeca\nLESS\n MEDS\n WAVE\n\nLattice-Based\n EagleSign\n EHTv4\n HAETAE\nHAWK\n HuFu\n Raccoon\n SQUIRRELS\n\nOther\n ALTEQ\n eMLE-Sig 2.0\n KAZ-SIGN\n PREON\n Xifrat1-Sign.I\n\nSymmetric-Based\n AIMer\n Ascon-Sign\nFAEST\n SPHINCS-alpha\n\nMPC-in-the-Head Multivariate\n\n Biscuit\nMIRA*\nMiRitH*\nMQOM\nPERK\nRYDE\nSDitH\n\nIsogeny-Based\nSQIsign\n\n 3WISE\n DME-Sign\n HPPC\nMAYO\n PROV\nQR-UOV\nSNOVA\n TUOV\nUOV\n VOX\n\nThe criteria for determining the first round candidates included provisions for reference\nand optimized C code implementations, known-answer tests, a written specification, and\nrequired intellectual property statements. These were the sole criteria used to judge the\nsubmission packages."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 9)"}, {"role": "assistant", "content": "| ...............................................................................................\n9 |\n| | Configuration Profiles and Scripts............................................................................... | 9 |\n| | Content Generation Scripts........................................................................................10 | |\n| 3.4.1. | Generate Baseline Script.......................................................................................10 | |\n| 3.4.2. | Generate Guidance Script .....................................................................................10 | |\n| 3.4.3. | macOS Security Compliance Tool .........................................................................11 | |\n| 3.4.4."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n3.2.1. 3.2.1."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\n\n\n## NIST Interagency Report NIST IR 8562\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nKaterina N. Megas Michael Fagan Barbara Cuthill Brad Hoehn Evie Petrella\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8562\n\n\n\n## NIST Interagency Report NIST IR 8562\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nKaterina N. Megas Michael Fagan Barbara Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nBrad Hoehn HII\n\nEvie Petrella Electrosoft Services, Inc. This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8562\n\nApril 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nNational Institute of Standards and Technology\n\nCraig S. Burkhardt, Acting NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-03-21\n\n## How to Cite this NIST Technical Series Publication\n\nMegas K, Fagan M, Cuthill B, Hoehn N, and Petrella E (2025) Summary Report for 'Workshop on Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Blockchain for Access Control Systems provide? (Part 8)"}, {"role": "assistant", "content": "blockchain system ....................8 | | Figure 5 - Example 4 of access control function points implemented in blockchain systems......................9 | Figure 5 - Example 4 of access control function points implemented in blockchain systems......................9 | | Figure 7 - Examples of Figure 2d with attribute source options.................................................................10 | Figure 7 - Examples of Figure 2d with attribute source options.................................................................10 | | Figure 6 - Attribute source is out of the chain ............................................................................................10 | Figure 6 - Attribute source is out of the chain ............................................................................................10 | | List of Tables | List of Tables | | 1 - Comparison of IoT AC system capabilities for general access control requirements by | 1 - Comparison of IoT AC system capabilities for general access control requirements by | | Table | Table | ## 1 Introduction Access control (AC) is concerned with determining the allowed activities of legitimate users and mediating every attempt by a user to access a resource in the system."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . .\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.1. Truncation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.2. Nonce Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.3. AEAD Requirements.............................................................. | 19 |\n| 4.4. Security Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.1. Single-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.2. Multi-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.3. Nonce-Misuse Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 21 |\n| 5. Hash and eXtendable-Output Functions (XOFs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.1. Specification of Ascon-Hash256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.2. Specification of Ascon-XOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 25 |\n| 5.3. Specification of Ascon-CXOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 28 |\n| 5.4. Streaming API for XOF............................................................ | 30 |\n| 5.5. Security Strengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nDigiCert's CertCentral web -based platform allows provisioning and managing publicly trusted X.509 certificates for TLS and code signing and a variety of other purposes. After establishing an account, clients can log in, request, renew, and revoke certificates via a browser. Multiple roles can be assigned within an account, and a discovery tool can inventory all certificates within the enterprise. In addition to certificatespecific features, the platform offers baseline enterprise SaaS capabilities, includi ng rolebased access control (RBAC), Security Assertion Markup Language (SAML), single sign -on (SSO), and security policy management and enforcement. All account features are fully compatible with the web portal and a publicly available API. Learn more about DigiCert at https://www.digicert.com. F5, Inc. is a publicly-held American technology company specializing in application security , multi -cloud management, online fraud prevention, application delivery networking, application availability & performance, network security, and access & authorization. F5 is headquartered in Seattle, Washington, with an additional 75 offices in 43 countries , focusing on account management, global services support, product development, manufacturing, and software engineering. F5 offers application delivery controller technology, application layer automation, multi -cloud, and security services. The company offe rs modules on its proprietary operating system, TMOS (Traffic Management Operating System), including Local Traffic Manager, Advanced Web Application Firewall, Domain Name Service, and Access Policy Manager. The modules offer the ability to deploy load balancing, Layer 7 application firewalls, SSO (for Active Directory [AD] ) , Azure AD, Lightweight Directory Access Protocol (LDAP), and enterprise -level virtual private networks."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| | 2.5.1.2 | 2.5.1.2 | Differences in Audit Approach | 34 | |-------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------|-----------| | | 2.5.2 Off-The-Shelf SoftwareATurnkey Systems | 2.5.2 Off-The-Shelf SoftwareATurnkey Systems | 2.5.2 Off-The-Shelf SoftwareATurnkey Systems | 35 | | | 2.5.2.1 | 2.5.2.1 | Differences from the AIS Life Cycle Matrix | 36 | | | 2.5.2.2 | 2.5.2.2 | Differences in Audit Approach | 37 | | | AIS | AIS | AIS | | | 2.6 | LIFE CYCLE DOCUMENTATION | LIFE CYCLE DOCUMENTATION | LIFE CYCLE DOCUMENTATION | 37 | | | 2.6.1 Needs Statement | 2.6.1 Needs Statement | 2.6.1 Needs Statement | 38 | | | 2.6.2 | Feasibility Study Document | Feasibility Study Document | 38 | | | 2.6.3 | Risk Analysis | Risk Analysis | 38 | | | 2.6.4 | Cost/Benefit Analysis | Cost/Benefit Analysis | 40 | | | 2.6.5 | System Decision Paper | System Decision Paper | 40 | | | 2.6.6 | Audit Plan | Audit Plan | 40 | | | 2.6.7 | Project Plan | Project Plan | 41 | | | 2.6.8 | Requirements Documents | Requirements Documents | 41 | | | | Functional Requirements Document | Functional"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/61/r3/final, including related content, potential updates, and document history. Within this document, an event is any observable occurrence that involves computing assets, including physical and virtual platforms, networks, services, and cloud environments. Examples of events are user login attempts, the installation of software updates, and an application responding to a transaction request. Many events focus on security or have security implications. Adverse events are any events associated with a negative consequence regardless of cause, including natural disasters, power failures, or cybersecurity attacks. This guide addresses only adverse cybersecurity events . Additional analysis is often needed to determine whether adverse cybersecurity events indicate that a cybersecurity incident has occurred."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 8)"}, {"role": "assistant", "content": "----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 5.3.1.\nAccess Control (§ 164.312(a)).....................................................................................................65 |\n| 5.3.2. Audit Controls (§ 164.312(b)).....................................................................................................69 |\n| 5.3.3. Integrity (§ 164.312(c))...............................................................................................................71 |\n| 5.3.4. Person or Entity Authentication (§ 164.312(d)).........................................................................73 |\n| 5.3.5. Transmission Security (§ 164.312(e)(1)).....................................................................................75 |\n| 5.4.1. Business Associate Contracts or Other Arrangements (§ 164.314(a)).......................................77 |\n| 5.4.2. Requirements for Group Health Plans (§ 164.314(b))................................................................79 |\n| 5.5.1."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nThe Institute consists of the following Divisions: | 2.1 | BACKGROUND | BACKGROUND | BACKGROUND | 16 | |-------|------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|------| | | 2.1.1 | PCIE - EDP Systems Review and Security Work Group | PCIE - EDP Systems Review and Security Work Group | 16 | | | 2.1.2 | System Development Life Cycle | System Development Life Cycle | 16 | | 2.2 | OPERATING ENVIRONMENT | OPERATING ENVIRONMENT | OPERATING ENVIRONMENT | 17 | | | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 17 | | | 2.2.1.1 IRM Planning | 2.2.1.1 IRM Planning | 2.2.1.1 IRM Planning | 17 | | | 2.2.1.2 Using Policy/Procedures/Standards | 2.2.1.2 Using Policy/Procedures/Standards | 2.2.1.2 Using Policy/Procedures/Standards | 18 | | | 2.2.1.2.1 | 2.2.1.2.1 | References Used by the Life Cycle Matrix | 19 | | | 2.2.1.2.2 | 2.2.1.2.2 | Major GSA References | 21 | | | 2.2.2 AIS Development Methodologies | 2.2.2 AIS Development Methodologies | 2.2.2 AIS Development Methodologies | 21 | | | 2.2.3 Project Administration and Control | 2.2.3 Project Administration and Control | 2.2.3"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n|\n| Federal Vulnerability Disclosure Coordination Body ....................................................\n| 6 | |\n| Preparation................................................................................................................. | 7 | |\n| 2.1.1. Create Source Vulnerability | Report Receipt Capability............................................. 7 | |\n| 2.1.2. Determine Scope and Obtain Contacts .................................................................... | 8 | |\n| 2.1.3. Develop Technical Analysis Capability ....................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\ny' and 'need not' indicate a course of ac�on permissible within the limits of the publica�on. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical, or causal.\n| 1 | Executive Summary.............................................................................1 | Executive Summary.............................................................................1 |\n|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | Introduction........................................................................................2 | Introduction........................................................................................2 |\n| | 2.1 | Audience ......................................................................................................................"}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.6 (NIST 3.4.6)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.4.6 Roles and Responsibilities ... 3.4.6 Roles and Responsibilities ... 3.4.6."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.4.6", "cmmc_practice_id": "CM.L2-3.4.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n## Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations\n\n## Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations\n\nBoyens J, Smith A, Bartol N, Winkler K, Holbrook A, Fallon M (2022) Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-161r1-upd1, Includes updates as of Novem ber 1, 2024. https://doi.org/10.6028/NIST.SP.800-161r1-upd1"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide? (Part 2)"}, {"role": "assistant", "content": "n Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562.\nhttps://doi.org/10.6028/NIST.IR.8562\n\n## Author ORCID iDs\n\nKaterina Megas: 0000-0002-2815-5448 Michael Fagan: 0000-0002-1861-2609 Barbara Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Abstract\n\nThis report summarizes the feedback received by the NIST Cybersecurity for the Internet of Things (IoT) program at the in-person and hybrid workshop on \"Updating Manufacturer Guidance for Securable Connected Product Development\" held in December 2024. The purpose of this workshop was to consider how to update Foundational Cybersecurity Activities for IoT Device Manufacturers (NIST Internal Report (IR) 8259) based on concepts in risk management, operational technology concerns, product end of life concerns and recent trends in IoT cybersecurity and privacy. Over time, the NIST volume of work has built upon the concepts introduced in NIST IR 8259,to add technical (NIST IR 8259A) and nontechnical (NIST IR 8259B) concepts to help manufacturers and customers consider the cybersecurity of IoT devices. The NIST IR 8259 series has been used to inform and develop subsequent publications that elaborate on IoT cybersecurity across sectors and use cases (e.g., federal agency uses cases reflected in NIST SP 800-213 and consumer use cases reflected in NIST IR 8425 and the U.S. Cyber Trust Mark). ## Keywords\n\ncybersecurity baseline; Internet of Things (IoT); IoT products; manufacturing; privacy; risk management; securable products; security requirements; software development; threat modelling. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.3.2 Job Experience\n\n## Focus Groups\n\nIn the focus group demographic survey, we asked participants how many years they had worked as government employees, in their current organization, and in a cybersecurity role."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| |----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | ASSESSMENT OBJECTIVE Determine if: | ASSESSMENT OBJECTIVE Determine if: | | | 3.1.1e[a] | Critical or sensitive system and organizational operations for which dual authorization is to be enforced are identified."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Security Assessment?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nThe intended audience for this report consists of manufacturers of consumer products, especially product security officers, retailers and related integrators and technical support firms serving the consumer and business sectors, and testing and certification bodies interested in establishing baselines of IoT cybersecurity capabilities. - create the IoT product (i.e., used to create each product component). - ii. IoT platform used in the development and operation of the IoT product, its product components, including related documentation. - iii. Trustworthiness and protection of software and hardware elements implemented to create the IoT product and its product components (e.g., secure boot, hardware root of trust, and secure enclave). - iv. Consideration for the known risks related to the IoT product and known potential misuses. - v. Secure software development and supply chain practices used. - vi. Accreditation, certification, and/or evaluation results for cybersecurity-related practices. - vii. The ease of installation and maintenance of the IoT product by a customer (i.e., the usability of the product [ISO9241]). - e. Maintenance requirements for the IoT product, for example :\n- i. Cybersecurity maintenance expectations and associated instructions or procedures (e.g., vulnerability/patch management plan). - ii. How the IoT product developer identifies authorized supporting parties who can perform maintenance activities (e.g., authorized repair centers). - iii. Cybersecurity considerations of the maintenance process (e.g., how customer data unrelated to the maintenance process remain confidential even from maintainers). - f. The secure system lifecycle policies and processes associated with the IoT product, including:\n- i. Steps taken during development to ensure the IoT product and its product components are free of any known, exploitable vulnerabilities. - ii."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. This publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, 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."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nSecurity is a collective responsibility involving manufacturers, integrators, and asset owners and operators. CISA helps clarify security roles and ensures all parties uphold their responsibilities. The key component of secure by design is seeing where manufacturers can embed cyber security from the start to make it more difficult or impossible for an integrator or asset owner to open a cyber security risk. Current US critical infrastructure contains legacy systems without security functionality that inherently complicate adding security today. Infrastructure improvement options include the present 'Bubble Boy' method, which segments all traffic, ta rgeted improvements, and the 'rip and replace' method. Secure operational technology (OT) devices need to be available to provide that defense in depth, so that any failures in segmentation do not result in total data protection. It emphasizes open standards and autonomy at the asset and operator level. Resilience features should resemble those in the enterprise space, including secure compromise. Secure-by-design for OT considers threat categories like vulnerability handling and communications, resilience, logging, and end-device capabilities. Stacey Higginbotham of Consumer Reports noted that connected devices establish an ongoing relationship between the buyer, seller, and manufacturer. The lifetime of a connected product is often separate from its physical state. While physical products fail in visible ways, software degrades more quickly, often without consumer awareness. The industry also lacks adequate support for maintenance. Stacey's discussion highli ghted three key areas: zombie hordes of end of life devices, supported devices with unsupportive owners, and herd immunity against malicious actors. ' Zombie devices ' are those that no longer receive software support and security updates. Higginbotham noted that unsupportive owners can neglect cybersecurity issues, leading to vulnerabilities."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 7)"}, {"role": "assistant", "content": "Romine Thomas Michelli Director, Information Technology Laboratory Chair-Defense Community Donna Dodson Susan Dorr-Intelligence Community Co-Chair Cybersecurity Advisor, Information Technology Laboratory Matt Scholl Vicki Michetti Tri-Chair-Defense Community Chief, Computer Security Division Kevin Stine Chris Johnson Chief, Applied Cybersecurity Division Tri-Chair-Intelligence Community Ron Ross Paul Cunningham FISMA Implementation Project Leader Tri-Chair-Civil Agencies ## Joint Task Force Working Group | Ron Ross | Kevin Dulany | Peter Duspiva | Kelley Dempsey | |--------------------|----------------------------------|------------------------------------|----------------------| | NIST, JTF Leader | DoD | Intelligence Community | NIST | | Taylor Roberts OMB | Ellen Nadeau NIST | Victoria Pillitteri NIST | Naomi Lefkovitz NIST | | Jordan Burris OMB | Charles Cutshall OMB | Kevin Herms OMB | Carol Bales OMB | | Jeff Marron NIST | Kaitlin Boeckl NIST | Kirsten Moncada OMB | Jon Boyens NIST | | Dorian Pappas CNSS | Dominic Cussatt Veterans Affairs | Esten Porter The MITRE Corporation | Celia Paulsen NIST | | | Christina Sames | Julie Snyder | Martin Stanley | | Daniel Faigin | | | | | The Aerospace | The MITRE Corporation | The MITRE | Homeland Security | | Corporation | | Corporation | | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ The authors also wish to recognize Matt"}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 10)"}, {"role": "assistant", "content": "n and establishment methods\n\nFor the current list of CMVP-approved sensitive security parameter generation and establishment methods, see https://csrc.nist.gov/projects/cmvp/sp800-140d. ## Appendix A.\nDocument Revisions\n\n| Edition | Date | Change |\n|-----------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Revision 1 (r1) | May 2022 | 6.1 Purpose Added language on CMVP-approved security functions. 6.2 Sensitive security parameter generation and establishment methods Added/Modified: Security function subsection headers. 6.2.1 Transitions Removed: SP 800-131A Rev."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 8)"}, {"role": "assistant", "content": "inted National Coordinator for Smart Grid Interoperability at in April 2009. He has been responsible for leading the development of standards underpinning the nation's Smart Grid. In October 2011, Dr.\nArnold added an additional role as Director of Cyber Physical Systems within NIST's Engineering Laboratory (EL). Anticipating and meeting the measurement science and standards needs for technology-intensive manufacturing construction, and cyber-physical systems in ways that enhance economic prosperity and improve the quality of life , EL promotes U.S. innovation and industrial competitiveness in areas of critical national priority. Dr. Arnold served as Chairman of the Board of the American National Standards Institute (ANSI), a private, non-profit organization that coordinates the U.S. voluntary standardization and conformity assessment system, from 2003 to 2005. He served as President of the IEEE Standards Association in 2007-2008 and as Vice President-Policy for the International Organization for Standardization (ISO) from 2006-2009 where he was responsible for guiding ISO's strategic plan. Dr. Arnold previously served as a Vice-President at Lucent Technologies Bell Laboratories where he directed the company's global standards efforts. His organization played a leading role in the development of international standards for Intelligent Networks and IP-based Next Generation Networks. In previous assignments at AT&T Bell Laboratories he had responsibilities in network planning, systems engineering, and application of information technology to automate operations and maintenance of the nationwide telecommunications network. Dr. Arnold received a Doctor of Engineering Science degree in Electrical Engineering and Computer Science from Columbia University in 1978. He is a Fellow of the IEEE. \n\n\n\n\n\n\n\n\n\n\n\n\n\n## 3."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Access Control on NoSQL Databases provide? (Part 2)"}, {"role": "assistant", "content": "aft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-05-01\n\n## How to Cite this NIST Technical Series Publication:\n\nHu VC (2024) Access Control on NoSQL Databases. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8504. https://doi.org/10.6028/NIST.IR.8504\n\n## Author ORCID iDs\n\nVincent C. Hu: 0000-0002-1648-0584\n\n## Contact Information\n\nir8504-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8504/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nNoSQL database systems and data stores often outperform traditional RDBMS in various aspects, such as data analysis efficiency, system performance, ease of deployment, flexibility/scalability of data management, and users' availability. However, with an increasing number of people storing sensitive data in NoSQL databases, security issues have become critical concerns. NoSQL databases suffer from vulnerabilities, particularly due to the lack of effective support for data protection, including weak authorization mechanisms. As access control is a fundamental data protection requirement of any database management system DBMS, this document focuses on access control on NoSQL database systems."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nThe profile builds on the NISTIR 8259 series by extending the IoT core baseline for consumer IoT products. NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers [IR8259], provides foundational guidance for IoT device manufacturers pertaining to developing IoT devices that can be used securely by customers. NISTIR 8259 does not target any specific IoT sector but discusses how manufacturers can approach cybersecurity for IoT devices in general. NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline [IR8259A] and NISTIR 8295B, IoT Non-Technical Supporting Capability Core Baseline [IR259B] define the IoT device cybersecurity capability core baseline (also referred to as the core baseline). The core baseline is a starting point for manufacturers to use in identifying the cybersecurity capabilities their customers may expect from the IoT devices they create. NISTIR 8259A discusses device cybersecurity capabilities, which are functions or features implemented by the device through its own hardware and software. For example, NISTIR 8259A discusses concepts such as data protection, access control, and software update, among others. NISTIR 8259B discusses non-technical supporting capabilities, which are actions taken by organizations to support the cybersecurity of the device. For example, NISTIR 8259B discusses concepts such as education and awareness, and information and query reception (e.g., by manufacturers/developers).\n\n## Cybersecurity State Awareness\n\n## Product Education and Awareness"}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n| | Introduction ...................................................................................................................... | Introduction ...................................................................................................................... |\n|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|\n| | Purpose and Scope.................................................................................................... | 1 |\n| | Audience .................................................................................................................... | 1 |\n| | Relevance to NIST SP 800-70 and the National Checklist Program ..........................."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n## Secure Software Development Framework (SSDF) Version 1.1:\n\n## Secure Software Development Framework (SSDF) Version 1.1:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MP.L2-3.8.1 (NIST 3.8.1)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.8.1 | The Audit Organization | The Audit Organization | 65 |\n| | 3. 3.8.1 The Audit Organization\n\nThe NBS/PCIE workshop attendees came up with a number of recommendations for further activity by ADP Audit/Computer Security Organizations."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.8.1", "cmmc_practice_id": "MP.L2-3.8.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST. This guideline focuses on identity proofing and enrollment for use in digital\nauthentication. During the process of identity proofing, an applicant provides evidence\nto a credential service provider (CSP) reliably identifying themselves, thereby allowing\nthe CSP to assert that identification at a useful identity assurance level. This document\ndefines technical requirements for each of three identity assurance levels. The guidelines\nare not intended to constrain the development or use of standards outside of this\npurpose. This publication supersedes NIST Special Publication (SP) 800-63A. The Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 4)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 2 | IoT Device Cybersecurity Capability Core Baseline Definition..........................3 | | References...................................................................................................................11 | References...................................................................................................................11 | | Appendix A-Understanding the IoT Device Cybersecurity Capability Core Baseline in the Context of Customer Needs and Goals...........................................14 | Appendix A-Understanding the IoT Device Cybersecurity Capability Core Baseline in the Context of Customer Needs and Goals...........................................14 | | Appendix B-Glossary ..............................................................................................16 | Appendix B-Glossary ..............................................................................................16 | ## Patent Disclosure Notice NOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| PO.2.1: Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed. | High | R1: Include AI model development security in SDLC-related roles and responsibilities throughout the SDLC. The roles and responsibilities should include, but are not limited to, AI model development, AI model operations, and data science. N1: Roles and responsibilities involving AI system producers, AI model producers, and other third-party providers can be documented in agreements. | AI RMF: Govern 2.1 |\n| Implement Roles and Responsibilities (PO.2): Ensure that everyone inside and outside of the organization involved in the SDLC is prepared to perform their SDLC-related roles and responsibilities throughout the SDLC. | PO.2.2: Provide role-based training for all personnel with responsibilities that contribute to secure development. Periodically review personnel proficiency and role-based training, and update the training as needed. | High | R1: Role-based training should include understanding cybersecurity vulnerabilities and threats to AI models and their possible mitigations. | AI RMF: Govern 2.2 OWASP: LLM04-7 |\n| Implement Roles and Responsibilities (PO.2): Ensure that everyone inside and outside of the organization involved in the SDLC is prepared to perform their SDLC-related roles and responsibilities throughout the SDLC. | PO.2.3: Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development- related roles and responsibilities. | Medium | R1: Leadership should commit to secure development practices involving AI models."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n3.4.2e | ENHANCED SECURITY REQUIREMENT Employ automated mechanisms to detect misconfigured or unauthorized system components; after detection, [ Selection (one or more): remove the components; place the components in a quarantine or remediation network ] to facilitate patching, re- configuration, or other mitigations. 3.4.2e_ODP[1] | One or more of the following is/are selected: remove the components; place the components in a quarantine or remediation network. 3.4.2e[a] | Automated mechanisms to detect misconfigured or unauthorized system components are identified."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Key Activities | Description | Sample Questions | |-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | • What are the human, natural, and environmental threats to systems that contain, store, process, or transmit ePHI?"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.4. Mirath (MIRA/MiRitH)\n\n3.4. Mirath (MIRA/MiRitH)"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n31 |\n| Table 10. Address for each byte of Ascon state word 𝑆 𝑖 in memory on little-endian and big-endian machines, where the word 𝑆 𝑖 begins at memory address 𝑎 . . . . . . . . . . | 36 |\n| Table 11.\nExamples of padding an unsigned integer 𝑥 to a 64-bit block, where 𝑥 encodes a sequence of bytes that each have value 0xFF in little-endian byte order . | 38 |\n| Table 12. Precomputedinitialization phasevaluesfor Ascon-Hash256 , Ascon-XOF128 and Ascon-CXOF128 provided in hexadecimal integer form . . . . . . . . . . . . . . . . . . . . . . . . . . | 40 |\n| Table 13. Parameters for initial value construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 40 |\n| Table 14. Initial values as hexadecimal integers......................................... | 41 |"}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 9)"}, {"role": "assistant", "content": "the reference design, or have questions about applying it in your environment, please email us at supplychain-nccoe@nist.gov. All comments are subject to release under the Freedom of Information Act.\nNational Cybersecurity Center of Excellence National Institute of Standards and Technology 100 Bureau Drive Mailstop 2002\n\nGaithersburg, MD 20899\n\nEmail: nccoe@nist.gov\n\n## NATIONAL CYBERSECURITY CENTER OF EXCELLENCE\n\nThe National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity issues. This public-private partnership enables the creation of practical cybersecurity solutions for specific industries, as well as for broad, cross-sector technology challenges. Through consortia under Cooperative Research and Development Agreements (CRADAs), including technology partners -from Fortune 50 market leaders to smaller companies specializing in information technology security -the NCCoE applies standards and best practices to develop modular, adaptable example cybersecurity solutions using commercially available technology. The NCCoE documents these example solutions in the NIST Special Publication 1800 series, which maps capabilities to the NIST Cybersecurity Framework and details the steps needed for another entity to re-create the example solution. The NCCoE was established in 2012 by NIST in partnership with the State of Maryland and Montgomery County, Maryland. To learn more about the NCCoE, visit https://www.nccoe.nist.gov/. To learn more about NIST, visit https://www.nist.gov. ## NIST CYBERSECURITY PRACTICE GUIDES\n\nNIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\nC-SCRM practitioners identify, assess, and mitigate cybersecurity risks throughout the supply chain at all levels of their organizations associated with information and communications technology (ICT) products and services. Potential risks include malicious functionality, counterfeit devices, or vulnerabilities derived from poor manufacturing and development practices within the supply chain."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n............................................................... 78 |\n| | 8.3 KAS2 Key Agreement......................................................................................................\n| 79 |\n| | 8.3.1 KAS2 Assumptions................................................................................................ | 80 |\n| | 8.3.2 KAS2-basic ............................................................................................................ | 81 |\n| | 8.3.3 KAS2 Key Confirmation........................................................................................ | 83 |\n| | 8.3.3.1 | KAS2 Key-Confirmation Components...................................................... 83 |\n| | 8.3.3.2 KAS2-Party_V-confirmation | ..................................................................... 83 |\n| | 8.3.3.3 KAS2-Party_U-confirmation | ..................................................................... 84 |\n| | 8.3.3.4 KAS2-bilateral-confirmation......................................................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 9)"}, {"role": "assistant", "content": "...................................................................... | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................ | 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING..............................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 5)"}, {"role": "assistant", "content": "......................................................... | 1. Introduction.............................................................................................................................\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Scope and Purpose.................................................................................................................. 1 | 2. Scope and Purpose.................................................................................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.4.4 | Equipment Replacement ... 3.4.4 Equipment Replacement\n\nIf the information system is damaged or destroyed or the primary site is unavailable, necessary hardware and software will need to be activated or procured quickly and delivered to the alternate location."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.4.4", "cmmc_practice_id": "CM.L2-3.4.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 9)"}, {"role": "assistant", "content": "A special note of thanks to Jim Foti and the NIST web team for their outstanding administrative support. In addition, the authors wish to acknowledge the United States Air Force and the 'RMF Next' initiative, facilitated by Air Force CyberWorx, that provided the inspiration for some of the new ideas in this update to the RMF. The working group, led by Lauren Knausenberger, Bill Bryant, and Venice Goodwine, included government and industry representatives Jake Ames, Chris Bailey, James Barnett, Steve Bogue, Wes Chiu, Kurt Danis, Shane Deichman; Joe Erskine, Terence Goodman, Jason Howe, Brandon Howell, Todd Jacobs, Peter Klabe, William Kramer, Bryon Kroger, Kevin LaSalle, Dinh Le, Noam Liran, Sam Miles, Michael Morrison, Raymond Tom Nagley, Wendy Nather, Jasmine Neal, Ryan Perry, Eugene Peterson, Lawrence Rampaul, Jessica Rheinschmidt, Greg Roman, Susanna Scarveles, Justin Schoenthal, Christian Sorenson, Stacy Studstill, Charles Wade, Shawn Whitney, David Wilcox, and Thomas Woodring. Finally, the authors also gratefully acknowledge the significant contributions from individuals and organizations in both the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. ## HISTORICAL CONTRIBUTIONS TO NIST SPECIAL PUBLICATION 800-37\n\nThe authors acknowledge the many individuals who contributed to previous versions of Special Publication 800-37 since its inception in 2005. They include Marshall Abrams, William Barker, Beckie Koonge, Roger Caslow, John Gilligan, Peter Gouldmann, Richard Graubart, John Grimes, Gus Guissanie, Priscilla Guthrie, Jennifer Fabius, Cita Furlani, Richard Hale, Peggy Himes, William Hunteman, Arnold Johnson, Donald Jones, Stuart Katzke, Eustace King, Mark Morrison, Sherrill Nicely, Karen Quigg, George Rogers, Cheryl Roby, Gary Stoneburner, Marianne Swanson, Glenda Turner, and Peter Williams."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.1.2 | Test Results... 3.1.2 Test Results\n\nFigure D-31 shows the remote connection being established through the Cisco AnyConnect VPN application through which a browser is used to access the ConsoleWorks web interface (Figure D-32). 3.1.24\n-  PI Interface for SNMP ReadOnly version 1."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n## Guidelines for Media Sanitization\n\n## Guidelines for Media Sanitization\n\nChandramouli R, Hibbard EA (2025) Guidelines for Media Sanitization. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-88r2. https://doi.org/10.6028/NIST.SP.800-88r2"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 4)"}, {"role": "assistant", "content": "le voice communication and text messaging capabilities. This guide also discusses procedures for the validation, preservation, acquisition, examination, analysis, and reporting of digital information.\n## Keywords\n\ncell phone forensics; forensic tools; mobile devices; mobile device forensics; mobile device tools; smart phones\n\n## Acknowledgements\n\nThe authors, Rick Ayers from NIST, Sam Brothers from U.S. Customs and Border Protection and Wayne Jansen from Booz-Allen-Hamilton, wish to thank colleagues who reviewed drafts of this document. In particular, our appreciation goes to Barbara Guttman from NIST and Simson Garfinkle from the Naval Postgraduate School for their technical support and written contributions to this document. Our appreciation also goes out to Bob Elder from TeelTech Canada, Gary Kessler from Gary Kessler Associates, Rick Mislan from Rochester Institute of Technology and Daren Melson for their assistance on technical issues that arose in our work. The authors would also like to thank all others who assisted with our review process."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.3.2. 3.3.2. 3.3.2."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nne or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control.\n- Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## 3.3. Analyze Stages of Hardware Development Life Cycle for Exploitability of the Threat"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n| Executive Summary....................................................................................................................1 | Executive Summary....................................................................................................................1 | Executive Summary....................................................................................................................1 | |------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| | Introduction .........................................................................................................................2 | Introduction .........................................................................................................................2 | | | Structural Implications of Drivers on the Enterprise Network Landscape .....................2 | Structural Implications of Drivers on the Enterprise Network Landscape .....................2 | | | Security Implications of Drivers on the Enterprise Network Landscape........................3 | Security Implications of Drivers on the Enterprise Network Landscape........................3 | | | The Need for a Security Guide......................................................................................3 | The Need for a Security Guide......................................................................................3 | | | Scope............................................................................................................................4 | Scope............................................................................................................................4 | | | Target Audience............................................................................................................4 | Target Audience............................................................................................................4 | | | Organization of This Document.....................................................................................4 | Organization of This Document.....................................................................................4 | | | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | Traditional Enterprise Network Access Approaches and Their Limitations .................5 | | Limitations of Network Perimeter-based Protections ....................................................5 | Limitations of Network Perimeter-based Protections ....................................................5 | | | Limitations of VPN-based Access .................................................................................5 | Limitations of VPN-based Access .................................................................................5 | | | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 | 2.3 Limitation of MPLS Technology as Enterprise WANs.............................................................6 | | 2.4 Limitation of"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 10)"}, {"role": "assistant", "content": "| Shortcomings of Identity-Based Segmentation Policies for Enterprise ZTA ................\n| 9 |\n| | Multi-Tier Policies for Enterprise ZTA ........................................................................."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n.............................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..............................................................................\n8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................. 18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE ...................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n3.5.3 Maintenance Plans for Scenario 3, Emergency Mitigation | ... 3.5.3 Maintenance Plans for Scenario 3, Emergency Mitigation\n\nOrganizations should plan for the quick implementation of multiple types of emergency mitigations to protect vulnerable assets."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Machine Learning for Access Control Policy Verification:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nThe author, Vincent C. Hu of the National Institute of Standards and Technology (NIST), wishes to thank Isabel Van Wyk and Jim Foti (NIST) who reviewed drafts of this document. The author also gratefully acknowledges and appreciates the comments and contributions made by government agencies, private organizations, and individuals in providing direction and assistance in the development of this document."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 8)"}, {"role": "assistant", "content": "ks in CI/CD Pipelines to Recommended High-Level Practices in SSDF..............................................................................................................................26 |\n| B.\nJustification for the Omission of Certain Measures Related to SSDF Practices in This |\n| Appendix |\n\nDocument ........................................................................................................................................ 32\n\n## Acknowledgments\n\nThe authors would like to express their thanks to Isabel Van Wyk of NIST for her detailed editorial review, both for the public comment version as well as for the final publication. ## Executive Summary\n\nCloud-native applications are made up of multiple loosely coupled components called microservices. This class of applications is generally developed through an agile software development life cycle (SDLC) paradigm called DevSecOps, which uses flow processes called Continuous Integration/Continuous Delivery (CI/CD) pipelines. Analyses of recent software attacks and vulnerabilities have led both government and privatesector organizations involved in software development, deployment, and integration to focus on the activities involved in the entire SDLC. This collection of activities constitutes the software supply chain (SSC), and the integrity of the individual activities contributes to the overall security of an SSC. Threats can arise from attack vectors unleashed by malicious actors during SSC activities as well as defects introduced when due diligence practices are not followed by legitimate actors during the SDLC."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Maintenance?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\n| 1. | Government actions to support strengthening IoT cybersecurity need to be coordinated with industry. |\n|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | The use of robust frameworks and the adoption of open standards are crucial for effectively managing risks across heterogeneous environments. |\n| 3 | The dynamic nature of threats requires more context aware inputs, more proactive tracking and mitigation measures, and more examination into the inputs of the threat modeling approach. |\n| 4 | There are market opportunities to securely design the next wave of products with cybersecurity through end of life and instill incentives into the maintenance of existing products. |\n| 5 | The balance of shared responsibility between manufacturers and users for improving security varies by sector and needs the right incentives for both. |\n| 6 | There are broad challenges to integrating privacy objectives into IoT cybersecurity risk management. |\n| 7 | There is an increased awareness for evolving cybersecurity responsibilities across the players of the IoT ecosystem from manufacturers to users of the ecosystem."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n- [1] DARPA (2020) DARPA Selects Teams to Increase Security of Semiconductor Supply Chain. Available at https://www.darpa.mil/news/2020/semiconductor-supply-chainsecurity\n- [2] DARPA (2021) Expanding Domestic Manufacturing of Secure, Custom Chips for Defense Needs. Available at https://www.darpa.mil/news-events/2021-03-18\n- [3] NSWC Crane Corporate Communications (2019) NSWC Crane leverages OTA to ensure that the U.S. Government has access to secure state-of-the-art design, assembly, packaging and test for state-of-the-art microelectronics. Available at https://www.navsea.navy.mil/Media/News/Article/2005099/nswc-crane-leverages-otato-ensure-that-the-us-government-has-access-to-secure/\n- [4] Institute for Systems Research (2020) AFRL-Northrop Grumman: Locked Electronics for Assured Design (LEAD): Delay Locking ASIC IP Blocks to Protect Functionality. Available at https://isr.umd.edu/research-funding/afrl-northrop-grumman-locked-electronicsassured-design-lead-delay-locking-asic-ip\n- [5] Wolfe F (2020) Aether Spy Next-Generation Multi-Function Radar to Advance, Northrop Grumman Says. Defense Daily . Available at https://www.defensedaily.com/aether-spynext-generation-multi-function-radar-advance-northrop-grumman-says/air-force/\n- [6] CISA (2020) Defining Insider Threats. Available at https://www.cisa.gov/topics/physicalsecurity/insider-threat-mitigation/defining-insider-threats\n- [7] Areno M (2020) Supply chain threats against integrated circuits. Intel Whitepaper . Available at https://www.intel.com/content/dam/www/centrallibraries/us/en/documents/2022-08/supply-chain-threats-against-integrated-circuitswhitepaper-july2020.pdf\n- [8] Evernex (2024) EOL Meaning: What Does End of Life Mean for Your Hardware? Available at https://evernex.com/industry-guide/eol-meaning/\n- [9] Vincent J (2018) Chinese spies reportedly inserted microchips into servers used by Apple, Amazon, and others."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\nQuick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)\n\n## NIST CSF 2.0: CYBERSECURITY SUPPLY CHAIN RISK MANAGEMENT (C-SCRM)\n\n## INTRODUCTION TO C-SCRM"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n-  Destructive malware, ransomware, malicious insider activity, and even honest mistakes all set the stage for why organizations need to detect and respond to an event that impacts data integrity. Businesses must be confident that these events are detected in a timely fashion and responded to appropriately.\n-  Attacks against an organization's data can compromise emails, employee records, financial records, and customer information-impacting business operations, revenue, and reputation.\n-  Examples of data integrity attacks include unauthorized insertion, deletion, or modification of data to corporate information such as emails, employee records, financial records, and customer data.\n-  The National Cybersecurity Center of Excellence (NCCoE) at NIST built a laboratory environment to explore methods to effectively detect and respond to a data\n- integrity event in various information technology (IT) enterprise environments, to immediately react to the event in an effort to prevent a complete compromise.\n-  This NIST Cybersecurity Practice Guide demonstrates how organizations can develop and implement appropriate actions during a detected data integrity cybersecurity event.\n\n- event detection\n- integrity monitoring\n- logging\n- reporting\n- mitigation and containment\n- forensics/analytics\n\nRansomware, destructive malware, insider threats, and even honest mistakes present an ongoing threat to organizations that manage data in various forms. Database records and structure, system files, configurations, user files, application code, and customer data are all potential targets of data corruption and destruction."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. These capabilities were developed in the context of NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers [2], which discusses considerations for manufacturers to help guide them in choosing and implementing the device cybersecurity capabilities their IoT devices will provide. NISTIR 8259 also defines terminology and concepts that provide critical context for understanding device cybersecurity capabilities as one part of the entire IoT cybersecurity ecosystem. Thus, though both NISTIR 8259 and this publication have manufacturers as the intended audience, the considerations and capabilities discussed across the two publications can be used by manufacturers, integrators, or consumers."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Media Protection\n\nDescription: Protect system media, both paper and digital; limiting access to data on system media to authorized users; and sanitizing or destroying system media before disposal or release for reuse."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.2.2 Scenario 2: | Verification of Components During Acceptance Testing... 3.2.2 Scenario 2: Verification of Components During Acceptance Testing\n\nIn this scenario, an IT administrator receives a computing device through non-verifiable channels (e. 3.2.2 | Dashboards..."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/171/a/r3/final, including related content, potential updates, and document history.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.02.01.ODP[01]: the frequency at which to provide security literacy training to system users after initial training is defined . A.03.02.01.ODP[02]: events that require security literacy training for system users are defined. A.03.02.01.ODP[03]: the frequency at which to update security literacy training content is defined. A.03.02.01.ODP[04]: events that require security literacy training content updates are defined. A.03.02.01.a.01[01]: security literacy training is provided to system users as part of initial training for new users. security literacy training is provided to system users"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| GV.SC-05 | Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties | Medium | R1: Cybersecurity supply chain risk management requirements should include cybersecurity performance and vulnerability, threat, and incident disclosure and information sharing."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n7 |\n| | | 3.2.2 Scenario 2: | Verification of Components During Acceptance Testing........................... 7 |\n| | | 3.2.3 | Scenario 3: Verification of Components During Use...................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\n## Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs\n\n## Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs\n\nCryptography is an essential component of modern computing. Unfortunately, implementing cryptography correctly is a non-trivial undertaking. Past research studies have supported this observation by revealing a multitude of errors and pitfalls in the cryptographic implementations of software products. However, the emphasis of these studies was on the practices of less-experienced, individual developers. Therefore, there is little understanding of the cryptographic development practices of organizations, including the benefits and challenges of using cryptographic resources such as standards specifications and libraries. To address this gap, a research team led by the National Institute of Standards and Technology (NIST) Information Technology Laboratory Visualization and Usability Group conducted a qualitative investigation into the processes and resources that organizations employ in the development and testing of cryptographic products. The study involved 21 in-depth interviews of 29 participants representing organizations that develop either a security product that uses cryptography or a non-security product that heavily relies on cryptography. This report categorizes and enumerates a subset of findings that document participant comments specific to NIST cryptographic publications and testing/validation programs, with a goal of informing future decisions of NIST and other standards bodies working in this space."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 3)"}, {"role": "assistant", "content": "......................................1 |\n| 2. Background....................................................................................................................................3 |\n| 3.\nPurpose and Uses...........................................................................................................................5 |\n| 4. Equations.......................................................................................................................................8 |\n| 5. Equation Derivation .....................................................................................................................10 |\n| 6. Example Output...........................................................................................................................14 |\n| 7. Empirical Results..........................................................................................................................16 |\n| 9. Performance ................................................................................................................................23 |\n| 10. Implementation and Availability.................................................................................................25 |\n\n| NIST CSWP 41 May 19, 2025 | Likely Exploited Vulnerabilities: A Proposed Metric for Vulnerability Exploitation Probability |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 11."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.1.1 | Required Training Fulfillment | 3 |\n| 3. 3.1.1 Required Training Fulfillment\n\nWe asked participants in what ways their employees could fulfill annual security awareness requirements (Figure 1)."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 6)"}, {"role": "assistant", "content": "## Table of Contents | Executive Summary.....................................................................................................................v | Executive Summary.....................................................................................................................v | |------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | Introduction........................................................................................................................1 | | 2 | Machine Learning for Access Control Verification.........................................................3 | | 3 | RFC Verification Approach ...............................................................................................7 | | 4 | Applications .....................................................................................................................14 | | 5 | Conclusion .......................................................................................................................16 | | References..................................................................................................................................17 | References..................................................................................................................................17 | | List of Figures | List of Figures | | Figure 1: 1a (above), 1b (below) - Subtrees model generated by RFC classifier........................................4 | Figure 1: 1a (above), 1b (below) - Subtrees model generated by RFC classifier........................................4 | | Figure 2: Mapping of access control policy types and verification methods.................................................6 | Figure 2: Mapping of access control policy types and verification methods.................................................6 | | Figure 3: Access control policy rules specified in a data table .....................................................................7 | Figure 3: Access control policy rules specified in a data table .....................................................................7 | | Figure 4: RFC program in Python code ......................................................................................................10 | Figure 4: RFC program in Python code ......................................................................................................10 | | Figure 5: First 28 rendered model rules from RFC subtrees ......................................................................11 | Figure 5: First 28 rendered model rules from RFC subtrees ......................................................................11 | | Figure 6: Machine Learning RFC method for access control policy verification.........................................12 | Figure"}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 3)"}, {"role": "assistant", "content": "described in NIST SP 800-207 and has had exposure to federal information security practices. ## Trademark Information\n\nAll registered trademarks or trademarks belong to their respective organizations.\n## Table of Contents\n\n| 1 | Zero Trust ...............................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|\n| 2 | Getting Started on the Journey.............................................................................4 |\n| | 2.1 The Process...................................................................................................."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| PURPOSEANDAPPLICABILITY ...................................................................................................\n| 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ......................................................................................... | 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS ...................................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nGuide to Auditing for Controls and Security: A System Development Life Cycle Approach ## Guide to Auditing for Controls and Security: A System Development Life Cycle Approach | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | xiii | |-------------------------|------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|--------| | CHAPTER 1 | CHAPTER 1 | CHAPTER 1 | CHAPTER 1 | | | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | 1 | | 1.1 | INTRODUCTION | INTRODUCTION | INTRODUCTION | 1 | | | 1.1.1 | Scope of the Audit Guide | Scope of the Audit Guide | 1 | | | 1.1.2 | How to Use the Audit Guide | How to Use the Audit Guide | 2 | | | 1.1.3 | Auditor Skills Needed | Auditor Skills Needed | 2 | | | 1.1.4 | Auditing in a Computerized Environment | Auditing in a Computerized Environment | 3 | | | 1.1.4.1 | 1.1.4.1 | The Need | 3 | | | 1.1.4.2 | 1.1.4.2 | The Scope of Audit in a Computerized Environment | 3 | | | 1.1.4.3 | 1.1.4.3 | Relationship Between Systems Development Audits and | | |"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 2)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2022-11-10\n\n## How to Cite this NIST Technical Series Publication:\n\nChandramouli R (2022) Guide to a Secure Enterprise Network Landscape."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide?"}, {"role": "assistant", "content": "## Summary of NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations\n\nKelley Dempsey Computer Security Division Information Technology Laboratory\n\nGreg Witte Doug Rike G2, Inc. Annapolis Junction, MD\n\nFebruary 19, 2014\n\n\n\n## Abstract\n\nThis 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\n\nassurance; computer security; FIPS Publication 199; FIPS Publication 200, FISMA; Privacy Act; Risk Management Framework; security controls; security requirements\n\n## Disclaimer\n\nAny 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\n\nFor 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": ". 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nThe authors wanted to acknowledge the many individuals who contributed to previous versions of Special\nPublication 800-53A since its inception in 2005.\nThey include Marshall Abrams, Dennis Bailey, Matt\nBarrett, Nadya Bartol, Frank Belz, Paul Bicknell, Deb Bodeau, Brett Burley, Bill Burr, Dawn Cappelli,\nCorinne Castanza, Matt Coose, George Dinolt, Donna Dodson, Randy Easter, Kurt Eleam, Jennifer Fabius,\nDaniel Faigin, Denise Farrar, Harriett Goldman, Peter Gouldmann, Richard Graubart, Jennifer Guild,\nSarbari Gupta, Peggy Himes, Bennett Hodge, Cynthia Irvina, Arnold Johnson, Roger Johnson, Lisa Kaiser,\nStu Katzke, Sharon Keller, Cass Kelly, Steve LaFountain, Steve Lipner, Bill MacGregor, Tom Macklin, Tom\nMadden, Erika McCallister, Tim McChesney, Michael McEvilley, John Mildner, Sandra Miravalle, Joji\nMontelibano, Doug Montgomery, George Moore, Harvey Newstrom, Robert Niemeyer, LouAnna\nNotargiacomo, Dorian Pappas, Tim Polk, Esten Porter, Karen Quigg, Steve Quinn, Ed Roback, George\nRogers, Scott Rose, Mike Rubin, Karen Scarfone, Roger Schell, Matt Scholl, Murugiah Souppaya, Kevin\nStine, Gary Stoneburner, Keith Stouffer, Marianne Swanson, Pat Toth, Glenda Turner, Joe Weiss, Richard\nWilsher, Mark Wilson, John Woodward, and Carol Woody. iv\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nNIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nDocument Conventions\n\nFor the purposes of this document, the term “security and privacy” is universally used since the\nguidance is applicable to both security and privacy control assessments. For certain systems,\nhowever, the guidance may only be relevant for security or privacy."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n1.3.1. Security, Fraud, and Threat Prevention . . . . . . . . . . . . . .\n\n3.4.1. Assess Privacy, Customer Experience, and Threat Resistance . . .\n\nDigital identity risks are dynamic and exist along a continuum. Consequently, a digital\nidentity risk management approach should seek to manage risks using outcome-based\napproaches that are designed to meet the organization’s unique needs. These guidelines\ndefine specific assurance levels that operate as baseline control sets. These assurance\nlevels provide multiple benefits, including a starting point for organizations in their\nrisk management journey and a common structure for supporting interoperability\nbetween different entities. It is, however, impractical to create assurance levels that\ncan comprehensively address the entire spectrum of risks, threats, or considerations\nthat an organization will face when deploying an identity solution. For this reason, these\nguidelines promote a risk-based approach to digital identity solution implementation\nrather than a compliance-oriented approach, and organizations are encouraged to tailor\ntheir control implementations based on the processes defined in these guidelines."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nesses at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems.\n- Facilitates the categorization of information and systems, the selection, implementation, assessment, and monitoring of controls, and the authorization of information systems and common controls; 11\n- Promotes the use of automation for near real-time risk management and ongoing system and control authorization through the implementation of continuous monitoring processes;\n- Encourages the use of correct and timely metrics to provide senior leaders and managers with the necessary information to make cost-effective, risk-based decisions for information systems supporting their missions and business functions;\n- Facilitates the integration of security and privacy requirements 12 and controls into enterprise architecture, 13 SDLC, acquisition processes, and systems engineering processes;\n- Connects risk management processes at the organization and mission/business process levels to risk management processes at the information system level through a senior accountable official for risk management and risk executive (function); 14 and\n- Establishes responsibility and accountability for controls implemented within information systems and inherited by those systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements\n\nNIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-01-30\n\nSupersedes NIST SP 800-66r1 (October 2008) https://doi.org/10.6028/NIST.SP.800-66r1\n\n## How to Cite this NIST Technical Series Publication\n\nMarron J (2024) Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-66r2. https://doi.org/10.6028/NIST.SP.800-66r2\n\n## Author ORCID iDs\n\nJeffrey A. Marron: 0000-0002-7871-683X\n\n## Contact Information\n\nsp800-66-comments@nist.gov\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/66/r2/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe HIPAA Security Rule focuses on safeguarding electronic protected health information (ePHI) held or maintained by regulated entities. The ePHI that a regulated entity creates, receives, maintains, or transmits must be protected against reasonably anticipated threats, hazards, and impermissible uses and/or disclosures. This publication provides practical guidance and resources that can be used by regulated entities of all sizes to safeguard ePHI and better understand the security concepts discussed in the HIPAA Security Rule."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 3)"}, {"role": "assistant", "content": "NIST Software Identification and SCAP can be found at https://csrc.nist.gov/projects/Software-Identification-SWID and https://csrc.nist.gov/projects/security-content-automation-protocol respectively.\n## Table of Contents\n\n| 1 | Introduction ............................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| 2 Gaps in SCAP | v1....................................................................................................2 |\n| 3 SCAP | v2..................................................................................................................3 |\n| 3.1 Design Goals for SCAP v2.............................................................................. | 3 |\n| 3.2 The SCAP v2 | Architecture.............................................................................. 4 |\n| 3.3 Adoption of International Standards | in SCAP v2 ............................................"}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\nLEV accuracy is dependent upon EPSS performance because LEV is calculated from historical EPSS scores. EPSS has published testing indicating that the latest version has a high performance in recall (i.e., coverage) and precision (i.e., efficiency), see Sec. 9. As EPSS performance improves over time (which it is has done significantly over the three versions), LEV performance will improve.\n\nEPSS is used by organizations to prioritize the remediation of vulnerabilities along with patch testing and application. The goal is to remediate vulnerabilities that are most likely to be exploited within the next 30 days. One approach is to specify a probability threshold and remediate all vulnerabilities above that threshold (starting with the most probable)."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "..........................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16.\nPersonnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23. Organization-Defined Parameters ............................................................................................106 |\n| Table 24. Change Log................................................................................................................................110 |\n\n## Acknowledgments\n\nThe authors gratefully acknowledge and appreciate the significant contributions from individuals and organizations in the public and private sectors whose constructive comments improved the overall quality, thoroughness, and usefulness of this publication."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy.\n\nThe criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n| Selected CSF Outcomes | Target Priority | Target Internal Practices | Selected Informative References |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|\n| PR.PS, The hardware, software (e.g., firmware, operating systems, applications), and services of physical and virtual platforms are managed consistent with the organization's risk strategy to protect their confidentiality, integrity, and availability | High | 1. Configure platforms to allow the installation of organization-approved software only. 2. Verify the source of new software and the software's integrity before installing it. 3. Configure platforms to use only approved DNS services that block access to known malicious domains. 4. ..."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.3.1 | Configuration... 3.3.1 Configuration\n\n-  Remote Access: Cisco VPN\n- Configured to allow authorized VPN users to access to ConsoleWorks web interface. 3.3.1 eyeInspect\n\n1."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\n| CLASS | FAMILY | IDENTIFIER |\n|-------------|--------------------------------------------------------|--------------|\n| Management | Risk Assessment | RA |\n| Management | Planning | PL |\n| Management | System and Services Acquisition | SA |\n| Management | Certification, Accreditation, and Security Assessments | CA |\n| Operational | Personnel Security | PS |\n| Operational | Physical and Environmental Protection | PE |\n| Operational | Contingency Planning | CP |\n| Operational | Configuration Management | CM |\n| Operational | Maintenance | MA |\n| Operational | System and Information Integrity | SI |\n| Operational | Media Protection | MP |\n| Operational | Incident Response | IR |\n| Operational | Awareness and Training | AT |\n| Technical | Identification and Authentication | IA |\n| Technical | Access Control | AC |\n| Technical | Audit and Accountability | AU |\n| Technical | System and Communications Protection | SC |\n\n| Technical Controls [NIST SP 800- 18] | The security controls (i.e., safeguards or countermeasures) for an information system that are primarily implemented and executed by the information system through mechanisms contained in the hardware, software, or firmware components of the system."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.1.\n\n3.3.1. Privacy Risk Assessment . . . . . . . . . . . . . . . . . . . . . .\n\n4.3.1. Proofing Types . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 5)"}, {"role": "assistant", "content": ".................................................................. 1 | 1. Introduction..............................................................................................................\n1 |\n|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 2. Scope and Purpose ................................................................................................. | 2. Scope and Purpose ................................................................................................. | 2. Scope and Purpose ................................................................................................. | 1 |\n| 3. Definitions, Symbols and Abbreviations ............................................................... | 3. Definitions, Symbols and Abbreviations ............................................................... | 3. Definitions, Symbols and Abbreviations ..............................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.7 (NIST 3.1.7)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.7. 3.1.7."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.7", "cmmc_practice_id": "AC.L2-3.1.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n|\n| Intel | HP Inc.\nElitebook 360 830 G5, Lenovo ThinkPad T480, Transparent Supply Chain Tools, Key Generation Facility, Cloud Based Storage, TSCVerify and AutoVerify software tools |\n| National Security Agency (NSA) | Host Integrity at Runtime and Start-Up (HIRS), Subject Matter Expertise |\n| Seagate Government Solutions | (3) 18TB Exos X18 hard drives, 2U12 Enclosure, Firmware Attestation API, Secure Device Authentication API |"}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.5.3 Other Considerations\n\nThis use case highlights the need for a response-oriented build to collaborate with an identify-oriented build."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\n## Overview and Considerations of Access Control Based on Attribute Encryption\n\n## Overview and Considerations of Access Control Based on Attribute Encryption\n\nHu VC (2023) Overview and Considerations of Access Control Based on Attribute Encryption. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8450-upd1, Includes updates as of December 20, 2023. https://doi.org/10.6028/NIST.IR.8450-upd1"}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 4)"}, {"role": "assistant", "content": "a goal of achieving long-term behavior changes. Security awareness professionals are individuals who are tasked with managing and executing the security awareness programs within their organizations.\nPrior industry surveys and research studies have identified challenges security awareness professionals face. Many members of security awareness teams perform security awareness duties on a part-time basis without a job title that reflects their duties, and they may lack sufficient professional skills (e.g., communications, relationship-building) that were viewed as essential in security awareness roles. In addition, the lack of understanding that security awareness is a unique discipline may lead to ill-prepared awareness professionals. However, it is unclear if these challenges also apply to security awareness professionals in the United States (U.S.) government. To better understand the needs, challenges, practices, and necessary competencies of federal security awareness teams and programs, we conducted a 'mixed methods' research study that leveraged both qualitative and quantitative methodologies. We first conducted eight focus groups of federal employees who had security awareness duties or were managers or executives who oversaw the programs within their organizations. The focus groups then informed an online survey completed by 96 federal employees with security awareness responsibilities. The research background and methodologies for these two phases are described in detail in NISTIR 8420 'Federal Cybersecurity Awareness Programs: A Mixed Methods Research Study.' This companion document reports on a subset of results focused on identifying the current job classifications, security awareness roles, and desired knowledge and skills for security awareness professionals within the federal government. The following is a high-level overview of these results, with statistics from the survey unless otherwise indicated."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nEnterprises that conduct proactive traffic assessments can use these traffic assessments as a baseline for comparison of the attributes of the traffic being monitored against their forward-looking expectations for cybersecurity. The compliance and hygiene scenario shows how to verify that the observed traffic profile complies with current cybersecurity standards and objecti ves. This includes verifying that updates are implemented according to enterprise policies and detecting instances where disallowed secu rity components, outdated protocols, systems, hardware, or software versions are in use."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nPairs for Key Establishment .......................................................... | 6.2 Criteria for RSA Key Pairs for Key Establishment ..........................................................\n| 37 |\n| | 6.2.1 | Definition of a Key Pair ......................................................................................... | 37 |\n| | 6.2.2 | Formats................................................................................................................... | 37 |\n| 6.3 RSA Key-Pair Generators................................................................................................. | 6.3 RSA Key-Pair Generators................................................................................................. | 6.3 RSA Key-Pair Generators................................................................................................. | 38 |\n| | 6.3.1 | RSAKPG1 Family: RSA Key-Pair Generation with a Fixed Public Exponent ....."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "ibed in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs.\nOrganizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control. - Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities. ## 4 Documenting the Control Selection Process\n\nTo aid in review activities, security planning, and risk assessments, organizations document the relevant decisions taken during the security control selection process, providing a sound rationale for those decisions. This documentation is essential when examining the security considerations for organizational information systems with respect to the potential impact on an organization's mission and business."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\n12 This may include the ability to communicate with product components that cannot implement the Data Protection capability the same way as other components (e.g., cannot support adequate cryptography). Any such communications (e.g., data transmitted with sub-par or limited protection)should still be performed in a way that reduces the subsequent risk, such as short-range and/or local network transmission protocol (e.g., Zigbee, Bluetooth) to communicate with some product components in limited, but necessary, circumstances."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide?"}, {"role": "assistant", "content": "\n\n## NIST Internal Report NIST IR 8523\n\n## Multi-Factor Authentication for Criminal Justice Information Systems\n\nImplementation Considerations for Protecting Criminal Justice Information\n\nWilliam Fisher Jason Ajmo Sudhi Umarji Spike E. Dog Mark Russell\n\nKaren Scarfone\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8523\n\n\n\n## NIST Internal Report NIST IR 8523\n\n## Multi-Factor Authentication for Criminal Justice Information Systems\n\nImplementation Considerations for Protecting Criminal Justice Information\n\nWilliam Fisher\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nJason Ajmo Sudhi Umarji Spike E. Dog\n\nThe MITRE Corporation\n\nMark Russell Appian Logic\n\nKaren Scarfone Scarfone Cybersecurity\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8523\n\nSeptember 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nNational Institute of Standards and Technology Craig Burkhardt, Acting Under Secretary of Commerce for Standards and Technology and Acting NIST Director\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\nThe National Bureau of Standards' was established by an act ot Congress on 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 promote public safety. The Bureau's technical work is performed by the National Measurement Laboratory, the National Engineering Laboratory, and the Institute for Computer Sciences and Technology.\n\nTHE NATIONAL MEASUREMENT LABORATORY provides the national system of physical and chemical and materials measurement; coordinates the system with measurement systems of other nations and furnishes essential services leading to accurate and uniform physical and chemical measurement throughout the Nation's scientific community, industry, and commerce; conducts materials research leading to improved methods of measurement, standards, and data on the properties of materials needed by industry, commerce, educational institutions, and Government; provides advisory and research services to other Government agencies; develops, produces, and distributes Standard Reference Materials; and provides calibration services. The Laboratory consists of the following centers:\n\nAbsolute Physical Quantities' - Radiation Research - Thermodynamics and Molecular Science - Analytical Chemistry - Materials Science."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.5 (NIST 3.1.5)?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n3.1.5. 3.1.5."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "nist_control": "3.1.5", "cmmc_practice_id": "AC.L2-3.1.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nInformation technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .\nISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.2.1 | Configuration... 3.2.1 Configuration\n\n-  Remote Access, User Authentication/User Authorization: Dispel\n- Dispel VDI is configured to allow authorized users to access PCS environment through the Dispel Enclave to the Dispel Wicket. 3.2.1 eyeInspect\n\neyeInspect is an appliance hosted on a Dell Embedded Box PC 5000."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 10)"}, {"role": "assistant", "content": "Trust Network Access (ZTNA) 17 | | 5.1 Microsegmentation................................................................................................................17 | 5.1 Microsegmentation................................................................................................................17 | 5.1 Microsegmentation................................................................................................................17 | | 5.1.1 | Prerequisites for Implementing Microsegmentation ....................................................18 | | | 5.1.2 | Microsegmentation - Implementation Approaches .....................................................19 | | | 5.2 Software-defined Perimeter (SDP) .......................................................................................21 | 5.2 Software-defined Perimeter (SDP) .......................................................................................21 | | | Network | Secure Wide Area Network Infrastructure for an Enterprise | .........................23 | | | Common Requirements for a Secure SD-WAN..........................................................23 | |---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| | | Specific Requirements for SD-WANs for Cloud Access..............................................24 | | | Requirements for an Integrated Security Services Architecture for SD-WAN.............26 | | | Summary and Conclusions..............................................................................................28 | | List of Figures | List of Figures | | Fig."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 3)"}, {"role": "assistant", "content": "10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-171Ar3. https://doi.org/10.6028/NIST.SP.800-171Ar3\n\n## Author ORCID iDs\n\nRon Ross: 0000-0002-1099-9757 Victoria Pillitteri: 0000-0002-7446-7506\n\n## Submit Comments\n\n## 800-171comments@list.nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/171/a/r3/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe protection of Controlled Unclassified Information (CUI) is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides organizations with assessment procedures and a methodology that can be used to conduct assessments of the security requirements in NIST Special Publication 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The assessment procedures are flexible and can be customized to the needs of organizations and assessors. Assessments can be conducted as independent, third-party assessments or as government-sponsored assessments. The assessments can be applied with various degrees of rigor based on customer-defined depth and coverage attributes."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n- Govern, Identify, and Protect help organizations prevent some incidents, prepare to handle incidents that do occur, reduce the impact of those incidents, and improve incident response and cybersecurity risk management practices based on lessons learned from those incidents. - Detect, Respond, and Recover help organizations discover, manage, prioritize, contain, eradicate, and recover from cybersecurity incidents, as well as perform incident reporting, notification, and other incident-related communications. - Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state\n\nAll six Functions have vital roles in incident response. Govern, Identify, and Protect help organizations prevent some incidents, prepare to handle incidents that do occur, reduce the impact of those incidents, and improve incident response and cybersecurity risk management practices based on lessons learned."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ..................................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nsential for patient safety in emergency conditions from patient personally identifiable information/data to allow different authentication and access control mechanisms to apply to each group of data.\nAlternately, identifying different modes of operation (such as home health setting versus open environment versus emergency situation) to allow the IMD to apply different authentication and access control mechanisms in different modes."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n...... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................\n5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 6)"}, {"role": "assistant", "content": ". The roles are described in NIST SP 800-207, but are summarized below:\n\n- Policy Engine (PE): The 'brain' of a ZTA implementation and the components that ultimately evaluate resource access requests.\nThe PE relies on information from the various data sources (access logs, threat intelligence, endpoint health, and network ID authentication, etc.)\n- Policy Administrator (PA): The executor function of the PE. The PA's role is to establish, maintain and ultimately terminate sessions 1 in the data plane between the subject and the resource. The PA, PE and PEP communicate on a logically (or physically) separate set of channels called the control plane. The control plane is used to establish and configure the data plane channels used to send application traffic. - Policy Enforcement Point (PEP): The component that applications, endpoints, etc. will interact with to be granted access permission to a resource. The PEP is responsible for gathering information for the PE and following the instructions issued by the PA to establish and terminate communication sessions. All data plane communications between enterprise resources must be managed by a PEP. - Information feeds (left and right ): Sometimes called policy information points (PIPs). These are not 'core' functional ZTA components themselves but used to support the PE. These feeds include the set of codified policies, identity and endpoint attributes, environmental factors and historical data used by the PE to generate resource access decisions. ## 1.1 Tenets of Zero Trust\n\nZero trust could be summarized as a set of principles (or tenets) used to plan and implement an IT architecture. The tenets below were originally defined in NIST SP 800-207 [1] but are repeated and expanded upon here and grouped as relating to network identity, endpoint health, or data flows. Some discussion of the tenets is included, and some considerations that planners should keep in mind when developing a zero trust architecture."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n3.1.3. 3.1.3."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 9)"}, {"role": "assistant", "content": "://www.nist.gov. ## NIST CYBERSECURITY PRACTICE GUIDES\n\nNIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors.\nThey are practical, user-friendly guides that facilitate the adoption of standards-based approaches to cybersecurity. They show members of the information security community how to implement example solutions that help them align with relevant standards and best practices, and provide users with the materials lists, configuration files, and other information they need to implement a similar approach. The documents in this series describe example implementations of cybersecurity practices that businesses and other organizations may voluntarily adopt. These documents do not describe regulations or mandatory practices, nor do they carry statutory authority. ## ABSTRACT\n\nRansomware, destructive malware, insider threats, and even honest mistakes present an ongoing threat to organizations that manage data in various forms. Database records and structure, system files, configurations, user files, application code, and customer data are all potential targets of data corruption and destruction. A timely, accurate, and thorough detection and response to a loss of data integrity can save an organization time, money, and headaches. While human knowledge and expertise is an essential component of these tasks, the right tools and preparation are essential to minimizing downtime and\n\nlosses due to data integrity events. The NCCoE, in collaboration with members of the business community and vendors of cybersecurity solutions, has built an example solution to address these data integrity challenges. This project details methods and potential tool sets that can detect, mitigate, and contain data integrity events in the components of an enterprise network. It also identifies tools and strategies to aid in a security team's response to such an event."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.4.1 Antivirus Software | ... 3.4.1 Antivirus Software\n\nAntivirus software is the most commonly used technical control for malware threat mitigation."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 3)"}, {"role": "assistant", "content": "er statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official.\nThis publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-02-02. ## How to Cite this NIST Technical Series Publication:\n\nGuo Y, Chandramouli R, Wofford L, Gregg R, Key G, Clark A, Hinton C, Prout A, Reuther A, Adamson R, Warren A, Bangalore P, Deumens E, Farkas C (2024) High-Performance Computing Security: Architecture, Threat Analysis, and Security Posture. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-223. https://doi.org/10.6028/NIST.SP.800-223\n\nNIST SP 800-223 February 2024\n\n## Author ORCID iDs\n\nYang Guo: 0000-0002-3245-3069\n\nRamaswamy Chandramouli: 0000-0002-7387-5858\n\nLowell Wofford: 0000-0003-1003-5090\n\nCatherine Hinton: 0000-0002-5230-2428\n\nAlbert Reuther: 0000-0002-3168-3663\n\nAron Warren: 0000-0002-5090-2198\n\nPurushotham Bangalore: 0000-0002-1098-9997\n\nErik Deumens: 0000-0002-7398-3090\n\n## Contact Information\n\nsp800-223-comments@list.nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/223/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA)."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.11 (NIST 3.1.11)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.11. 3.1.11."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.11", "cmmc_practice_id": "AC.L2-3.1.11", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.5.1. Evaluation Inputs . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n2. Continuous improvement programs. Establishing a continuous evaluation\n\nReaders of this guideline should take a holistic approach to considering the interactions\nthat each user will engage in throughout the process of enrolling in and authenticating\nto a service. Throughout the design and development of a digital identity system or\nprocess, it is important to conduct usability evaluations with representative users\nand perform realistic scenarios and tasks in appropriate contexts of use. Additionally,\nfollowing usability guidelines and considerations can help organizations meet their\ncustomer experience goals. Digital identity management processes should be designed\nand implemented so that it is easy for users to do the right thing, hard to do the wrong\nthing, and easy to recover when the wrong thing happens."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 3)"}, {"role": "assistant", "content": "us Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Internal Report (IR) NIST IR 8545.\nhttps://doi.org/10.6028/NIST.IR.8545\n\n## Author ORCID iDs\n\nGorjan Alagic:\n\n0000-0002-0107-6037\n\nMaxime Bros:\n\n0000-0001-7838-2529\n\nPierre Ciadoux:\n\n0009-0001-2272-681X\n\nDavid Cooper:\n\n0009-0001-2410-5830\n\nQuynh Dang:\n\n0009-0005-9801-6805\n\nThinh Dang:\n\n0000-0001-9705-0925\n\nJohn Kelsey:\n\n0000-0002-3427-1744\n\nJacob Lichtinger:\n\n0000-0003-2407-5309\n\nYi-Kai Liu:\n\n0000-0001-7458-4721\n\nCarl Miller:\n\n0000-0003-1917-1531\n\nDustin Moody:\n\n0000-0002-4868-6684\n\nRene Peralta:\n\n0000-0002-2318-7563\n\nRay Perlner:\n\n0000-0001-8793-2238\n\nAngela Robinson:\n\n0000-0002-1209-0379\n\nHamilton Silberg:\n\n0009-0004-4178-8954\n\nDaniel Smith-Tone:\n\n0000-0002-7995-8734\n\nNoah Waller:\n\n0000-0002-6979-9725\n\n## Contact Information\n\npqc-comments@nist.gov\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8545/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nNIST is selecting public-key cryptographic algorithms through a public, competition-like process to specify additional digital signature, public-key encryption, and key-establishment algorithms to supplement FIPS 186-5, SP 800-56Ar3, and SP 800-56Br2. These algorithms are intended to protect sensitive information well into the foreseeable future, including after the advent of quantum computers. In the fourth round of the Post-Quantum Cryptography Standardization Process, NIST selected four candidate algorithms for key establishment to be studied: BIKE, Classic McEliece, HQC, and SIKE. This report describes the evaluation and selection process of these fourth-round candidates based on public feedback and internal review."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 8)"}, {"role": "assistant", "content": "| ....................................................................................................\n4 |\n| mSCP Components.......................................................................................................... | mSCP Components.......................................................................................................... | 6 |\n| | Baselines and Benchmarks | ........................................................................................ 6 |\n| | Security Baseline Files | ............................................................................................... 6 |\n| 3.2.1. | Rule File Composition............................................................................................. | 7 |\n| 3.2.2. | Rule File Categories | ..............................................................................................."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nA majority of survey participants believe employees understand the relevance of RBT and are supportive of the program. Clear communications about why RBT is relevant to employee work roles is critical for garnering this support. Although most also thought that leadership was supportive of RBT activities, a perceived lack of funding and staff does not reflect this support."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\n- Endpoint Applicability Language: Security and operations personnel need to know if a vulnerability or set of configuration settings apply to their networks. To do this, they need to map their knowledge of the software installed on Endpoints to vulnerability reports and configuration checklists. In SCAP v1, the CPE Applicability Language [11] is used to associate software and hardware products with a vulnerability or configuration setting information. If software inventory of endpoints is reported using SWID tag information, the CPE Applicability Language needs to be replaced with an applicability language that can match against the larger set of information provided by SWID tags. Development of this applicability language is currently underway and is expected to be published as a NIST Internal Report once the initial draft is complete. Once completed, the applicability language will be piloted as part of the National Vulnerability Database (NVD) vulnerability feeds. 1\n- ROLIE Extensions: ROLIE, defined by RFC8322 [8] provides a standardized method to easily identify and retrieve vulnerability records, SWID tags, configuration setting checklists, and other security content to support vulnerability and configuration setting assessment. ROLIE provides a content syndication approach that allows software creators, vulnerability reporters, and configuration setting checklist developers to establish federated repositories of the security content they produce. While ROLIE standardizes the repository communication protocol, each class of information ROLIE serves requires a ROLIE extension to define how the information is indexed and supported. Extensions to ROLIE to support SWID tag [12], vulnerability, checklist, and incident [13] information are currently being developed in the IETF Managed Incident Lightweight Exchange (MILE) [14] and the IETF Security Automation and Continuous Monitoring (SACM) [15] working groups."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nProfessional Backgrounds, Knowledge, Skills, and Development Activities\n\nProfessional Backgrounds, Knowledge, Skills, and Development Activities\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThese activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle. traceability tools. This assurance is needed early, while the chips are inexpensive. The payoff is Semiconductor manufacturing harvests a significant amount of data. Jeremy stated that Global Foundries accumulated about 12 terabytes of data per day. There must be an analytic environment to take advantage of these data through an 'observe, orient, decide, and act' (OODA) loop to develop assurance and awareness capabilities (e.g., supply chain and digitaltwins capabilities) and support the stress testing of manufacturing supply disruptions (e.g., the 2008 financial crisis bank stress testing). This would enable the transition from a trust framework of people watching people make assessments to using digital twins to model sensors and data to monitor the supply chain in a manner that creates value by establishing provenance and traceability. Andrew Seward introduced the Semiconductor Manufacturing Cybersecurity Consortium (SMCC) efforts that Semiconductor Equipment and Materials International (SEMI) is implementing. SEMI is an international organization that has focused on the semiconductor industry since 1970 and provides global advocacy and technical leadership. It currently meets the cybersecurity needs of the industry, from material and equipment suppliers to end users."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 10)"}, {"role": "assistant", "content": "ributed at the Workshop 3.3 Reading the Report 3.4 References | 3.2 Materials Distributed at the Workshop 3.3 Reading the Report 3.4 References | |\n| PART II: 1.\n| INTRODUCTION CaiPUTERS HAVE BROUGHT NEED FOR SECURITY CONTROLS | KEYNOTE ADDRESS 7 | 2-1 2-2 |\n| 2. | 2.1 Old Controls are Obsolete New | 2.1 Old Controls are Obsolete New | 2-2 2-3 |\n| | 2.2 Controls Are Needed OF THIS WORKSHOP | 2.2 Controls Are Needed OF THIS WORKSHOP | 2-3 |\n| 3."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nThere are references in this publication to documents currently under development by NIST in accordance with responsibilities assigned to NIST under the Federal Information Security Management Act of 2002. The methodologies in this document may be used even before the completion of such companion documents. Thus, until such time as each document is completed, current requirements, guidelines, and procedures (where they exist) remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new documents by NIST. Individuals are also encouraged to review the public draft documents and offer their comments to NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in federal computer systems. This Special Publication 800-series reports on ITL's research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. The authors, Marianne Swanson and Pauline Bowen of the National Institute of Standards and Technology (NIST), Amy Wohl Phillips, Dean Gallup, and David Lynes of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n3.1.2. 3.1.2."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nd security solutions. If availability and operational problems occur , e nterprises that provide these services to customers, partners, and employees need to rapidly troubleshoot and fix these issues.\nOperations troubleshooting scenarios demonstrate the enterprise tracing transactions through all tiers of an application, including the collection of detailed information such as transaction identifiers, data payload, and the results of operations performed by each application tier. Because operational issues can be intermittent and difficult to replicate, troubleshooting scenarios include the ability to proactively collect and view detailed historical data that may or may not appear in logs. Examples of troubleshooting situations include application unavailability and intermittent system failures. Visibility into enterprise elements such as communications for networkattached storage (NAS), identity management systems, databases, routers and switches, application servers, web servers, load balancers, and firewalls can help provide a complete picture of the end-toend session across the enterprise. The troubleshooting scenario includes these elements:"}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nThere may also be some overlap by the security controls within the different families of controls.” to “Many safeguards for mobile devices are reflected in other controls.” Control AC-20 Discussion: Change “organizational systems” to “organizational systems,” Control Enhancement AC-20(3) Discussion: Change “AC-20(6)” to “AC-20 b.” Control AT-1a.1.: Change “organization-level; mission/business process-level; system-level” to “Organization-level; Mission/business process-level; System-level” Control AT-1 Discussion: Change “security or privacy incidents” to “security incidents or breaches” Control AT-2d.: Change “security or privacy incidents” to “security incidents or breaches” Control AT-2 Discussion: Change “security or privacy incidents” to “security incidents or breaches” Control AT-3c.: Change “security or privacy incidents” to “security incidents or breaches” Control AT-3 Discussion: Change “security or privacy incidents” to “security incidents or breaches” Control AT-3 Related Controls: Change “IR-10” to “IR-4” Control AT-6 Discussion: Change “assessment and update” to “evaluation and update” Control AT-6 Discussion: Change “organization training” to “organizational training” Control AU-1a.1.: Change “organization-level; mission/business process-level; system-level” to “Organization-level; Mission/business process-level; System-level” Control AU-1 Discussion: Change “security or privacy incidents” to “security incidents or breaches” Control CA-1a.1.: Change “organization-level; mission/business process-level; system-level” to “Organization-level; Mission/business process-level; System-level” Control CA-1 Discussion: Change “security or privacy incidents” to “security incidents or breaches” Control CA-1"}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\n'We have one annual course, and we've bundled a lot of training requirements in this one course. It's security awareness, privacy, incident response, rules of behavior, all these things in one course.' (S06)\n\n'Logistics and event planning are key KSA [knowledge, skills, and abilities] areas.' (Q56)"}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 7)"}, {"role": "assistant", "content": "IoT Product | .................................................11 | | | Consumer Sector Considerations Used to Create the Profile ......................................17 | Consumer Sector Considerations Used to Create the Profile ......................................17 | | References.................................................................................................................................22 | References.................................................................................................................................22 | | | Appendix A."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\n## · B.2.4 Roles, services, and authentication\n\n- B.2.4 Roles, services, and authentication\n\n- Security Functions Table - The table of all security functions with specific key strengths employed for approved services as well as the implemented modes of operation (e.g. CBC [Cipher Block Chaining], CCM [Counter with Cipher Block Chaining-Messsage Authentication Code]), if appropriate"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Security Assessment?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nprocesses associated with the IoT product, including:\n- i. Steps taken during development to ensure the IoT product and its product components are free of any known, exploitable vulnerabilities. - ii.\nThe process of working with component suppliers and third-party vendors to ensure the security of the IoT product and its product components is maintained for the duration of its supported lifecycle. - iii. Any post end-of-support considerations, such as the discovery of a vulnerability that would significantly impact the security, privacy, or safety of customers who continue to use the IoT product and its product components. - g. The vulnerability management policies and processes associated with the IoT product, including :\n- i. Methods of receiving reports of vulnerabilities (see Information and Query Reception below). - ii. Processes for recording reported vulnerabilities. - iii. Policy for responding to reported vulnerabilities, including the"}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Assessing Security Requirements for Controlled Unclassified Information support CMMC certification?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171Ar3\n\n\n\n## NIST Special Publication\n\n## NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-171Ar3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nAs the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process. The baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems .\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n17 The Audit and Accountability, Maintenance, Media Protection, and Physical Protection families do not contain enhanced security requirements at this time.\n\n## 3.8 MEDIA PROTECTION"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- NSAT-HLM-1: The tools should scale to meet the volume, velocity, and variety of today's application development, deployment, and maintenance paradigms [13]. This requirement is critical in environments where DevSecOps is used to deploy not only applications but also infrastructures, the latter using infrastructure-as-code (IaC) tools. These tools are an integral part of the smart automated workflows called CI/CD pipelines, which invoke them to deploy servers (computing), networking, and storage infrastructure. Hence, this class of network automation tools should have the capability to be seamlessly integrated into the corresponding CI/CD pipelines.\n- NSAT-HLM-2: The tools should have the capability to minimize human intervention for security remediation, which is slow and prone to error. In other words, the more automated remediation features built into the tool, the better.\n- NSAT-HLM-3 (enhanced threat intelligence and protection): The tools should have advanced threat intelligence, real-time threat prevention capabilities for known and zeroday vulnerabilities, and sandboxing features for isolating malicious traffic.\n- NSAT-HLM-4 (leveraging knowledge of previous events): The tools should have features for matching current events to past ones and for leveraging the remediation measures performed for those instances in the current solution. This brings about reduction to the average outage time [14].\n\n- a. Ability to support endpoint devices with different operating systems\n- b. Installation and maintenance of device and service authentication certificates\n- c. Installation and maintenance of device health applications\n- d. Updates of patches on the devices\n- e. Enables admins to track, audit, and report endpoints for content and applications"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Maintenance?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nupdates, such as software updates, algorithm changes, new protocols, or changes in the vendors used by the manufacturer to update cybersecurity, that may impact cybersecurity risks."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n3.2.1 DETERMINE WHICH SECURITY AND PRIVACY CONTROLS ARE TO BE ASSESSED\n\nThe security plan and privacy plan provide an overview of the security and privacy requirements\nfor the system and organization and describe the security controls and privacy controls in place\nor planned for meeting those requirements."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 3)"}, {"role": "assistant", "content": "y core baseline, which is a set of device capabilities generally needed to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems.\nThe purpose of this publication is to provide organizations a starting point to use in identifying the device cybersecurity capabilities for new IoT devices they will manufacture, integrate, or acquire. This publication can be used in conjunction with NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers . ## Keywords\n\ncybersecurity baseline; Internet of Things (IoT); securable computing devices. ## Acknowledgments\n\nThe authors wish to thank all contributors to this publication, including the participants in workshops and other interactive sessions; the individuals and organizations from the public and private sectors, including manufacturers from various sectors as well as several manufacturer trade organizations, who provided feedback on the preliminary essay and the public comment drafts; and colleagues at NIST who offered invaluable inputs and feedback. Special thanks to Cybersecurity for IoT Program team members Barbara Cuthill and Jeff Marron and the NIST FISMA Implementation Project team for their extensive help in copy editing. ## Audience\n\nThe main audience for this publication is IoT device manufacturers. This publication may also help IoT device customers or integrators."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 10)"}, {"role": "assistant", "content": "| |\n| Fig. 1.\nSanitization and disposition decision flow...............................................................................20 | |\n| Fig. 2. Certificate of sanitization .......................................................................................................37 | |\n\n## Acknowledgments\n\nThe authors would like to thank Richard Kissel, Andrew Regenscheid, Matthew Scholl, and Kevin Stine for their work on the original version and the first revision of this publication. The authors would also like to thank Steven Skolochenko and Xing Li for their contributions to the original version of this publication. The authors would also like to thank Jim Foti and Isabel Van Wyk for their exceptional editing skills and thorough review of this document; their work made this a much better document. Thanks to their diligent and detailed reviews, we expect this document to serve as a useful guide for developing an effective media sanitization program. ## Executive Summary\n\nProtecting the confidentiality of information should be a concern for everyone, from federal agencies and businesses to home users. Media disposition and sanitization decisions need to consider the confidentiality obligations associated with recording or storing sensitive information on hard copy media or information storage media (ISM). To help ensure media disposition and sanitization are effective and traceable, consideration should be given to implementing a media sanitization program. The modern storage environment is rapidly evolving."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "Cybersecurity Policy and Partnerships\n\nDirector, Security Coordination Center\n\n## National Institute of Standards and Technology\n\n## Committee on National Security Systems\n\nCharles H. Romine\n\nMark G.\nHakun\n\nDirector, Information Technology Laboratory\n\nChair\n\nKevin Stine\n\nSusan Dorr Co-Chair\n\nActing Cybersecurity Advisor, ITL\n\nMatthew Scholl\n\nKevin Dulany\n\nChief, Computer Security Division\n\nTri-Chair-Defense Community\n\nKevin Stine\n\nChris Johnson\n\nChief, Applied Cybersecurity Division\n\nTri-Chair-Intelligence Community\n\nRon Ross\n\nVicki Michetti\n\nFISMA Implementation Project Leader\n\nTri-Chair-Civil Agencies\n\n## Joint Task Force Working Group\n\n| Victoria Pillitteri | McKay Tolboe | Dorian Pappas | Kelley Dempsey |\n|-----------------------|-----------------------|------------------------|------------------|\n| NIST, JTF Leader | DoD | Intelligence Community | NIST |\n| Ehijele Olumese | Lydia Humphries | Daniel Faigin | Naomi Lefkovitz |\n| The MITRE Corporation | Booz Allen Hamilton | Aerospace Corporation | NIST |\n| Esten Porter | Julie Nethery Snyder | Christina Sames | Christian Enloe |\n| The MITRE Corporation | The MITRE Corporation | The MITRE Corporation | NIST |\n| David Black | Rich Graubart | Peter Duspiva | Kaitlin Boeckl |\n| The MITRE Corporation | The MITRE Corporation | Intelligence Community | NIST |\n| Eduardo Takamura | Ned Goren | Andrew Regenscheid | Jon Boyens |\n| NIST | NIST | NIST | NIST |\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\nIn addition to the above acknowledgments, a special note of thanks goes to Jeff Brewer, Jim Foti, and the NIST web team for their outstanding administrative support."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nExample 5 : Establish and follow processes to address risk when there are security requirements that third-party software components to be acquired do not meet; this should include periodic reviews of all approved exceptions to requirements. | SCAGILE : Tasks Requiring the Help of Security Experts 8 SCFPSSD : Manage Security Risk Inherent in the Use of Third-Party Components SCSIC : Vendor Sourcing Integrity Controls SP80053 : SA-4, SA-9, SA-10, SA-10(1), SA-15, SR-3, SR-4, SR-5 SP800160 : 3.1.1, 3.1.2 SP800161 : SA-4, SA-9, SA-9(1), SA-9(3), SA-10, SA-10(1), SA-15, SR-3, SR-4, SR-5 SP800181 : T0203, T0415; K0039; S0374; A0056, A0161 |\n| Implement Roles and Responsibilities (PO.2) : Ensure that everyone inside and outside of the organization involved in the SDLC is prepared to perform their SDLC-related roles and responsibilities throughout the SDLC. | PO.2.1 : Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed. | Example 1 : Define SDLC-related roles and responsibilities for all members of the software development team. Example 2 : Integrate the security roles into the software development team. Example 3 : Define roles and responsibilities for cybersecurity staff, security champions, project managers and leads, senior management, software developers, software testers, software assurance leads and staff, product owners, operations and platform engineers, and others involved in the SDLC. Example 4 : Conduct an annual review of all roles and responsibilities."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide?"}, {"role": "assistant", "content": "## NIST Special Publication NIST SP 800-40r4\n\n## Guide to Enterprise Patch Management Planning:\n\nPreventive Maintenance for Technology\n\nMurugiah Souppaya Karen Scarfone\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-40r4\n\n\n\n## NIST Special Publication NIST SP 800-40r4\n\n## Guide to Enterprise Patch Management Planning:\n\nPreventive Maintenance for Technology\n\nMurugiah Souppaya Computer Security Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-40r4\n\nApril 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 2)"}, {"role": "assistant", "content": "as normas y directrices no se aplicarán a los sistemas de seguridad nacional sin la aprobación expresa de los funcionarios federales apropiados que ejercen la autoridad política sobre dichos sistemas.\nEsta directriz es coherente con los requisitos de la Circular A-130 de la Oficina de Gestión y Presupuesto (OMB). Nada de lo que figura en esta publicación debe interpretarse como contradictorio con las normas y directrices que el Secretario de Comercio ha hecho obligatorias y vinculantes para los organismos federales en virtud de la autoridad legal. Estas directrices tampoco deben interpretarse como una alteración o sustitución de las autoridades existentes del Secretario de Comercio, el Director de la OMB o cualquier otro funcionario federal. Esta publicación puede ser utilizada por organizaciones no gubernamentales de forma voluntaria y no está sujeta a derechos de autor en los Estados Unidos. No obstante, el NIST agradecerá que se cite su procedencia. Publicación especial 800-207 del Instituto Nacional de Estándares y Tecnología (NIST)\n\nInst. Nac. Est. Technol. Publ. Espec. 800-207, 59 páginas (agosto de 2020) CODEN: NSPUE2\n\nEsta publicación está disponible en inglés de forma gratuita en: https://doi.org/10.6028/NIST.SP.800-207\n\nEn este documento pueden identificarse ciertas entidades, equipos o materiales comerciales con el fin de describir adecuadamente un procedimiento o concepto experimental. Dicha identificación no implica una recomendación o aprobación por parte del NIST, ni que las entidades, materiales o equipos sean necesariamente los mejores disponibles para el propósito. En esta publicación puede haber referencias a otras que actualmente están siendo desarrolladas por NIST de acuerdo con sus responsabilidades estatutarias asignadas."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nrmeasures) for an information system that are primarily implemented and executed by the information system through mechanisms contained in the hardware, software, or firmware components of the system.\n|\n|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Threat [CNSS Inst. 4009, Adapted] | Any circumstance or event with the potential to adversely impact agency operations (including mission, functions, image, or reputation), agency assets, or individuals through an information system via unauthorized access, destruction, disclosure, modification of information, and/or denial of service. |\n| Threat Agent/Source [NIST SP 800- 30] | Either: (i) intent and method targeted at the intentional exploitation of a vulnerability; or (ii) a situation and method that may accidentally trigger a vulnerability. |\n| Threat Assessment [CNSS Inst. 4009] | Formal description and evaluation of threat to an information system. |\n| Trusted Path | A mechanism by which a user (through an input device) can communicate directly with the security functions of the information system with the necessary confidence to support the system security policy. This mechanism can only be activated by the user or the security functions of the information system and cannot be imitated by untrusted software. |\n| User [CNSS Inst. 4009] | Individual or (system) process authorized to access an information system. |\n| Vulnerability [CNSS Inst."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| Chapter 1."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Planning?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nInstead, participants recommended that the government could provide top-level support for broader cybersecurity objectives, integrating planning approaches to navigate the complexities of different sectors. Tools like effective consumer education awareness campaigns may drive better security practices to ensure consumers are well-informed about cybersecurity measures as they evolve. Participants agreed that one key aspect of government involvement is effective communication, which the participants agreed should be action-based messages directed at consumers. For example, simplifying communication and facilitating customer outreach are ways to promote awareness and understanding of cybersecurity practices. Government-led programs for consumer education were seen as vital by the audience in driving consumer engagement and encouraging consumers to value secure products. It was noted that 'one size fits all communications' does not address the varying levels of knowledge in the general public."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 9)"}, {"role": "assistant", "content": "and Computer Science from Columbia University in 1978. He is a Fellow of the IEEE. \n\n\n\n\n\n\n\n\n\n\n\n\n\n## 3.\nImplantable Medical Devices - Cyber Risks and Mitigation Approaches\n\nSarbari Gupta Electrosoft Services Reston, Virginia USA sarbari@electrosoft-inc.com\n\nAbstract -Over the past decade, there has been an explosion in the deployment of implantable medical devices (IMDs) to facilitate the management and treatment of a wide variety of human health conditions. While functionality and patient safety requirements have driven new generation IMDs to be increasingly accessible through wireless communication channels, these changes cause significant concern in terms of increased risk from cyber threats whether malicious or unintentional. This paper investigates the risks associated with such devices from the cyber environment and proposes approaches to support decisions regarding the integration of adequate security and privacy measures to mitigate these risks. Keywords-medical devices; security, privacy, cyber, risks\n\n## I. Introduction\n\nDeployment rates for implantable medical devices (IMDs) have skyrocketed over the past decade. Devices such as pacemakers, cardiac defibrillators, heart monitors, cochlear implants, insulin pumps, infusion pumps and other similar devices are routinely used to monitor and treat a plethora of medical conditions. These IMDs have been increasingly accessible through wireless channels to support functions such as emergency extraction of patient health history, remote monitoring of health status, firmware updates and local as well as remote therapy reprogramming. As with all things connected to the cyber world, there are known and unknown threats lurking that threaten the reliability and safety of these devices as well the privacy of patients who depends on them. ## II."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 8)"}, {"role": "assistant", "content": "e 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.\nThe protection of a specific service to include CUI that is processed, stored or transmitted during the provision of that service, is achieved by implementing the enhanced security requirements for the service, or the system or system components responsible for providing that service. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. The term organizational system is used in many of the enhanced security requirements. It has a specific meaning regarding the applicability of the enhanced requirements as described above. Appropriate scoping considerations for the requirements are important factors in determining protection-related investment decisions and managing security risk for nonfederal organizations that have the responsibility of protecting CUI associated with critical programs and high value assets. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## FRAMEWORK FOR IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY\n\nOrganizations that have implemented or plan to implement the NIST Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nInformation security programs are responsible for protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction (i.e., unauthorized system activity or behavior) in order to provide confidentiality, integrity, and availability. Privacy programs are responsible for managing the risks to individuals associated with the creation, collection, use, processing, dissemination, storage, maintenance, disclosure, or disposal (collectively referred to as 'processing') of personally identifiable information (PII) and for ensuring compliance with applicable privacy requirements. 11 When a system processes PII, the information security and privacy programs have a shared responsibility to manage the impacts to individuals that arise from security risks and collaborate to determine the security categorization and the selection and tailoring of controls from the security control baselines."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. This publication provides security and privacy control baselines for the Federal Government. There are three security control baselines (one for each system impact level-low-impact, moderate-impact, and high-impact), as well as a privacy baseline that is applied to systems irrespective of impact level. In addition to the control baselines, this publication provides tailoring guidance and a set of working assumptions that help guide and inform the control selection process."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nThis publication provides recommendations for improving an organization's malware incident prevention measures. It also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones. This revision of the publication, Revision 1, updates material throughout the publication to reflect the changes in threats and incidents. Unlike most malware threats several years ago, which tended to be fastspreading and easy to notice, many of today's malware threats are more stealthy, specifically designed to quietly, slowly spread to other hosts, gathering information over extended periods of time and eventually leading to exfiltration of sensitive data and other negative impacts. An organization's policy statements should be used as the basis for additional malware prevention efforts, such as user and IT staff awareness, vulnerability mitigation, threat mitigation, and defensive architecture. If an organization does not state malware prevention considerations clearly in its policies, it is unlikely to perform malware prevention activities consistently and effectively throughout the organization. Malware prevention-related policy should be as general as possible to provide flexibility in policy implementation and to reduce the need for frequent policy updates, but should also be specific enough to make the intent and scope of the policy clear. Malware prevention-related policy should include provisions related to remote workers-both those using hosts controlled by the organization and those using hosts outside of the organization's control (e.g., contractor computers, employees' home computers, business partners' computers, mobile devices). Organizations should ensure that their policies address prevention of malware incidents."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.3.4. 3.3.4. 3.3.4."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.5 (NIST 3.1.5)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.1.5. 3.1.5): A one-time secret obtained from a device\n\nor application held by the subscriber that requires activation by a second\nauthentication factor\n\n• Single-factor cryptographic authentication (Sec. 3.1.5)\n\n• Multi-factor cryptographic authentication (Sec."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.1.5", "cmmc_practice_id": "AC.L2-3.1.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "ns. This publication can be used in conjunction with its companion publication, NIST Special Publication 800-171A, which provides a comprehensive set of procedures to assess the security requirements.\n## Keywords\n\nControlled Unclassified Information; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; nonfederal organizations; nonfederal systems; organization-defined parameter; security assessment; security control; security requirement. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy.\n\nThe criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nSee [SP 800-37], Task S-2, Control Tailoring, for additional guidance on tailoring control baselines for systems and environments of operation.' | 9 | | 12-10-2020 | Editorial | Section 2.4 (Footnote 28): Change 'Guidance on developing privacy plans is forthcoming.' to 'Guidance on developing privacy and supply chain risk management plans is forthcoming.' | 9 | | 12-10-2020 | Editorial | Table 3-1 (AC-3(1)) Title: Change 'FUNCTION' to 'FUNCTIONS' | 16 | | 12-10-2020 | Editorial | Table 3-1 (AC-3(6)): Change 'MP-4, SC-28' to 'MP-4 and SC-28' | 16 | | 12-10-2020 | Editorial | Table 3-1 (AC-13): Change 'AC-2, AU-6' to 'AC-2 and AU-6' | 18 | | 12-10-2020 | Editorial | Table 3-1 (AC-19(5)) Title: Change 'FULL DEVICE AND' to 'FULL DEVICE OR' | 19 | | 12-10-2020 | Editorial | Table 3-1 (AC-20(4)) Title: Change 'NETWORK-ACCESSIBLE' to 'NETWORK ACCESSIBLE' | 19 | | 12-10-2020 | Editorial | Table 3-2 (AT-3(5)) Title: Change 'ACCESSING PERSONALLY' to 'PROCESSING PERSONALLY' | 20 | | 12-10-2020 | Editorial | Table 3-3 (AU-7(2)) Title: Change 'SEARCH AND SORT' to 'SORT AND SEARCH' | 21 | | 12-10-2020 | Editorial | Table 3-3 (AU-15): Change 'Incorporated into' to 'Moved to' | 22 |"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nadopting secure software development practices involving AI models. The contents of the Profile are meant to be adapted and customized, as not all practices and tasks are applicable to all use cases.\nOrganizations should adopt a riskbased approach to determine what practices and tasks are relevant, appropriate, and effective to mitigate the threats to software development practices from the organization's perspective as an AI model producer, AI system producer, or AI system acquirer. Factors such as risk, cost, feasibility, and applicability should be considered when deciding which practices and tasks to use and how much time and resources to devote to each one. Cost models may need to be updated to effectively consider the costs inherent to AI model development. A risk-based approach to secure software development may change over time as an organization responds to new or elevated capabilities and risks associated with an AI model or system. Generative AI and dual-use foundation models present additional challenges in tracking model versioning and lineage. Source code for defining the model architecture and building model binaries is amenable to secure software engineering practices for versioning, lineage, and reproducibility. However, the final model weights are defined only after the model is trained and fine-tuned; this is where limitations in tracking all aspects of collection, processing, and training arise. Organizations should follow secure software development practices for the parts of a model that can be covered fully and strive to introduce secure practices to the extent possible for the stages and corresponding artifacts where obtaining such security guarantees is hard to achieve. Organizations should document the parts and artifacts that are not covered by the secure software development practices."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 3)"}, {"role": "assistant", "content": "es even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. Submit comments on this publication to:\n\nssdf@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide? (Part 7)"}, {"role": "assistant", "content": "While the NCCoE used a suite of commercial products to address this challenge, this guide does not endorse these particular products, nor does it guarantee compliance with any regulatory initiatives.\nYour organization's information security experts should identify the products that will best integrate with your existing tools and IT system infrastructure. Your organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring and implementing parts of a solution. ## HOW TO USE THIS GUIDE\n\nDepending on your role in your organization, you might use this guide in different ways:\n\nBusiness decision makers, including chief information security and technology officers, can use this part of the guide, NIST SP 1800-10A: Executive Summary , to understand the drivers for the guide, the cybersecurity challenge we address, our approach to solving this challenge, and how the solution could benefit your organization. Technology, security, and privacy program managers who are concerned with how to identify, understand, assess, and mitigate risk can use NIST SP 1800-10B: Approach, Architecture, and Security Characteristics . It describes what we built and why, including the risk analysis performed and the security/privacy control mappings. Technology professionals who want to implement an approach like this can make use of NIST SP 180010C: How-To Guides . It provides specific product installation, configuration, and integration instructions for building the example implementation, allowing you to replicate all or parts of this project. ## SHARE YOUR FEEDBACK\n\nYou can view or download the guide at https://www.nccoe.nist.gov/projects/usecases/manufacturing/integrity-ics. Once the example implementation is developed, you can adopt this solution for your own organization. If you do, please share your experience and advice with us."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 7)"}, {"role": "assistant", "content": "| Survey Data Analysis ..................................................................................................\n| 6 |\n| 3 | REPRESENTED PARTICIPANTS, ORGANIZATIONS, AND PROGRAMS ............ 7 | REPRESENTED PARTICIPANTS, ORGANIZATIONS, AND PROGRAMS ............ 7 |\n| 3.1 PARTICIPANTS ...................................................................................................................... 7 | 3.1 PARTICIPANTS ...................................................................................................................... 7 | 3.1 PARTICIPANTS ...................................................................................................................... 7 |\n| 3.1.1 | Security Awareness Role............................................................................................. | 8 |\n| 3.1.2 | Time Spent on Security Awareness ............................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\ngement, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems.\nThe Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 7)"}, {"role": "assistant", "content": "| 2.4 Limitation of Authentication Infrastructure...............................................................................6 | 2.4 Limitation of Authentication Infrastructure...............................................................................6 | 2.4 Limitation of Authentication Infrastructure...............................................................................6 | | Network Security Appliances in the Enterprise Network Landscape ............................8 | Network Security Appliances in the Enterprise Network Landscape ............................8 | | | Cloud Access Security Broker (CASB)..........................................................................8 | Cloud Access Security Broker (CASB)..........................................................................8 | | | Enhanced Firewall Capabilities | Enhanced Firewall Capabilities | .....................................................................................8 | | Appliance-set with Integrated Functions | Appliance-set with Integrated Functions | .....................................................................10 | | Network Security Automation Tools | Network Security Automation Tools | ............................................................................11 | | 3.4.1."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nThis section provides further guidance on what type of information is expected for a specific requirement or set of requirements from Annex B and the additional requirements listed in Section 3.2. All of the requirement statements are organized into appropriately named and numbered subsections (e.g., 1.2 - Security Levels, 2.1 - Purpose or Use). Each subsection identifies the applicable requirements and provides any clarifying and explanatory notes."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/\nsp/800/63/A/4/final, including related content, potential updates, and document\nhistory.\n\n3.7. Additional Requirements for Federal Agencies\n\n4.3.7. On-Site Attended Requirements — Colocated Agent"}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nn approaches were adequately tailored. Teams indicated that any standardization effort should similarly be human-centric and consider the spectrum of potential users of a given application or product.\nUnlike some areas of cybersecurity (e.g., encryption) which require limited human interaction, particularly with users, education and awareness addresses the human-in-the-loop and so depends, in large part, on human-factors for efficacy. All three teams specifically considered how their designs could be 'easiest' for users to use, understand, and be most accessible. Teams 1 and 3 incorporated gamification and other interactive elements to encourage users to pursue cybersecurity topics. For example, Team 3 attempted to gamify the pursuit of cybersecurity knowledge relative to the product by building out 'levels' of concepts that build upon each other so that users could 'level up' at their pace. Understanding and encouraging cybersecurity engagement has been a focus of research for the SOUPS community [8][9][10][11][12][13], and so the teams brought the insights from that research to the practical tasks of the Design-A-Thon. The contextual nature of cybersecurity education and awareness approaches was apparent when two teams (i.e., Teams 2 and 3) selected the same product but developed different approaches and focused on different aspects of the design. Teams 2 and 3 homed in on different information that may be useful at different times during the product's lifecycle. In one case, Team 2 focused on ensuring information was at users' fingertips, particularly when support was needed. In the other case, Team 3 considered how individuals could be encouraged to engage on cybersecurity education and awareness outside of times they needed support, landing on gamification elements."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n## Validating the Integrity of Computing Devices\n\n## Validating the Integrity of Computing Devices\n\n## Validating the Integrity of Computing Devices"}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to A Data Structure for Integrity Protection with Erasure Capability:\n\nThe data block matrix technology (US Patent #11,175,826) is available to be licensed . For information on patent and licensing see NIST Technology Partnerships Office (TPO). Parties interested in licensing a NIST-owned invention may contact TPO, or may complete a research license application or commercial use license application. Instructions on how to submit the license application are provided at the end of each application. When a license application is received, TPO will contact you regarding the licensing process and to obtain additional information that may be necessary for the application process. A license application should include the prospective licensee's intentions for research and development of the invention(s) and a description of the resources and technical capabilities of the prospective licensee to bring the invention to practical application."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 10)"}, {"role": "assistant", "content": "CAD/RMS web app and IdP at county (SAML proxy). .............................................................45 |\n| Fig. 23. CAD/RMS web app and IdP at state - OIDC and OAuth 2.0.\n...................................................47 |\n| Fig. 24. VPN with an LDAP directory..................................................................................................49 |\n| Fig. 25. VPN with Kerberos. ..............................................................................................................50 |\n| Fig. 26. VPN gateway integration with enterprise SSO.......................................................................51 |\n\n## Acknowledgments\n\nWe are grateful to the following individuals for their generous contributions of expertise and time. | Name | Organization |\n|---------------------|--------------------------------------------|\n| Chris Weatherly | Federal Bureau of Investigation (FBI) CJIS |\n| Jeff Campbell | FBI CJIS |\n| Holden Cross | ECS |\n| John Beltz | NIST |\n| Hildegard Ferraiolo | NIST |\n| Ryan Galluzzo | NIST |\n| Cheri Pascoe | NIST |\n| Andrew Regenscheid | NIST |\n| Ron Pulivarti | NIST |\n| Julie Chua | NIST |\n\n## Executive Summary\n\nThe Criminal Justice Information Services (CJIS) Security Policy versions 5.9.2 and later [1] require the use of multi-factor authentication (MFA) to protect access to criminal justice information (CJI). MFA is important for protecting against credential compromises and other cyber risks that may threaten CJI."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Software Supply Chain (SSC) -Definition and Model .....................................................................4 |\n| 2.4.1. Software Supply Chain Defects ....................................................................................................6 |\n| 2.4.2. Software Supply Chain Attacks.....................................................................................................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1. Developer Environment ...............................................................................................................8 |\n| 3.1.2. Threat Actors................................................................................................................................8 |\n| 3.1.3. Attack Vectors ..............................................................................................................................9 |\n| 3.1.4. Attack Targets (Assets).................................................................................................................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 7)"}, {"role": "assistant", "content": "6: Machine Learning RFC method for access control policy verification.........................................12 | | Figure 7: Numerical attribute values in a subtree model ............................................................................15 | Figure 7: Numerical attribute values in a subtree model ............................................................................15 | | List of Tables | List of Tables | ## 1 Introduction As a software test, access control policy verification relies on methods such as model proof [Hwang et al."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nof network events that can be used to identify patterns of performance and security issues. - Access control functions: Access control functions enforce granular sophisticated access control policies.\n- Multiple locations and functions: Firewalls reside at different locations to perform different functions. Firewalls at the network edge perform the network perimeter protection function by filtering disallowed sources and destinations and blocking the packets of potential threats. Firewalls inside a data center can segment the internal network to prevent the lateral movement of traffic and isolate sensitive resources (e.g., services and data stores). Device-based firewalls prevent malicious traffic in and out of endpoints. - Open Application Programming Interfaces (APIs): These enable integration with many networking products that provide additional security capabilities. - Policy Composition Capabilities: Some firewalls can have the capabilities to merge policies at enforcement time so as to ensure that consistent policies are applied to different classes of users (e.g., those on-premises and on private and public clouds). - Web application firewalls (WAF): This class of firewalls has been used ever since web applications accessed through web protocols, such as Hypertext Transfer Protocol"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n| Table of Contents | Table of Contents | Table of Contents |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| TABLE OFCONTENTS.............................................................................................................V | TABLE OFCONTENTS.............................................................................................................V | |\n| LIST OF FIGURES....................................................................................................................VII | LIST OF FIGURES....................................................................................................................VII | |\n| LIST OFTABLES.................................................................................................................... | LIST OFTABLES...................................................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nPairs for Key Establishment .......................................................... | 6.2 Criteria for RSA Key Pairs for Key Establishment ..........................................................\n| 37 |\n| | 6.2.1 | Definition of a Key Pair ......................................................................................... | 37 |\n| | 6.2.2 | Formats................................................................................................................... | 37 |\n| 6.3 RSA Key-Pair Generators................................................................................................. | 6.3 RSA Key-Pair Generators................................................................................................. | 6.3 RSA Key-Pair Generators................................................................................................. | 38 |\n| | 6.3.1 | RSAKPG1 Family: RSA Key-Pair Generation with a Fixed Public Exponent ....."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 6)"}, {"role": "assistant", "content": "publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication.\n## Table of Contents\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................4 |\n| 2. HIPAA Security Rule .......................................................................................................................9 |\n| 3. Risk Assessment Guidance............................................................................................................14 |\n| 4. Risk Management Guidance .........................................................................................................24 |\n| 5. Considerations When Implementing the HIPAA Security Rule........................................................28 |\n| 5.1.2. Assigned Security Responsibility (§ 164.308(a)(2)) ....................................................................35 |\n| 5.1.3. Workforce Security (§ 164.308(a)(3)).........................................................................................36 |\n| 5.1.4. Information Access Management (§ 164.308(a)(4)) ..................................................................38 |\n| 5.1.5. Security Awareness and Training (§ 164.308(a)(5)) ...................................................................41 |\n| 5.1.6."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.2.6 Environment Control | 4-11 |\n| 4. 3.2.6 Environment Control ."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.2.6", "cmmc_practice_id": "AT.L2-3.2.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\n1. Each IoT product component controls access to and from all interfaces (e.g., local interfaces, whether externally accessible or not, network interfaces, protocols, and services) in order to limit access to only authorized entities. At a minimum, the IoT product component shall:\n- a. Use and have access only to interfaces necessary for the IoT product's operation. All other channels and access to channels are removed or secured. - b. For all interfaces necessary for the IoT product's use, access control measures are in place (e.g., unique password-based multifactor authentication, physical interface ports inaccessible from the outside of a component). - c. For all interfaces, access and modification privileges are limited. 2. Some, but not necessarily all, IoT product components have the means to protect and maintain interface access control. At a minimum, the IoT product shall:\n- a. Validate that data shared among IoT product components match specified definitions of format and content. - b. Prevent unauthorized transmissions or access to other product components. - c. Maintain appropriate access control during initial connection (i.e., onboarding) and when reestablishing connectivity after disconnection or outage."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Access Control?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n- [1] Joint Task Force Transformation Initiative (2013) Security and Privacy Controls for Federal Information Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-53, Rev. 4, Includes updates as of January 22, 2015. https://doi.org/10.6028/NIST.SP.800-53r4\n- [2] Fagan M, Megas KN, Scarfone K, Smith M (2020) Foundational Cybersecurity Activities for IoT Device Manufacturers. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8259. https://doi.org/10.6028/NIST.IR.8259\n- [3] Joint Task Force Transformation Initiative (2012) Guide for Conducting Risk Assessments. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-30, Rev. 4. https://doi.org/10.6028/NIST.SP.80030r1\n- [4] Boeckl K, Fagan M, Fisher W, Lefkovitz N, Megas K, Nadeau E, Piccarreta B, Gabel O'Rourke D, Scarfone K (2019) Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8228. https://doi.org/10.6028/NIST.IR.8228\n- [5] AgeLight Digital Trust Advisory Group (2019) IoT Safety Architecture & Risk Toolkit (IoTSA) v3.1. (AgeLight Advisory & Research Group, Bellevue, WA). http://agelight.com/iot.html\n- [6] Broadband Internet Technical Advisory Group (BITAG) (2016) Internet of Things (IoT) Security and Privacy Recommendations. (Broadband Internet Technical Advisory Group [BITAG], Denver, CO). https://www.bitag.org/documents/BITAG\\_Report\\_-\\_Internet\\_of\\_Things\\_(IoT)\\_Security\\_and\\_Privacy\\_Recommendations.pdf\n- [7] Cloud Security Alliance (CSA) IoT Working Group (2015) Identity and Access Management for the Internet of Things. (Cloud Security Alliance [CSA])."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines provide? (Part 7)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . . . . 3.3.2. Assurance Level Descriptions\n\n. . . . . . . . . . . . . . . . . . . 3.3.3. Initial Assurance Level Selection . . . . . . . . . . . . . . . . . . 3.3.4.\nIdentify Baseline Controls . . . . . . . . . . . . . . . . . . . . . 3.4. Tailor and Document Assurance Levels\n\n. . . . . . . . . . . . . . . . . . 3.4.1. Assess Privacy, Customer Experience, and Threat Resistance . . . 3.4.2. Identify Compensating Controls . . . . . . . . . . . . . . . . . . 3.4.3. Identify Supplemental Controls . . . . . . . . . . . . . . . . . . 3.4.4. Digital Identity Acceptance Statement . . . . . . . . . . . . . . . 3.5. Continuously Evaluate and Improve . . . . . . . . . . . . . . . . . . . . 3.5.1. Evaluation Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2. Performance Metrics . . . . . . . . . . . . . . . . . . . . . . . . 3.5.3. Measurement in Support of Customer Experience Outcomes\n\n. . Redress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cybersecurity, Fraud, and Identity Program Integrity . . . . . . . . . . . 3.6. 3.7. 3.8. Artificial Intelligence and Machine Learning in Identity Systems\n\n. . . . . References\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A. List of Symbols, Abbreviations, and Acronyms . . . . . . . . . . . . Appendix B. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.1. C.2. C.3. C.4. SP 800-63-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SP 800-63-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SP 800-63-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SP 800-63-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of Tables\nTable 1. Table 2. Table 3. Table 4. IAL Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AAL Summary . . . ."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MP.L2-3.8.2 (NIST 3.8.2)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.8.2 | The ADP Auditor | The ADP Auditor | 65 |\n| CHAPTER 4 | CHAPTER 4 | CHAPTER 4 | CHAPTER 4 | CHAPTER 4 |\n| AIS | DEVELOPMENTAL | DEVELOPMENTAL | AUDITS | 67 |\n\ni\n\n^\n\n(\n\nI\n\n^\n\n| 4. 3.8.2 The ADP Auditor\n\nHopefully, the ADP auditor will have the opportunity to prioritize his or her work before jumping in."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.8.2", "cmmc_practice_id": "MP.L2-3.8.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 7)"}, {"role": "assistant", "content": ". Overview of Key-Establishment Schemes........................................................... | 4. Overview of Key-Establishment Schemes...........................................................\n| 14 |\n| | 4.1 | Key Establishment Preparations .................................................................................... | 15 |\n| | 4.2 | Key-Agreement Process................................................................................................. | 17 |\n| | 4.3 | DLC-based Key-Transport Process ............................................................................... | 19 |\n| 5. Cryptographic Elements ......................................................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n- NIST research and publications on trustworthy and responsible AI, including the Artificial Intelligence Risk Management Framework (AI RMF 1.0) [2], Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations [3], Towards a Standard for Identifying and Managing Bias in Artificial Intelligence [4], and the Dioptra experimentation testbed for security evaluations of machine learning algorithms [5]. - NIST's Secure Software Development Framework (SSDF) Version 1.1 [6], which is a set of fundamental, sound, and secure software development practices. It provides a common language to help facilitate communications among stakeholders, including software producers and software acquirers. The SSDF has also been used in support of EO 14028, Improving the Nation's Cybersecurity [7], to enhance software supply chain security. - NIST general cybersecurity resources, including The NIST Cybersecurity Framework (CSF) 2.0 [8], Security and Privacy Controls for Information Systems and Organizations [9], and Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations [10]. - AI model developers, AI researchers, AI system developers, and secure software practitioners from industry and government with expertise in the unique security challenges of AI models and the practices for addressing those challenges. This expertise was primarily captured through NIST's January 2024 workshop, where speakers and attendees shared suggestions for adapting secure software development practices and tasks to accommodate the unique aspects of AI model development and the software leveraging them."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n| Phase | User Base | Rationale | Outcome |\n|---------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 | IT support and help desk personnel | IT support and help desk personnel are tech-savvy users who can also anticipate potential support issues that the larger user base may have with the solution. | • Test multiple authenticator types and gain feedback on the processes of obtaining and using each authenticator. • Enumerate potential support issues. • Gain feedback on MFA instructions and communication tools. • Confirm authenticator type selection. |\n| 2 | General IT staff | This is a larger, but still technically literate, user base. | • Test authenticators selected from phase 1. • Gain feedback on MFA instructions and communication tools. • Update communications and/or policy based on feedback. |\n| 3 | General user cohort | A representative cohort of general users can help test the MFA solution before a general user rollout. | • Take volunteers or a selection of the general cohort to test the MFA solution."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.3.3. 3.3.3. 3.3.3."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nn of Posture Evaluator service instances across the network. A Posture Evaluator retrieves previously collected posture from a CMDB and requests new posture collection from Posture Collection Servers.\nThrough these interactions, Posture Evaluators gain access to current posture information without having to collect all posture information directly from Endpoints. Posture Evaluators can store evaluation results in CMDBs, making these results available for additional evaluation and use by other tools. - Configuration Management Database: A Configuration Management Database (CMDB) maintains stores of collected endpoint posture information and evaluated data. Before directing the collection of additional posture information from Endpoints, evaluators can query one or more CMDBs to retrieve previously collected information, streamlining data collection needs. CMDBs serve as a consolidated point of access control for authorizing access to posture information, reducing the need for peer-to-peer trust relationships that open attack vectors on the network. - SCAP Content Repository: SCAP v2 will continue to support interoperable, standardized content formats, enabling community-driven content production. Additionally, SCAP v2 supports discovery and retrieval of content through standardized interfaces. One or more SCAP Content Repositories can serve SCAP content including SWID tags, vulnerability records, configuration checklists, and other security automation content. Authorized SCAP components will be able to automatically retrieve new and updated content from local and/or remote SCAP Content Repositories, keeping used content current and improving content reuse. NIST, software vendors, and third-parties will be able to self-publish and manage their own content, while allowing tools to automatically access this content."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nance that the shared resources, i.e., networks, communications, and physical access within the whole general support system or major application, are protected adequately for the highest impact level.\nHaving the ability to isolate the high impact systems will not only result in more secure systems, but will also reduce the amount of resources required to secure many applications/systems that do not require that level of security. NIST SP 800-53 provides three security control baselines, i.e., low, moderate, and high, that are associated with the three FIPS 199 impact levels; as the impact level increases, so do the minimum assurance requirements. For reporting purposes, i.e., FISMA annual report, when an information system has varying FIPS 199 impact levels, that system is categorized at the highest impact level on that information system."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.2.3 | Identify System Resource Recovery Priorities ... 3.2.3 Identify System Resource Recovery Priorities\n\nDeveloping recovery priorities is the last step of the BIA process."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 4)"}, {"role": "assistant", "content": "NA]), and the evolving wide area network (WAN) infrastructure to provide a comprehensive set of security services for the modern enterprise network landscape (e.g., secure access service edge [SASE]).\n## Keywords\n\ncloud access security broker (CASB); firewall; microsegmentation; secure access service edge (SASE); secure web gateway (SWG); security orchestration, automation, and response (SOAR); software-defined perimeter (SDP); software-defined wide area network (SD-WAN); virtual private network (VPN); zero trust network access (ZTNA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n- Incident Management: Incidents are escalated or elevated as needed [RS.MA-04]\n- Incident Response Reporting and Communication: Internal and external stakeholders are notified of incidents [RS.CO-02]"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 10)"}, {"role": "assistant", "content": "Parameters\n- Appendix E: Change Log\n\nThe contents of this publication can be used for many different assessment-related purposes to determine organizational compliance with the security requirements.\nThe broad range of potential assessment methods and objects listed in this publication does not necessarily reflect and should not be directly associated with actual compliance or noncompliance. Rather, the selection of specific assessment methods and objects from the list provided can help generate a picture of overall compliance with the security requirements. There is no expectation about the number of methods or objects needed to determine compliance with the security requirements. Moreover, the entire list of potential assessment objects should not be viewed as required artifacts needed to determine compliance. Organizations have the flexibility to determine the specific methods and objects sufficient to obtain the needed evidence to support any claims of compliance. ## 2. The Fundamentals\n\nThe process used by organizations and assessors to assess the security requirements in SP 800171 [3] includes (1) preparing for the assessment, (2) developing a security assessment plan, (3) conducting the assessment, and (4) documenting, analyzing, and reporting the assessment results. 2 The remainder of this section describes the structure and content of the procedures used to assess the security requirements and the importance of assurance cases in providing the evidence necessary to determine compliance with the requirements. ## 2.1. Assessment Procedures\n\nThe security requirements in SP 800-171 are organized into 17 families, as illustrated in Table 1. The assessment procedures in Sec. 3 are grouped by similar family designations to ensure the completeness and consistency of assessments. The procedures have been derived from the assessment procedures in SP 800-53A [5]. Table 1."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n| 1. Introduction...................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. HPC System Reference Architecture and Main Components ............................................................2 |\n| 2.1.1. Components of the High-Performance Computing Zone.............................................................3 |\n| 2.1.2. Components of the Data Storage Zone........................................................................................4 |\n| 2.1.3. Parallel File System.......................................................................................................................4 |\n| 2.1.4. Archival and Campaign Storage....................................................................................................5 |\n| 2.1.5. Burst Buffer ..................................................................................................................................5 |\n| 2.1.6. Components of the Access Zone..................................................................................................6 |\n| 2.1.7. Components of the Management Zone.......................................................................................6 |\n| 2.1.8. General Architecture and Characteristics ....................................................................................6 |\n| 2.1.9. Basic Services................................................................................................................................7 |\n| 2.1.10."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-66r2\n\n## Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule\n\nA Cybersecurity Resource Guide\n\nJeffrey A. Marron\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-66r2\n\n\n\n## NIST Special Publication 800 NIST SP 800-66r2\n\n## Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule\n\nA Cybersecurity Resource Guide\n\nJeffrey A. Marron Applied Cybersecurity Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-66r2\n\nFebruary 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide?"}, {"role": "assistant", "content": "\n\n\n\n## NIST Cybersecurity Framework 2.0:\n\nQuick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)\n\n\n\nLaurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and\n\nNIST Special Publication NIST SP 1305\n\nhttps://doi.org/10.6028/NIST.SP.1305 Please send your comments to cyberframework@nist.gov. ## NIST CSF 2.0: CYBERSECURITY SUPPLY CHAIN RISK MANAGEMENT (C-SCRM)\n\nA QUICK-START GUIDE\n\n## INTRODUCTION TO C-SCRM\n\n## Use the CSF to Improve Your C-SCRM Processes\n\nThe CSF can help an organization become a smart acquirer and supplier of technology products and services. This guide focuses on two ways the CSF can help you:\n\n1. Use the CSF's GV.SC Category to establish and operate a C-SCRM capability. 2. Define and communicate supplier requirements using the CSF . ## What is the supply chain ecosystem? The supply chain ecosystem is composed of public and private sector entities - including acquirers, suppliers, developers, system integrators, external system service providers, and other technology-related service providers - that interact to research, develop, design, manufacture, acquire, deliver, integrate, operate, maintain, dispose of, and otherwise utilize or manage technology products and services. Consider a laptop with hardware subcomponents (like the graphics processor, random-access memory, or network interface card) sourced from different countries and third-party manufacturers, and subject to distinct supply chain interactions. That laptop also contains software (and firmware) developed by different companies and people. How do we manage risk for complex ICT devices with multiple components? In today's interconnected world, the supply chain ecosystem includes other third parties such as business partners and various data and digital service providers. Practices in this QSG can be applied to manage cybersecurity risks from such relationships as well."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n.............6 |\n| 2.1.9. Basic Services................................................................................................................................7 |\n| 2.1.10.\nConfiguration Management.......................................................................................................7 |\n| 2.1.11. HPC Scheduler and Workflow Management..............................................................................7 |\n| 2.1.12. HPC Software..............................................................................................................................8 |\n| 2.1.13. User Software.............................................................................................................................8 |\n| 2.1.14. Site-Provided Software and Vendor Software ...........................................................................8 |\n| 2.1.15. Containerized Software in HPC ..................................................................................................9 |\n| 3. HPC Threat Analysis......................................................................................................................10 |\n| 3.2.1. Access Zone Threats...................................................................................................................11 |\n| 3.2.2. Management Zone Threats........................................................................................................11 |\n| 3.2.3. High-Performance Computing Zone Threats..............................................................................12 |\n| 3.2.4. Data Storage Zone Threats.........................................................................................................12 |\n| 4."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThis publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, 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. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 7)"}, {"role": "assistant", "content": "171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements.\n|\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |\n\n\n\nView more FAQs here. If you still have a question after reviewing all our FAQs , send your question to: sec-cert@nist.gov. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n\n\n## Additional Resources\n\n## Online Introductory Courses Available for the NIST SP 800-53 Series\n\n\n\nSP 800-171 requirements are focused on protecting confidentiality and are based on a subset of controls found in SP 800-53, which is a catalog of security and privacy controls for systems and organizations. With that in mind, it is important to have a basic understanding of the SP 800-53 series. To assist, NIST has released three self-guided online introductory courses to provide a high-level overview of foundational security and privacy risk management concepts. The online introductory courses are between 45-60 minutes, are available at no cost, and registration is not required. Access the courses. ## Roles of Different Federal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nreover, adversaries are using the supply chain as an attack vector and effective means of penetrating our systems, compromising the integrity of system elements, and gaining access to critical assets.\n- To provide closer linkage and communication between the risk management processes and activities at the C-suite or governance level of the organization and the individuals, processes, and activities at the system and operational level of the organization;\n- To institutionalize critical risk management preparatory activities at all risk management levels to facilitate a more effective, efficient, and cost-effective execution of the RMF;\n- To demonstrate how the NIST Cybersecurity Framework [NIST CSF] can be aligned with the RMF and implemented using established NIST risk management processes;\n- To integrate privacy risk management processes into the RMF to better support the privacy protection needs for which privacy programs are responsible;\n- To promote the development of trustworthy secure software and systems by aligning life cycle-based systems engineering processes in NIST Special Publication 800-160, Volume 1 [SP 800-160 v1], with the relevant tasks in the RMF;\n- To integrate security-related, supply chain risk management (SCRM) concepts into the RMF to address untrustworthy suppliers, insertion of counterfeits, tampering, unauthorized production, theft, insertion of malicious code, and poor manufacturing and development practices throughout the SDLC; and\n- To allow for an organization-generated control selection approach to complement the traditional baseline control selection approach and support the use of the consolidated control catalog in NIST Special Publication 800-53, Revision 5."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Updates to the Security Requirements and Families\n\n- It is important to identify permitted and prohibited actions regarding software installation when users have the ability to install software on organizational systems. Permitted software installations could include updates and security patches to existing software and downloading new applications from organizationapproved 'app stores.' Companies might prohibit employees from downloading certain programs, services, software versions, etc ."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nInstead, to achieve the goal of routing email through Glasswall, we redirect local mail exchange (MX) records to Glasswall FileTrust. We implemented it this way because of limitations of the lab environment, but organizations should consult with the vendor for the best solution to route email through the email sanitization component, as other options may be available depending on the enterprise."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n□ Malware, including viruses, ransomware, etc.\n\n□ Cybersecurity incident response"}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nsential for patient safety in emergency conditions from patient personally identifiable information/data to allow different authentication and access control mechanisms to apply to each group of data.\nAlternately, identifying different modes of operation (such as home health setting versus open environment versus emergency situation) to allow the IMD to apply different authentication and access control mechanisms in different modes."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Configuration Management?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\ncybersecurity baseline; Internet of Things (IoT); IoT products; manufacturing; privacy; risk management; securable products; security requirements; software development; threat modelling. Over time, the NIST volume of work has built upon the concepts introduced in the NIST IR 8259 series to introduce technical, IoT Device Cybersecurity Capability Core Baseline (NIST IR 8259A) and nontechnical, IoT Non-Technical Supporting Capability Core Baseline (NIST IR 8259B) concepts to help manufacturers and customers consider the cybersecurity of IoT devices. The NIST IR 8259 series has been used to inform and develop subsequent publications that elaborate on IoT cybersecurity across sectors and use cases (e.g., federal agency uses cases reflected in IoT Device Cybersecurity Guidance for the Federal Government: Establishing IoT Device Cybersecurity Requirements (NIST SP 800-213) and consumer use cases reflected in Profile of the IoT Core Baseline for Consumer IoT Products (NIST IR 8425) and the U.S. Cyber Trust Mark). Privacy is a complex and evolving concept that safeguards important values like human autonomy and dignity. It reflects various factors and individual preferences and is highly context-specific, differing between public and private activities. Effective privacy risk management must consider these contexts and the various ways to achieve privacy, such as seclusion, limiting observation, and controlling facets of identity. Gilbert emphasized that privacy could drive innovation and serve as a market differentiator. However, organizations need to have honest and risk-informed discussions about how best to balance optimizing data utility while protecting individuals' privacy, particularly in cases where privacy risk interacts with other risk domains such as cybersecurity. The NIST Privacy Framework helps organizations understand the relationship between privacy and cybersecurity risks in the context of the Internet of Things (IoT)."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.2.4. 3.2.4 Create an Authorized Service Token\n\n1."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n- External attackers who seek privileged access to an SSC\n- Disgruntled employees or contractors who perpetuate insider threats\n\napplications. This paradigm consists of a series of stages that takes code from variously sourced In this document, the term 'artifacts' denotes source code as well as the things generated from it, such as builds and packages. Each of the artifacts is associated with an owner. The logical containers that hold these artifacts are called repositories. The build process is based on application logic-driven dependencies and generates builds using many individual source-code artifacts that are stored in build repositories. The build artifacts are tested and used to generate packages whose artifacts are then stored in designated repositories and scanned before being deployed in testing or production environments. These stages and the various tasks performed at each stage are collectively called CI/CD pipelines. In other words, CI/CD pipelines use processes called workflows to transform source artifacts to deployable packages in production environments. A common approach to SSC security in all of these workflows is to generate as much provenance data as possible. Provenance data are associated with the chronology of the origin, development, ownership, location, and changes to a system or system component, including the personnel and processes that enabled those changes or modifications. The generation of these data should be accompanied by corresponding mechanisms to validate, authenticate, and leverage them in policy decisions. From the above description of CI/CD pipelines and associated activities, one can identify the set of security assurance measures that need to be added:\n\n- SAST and DAST tools (covering all languages used in development) should be run in CI/CD pipelines with code coverage reports being provided to developers and security personnel."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\n\n\n## NIST Internal Report NIST IR 8425\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nMichael Fagan Katerina Megas Paul Watrobski Jeffery Marron Barbara Cuthill\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8425\n\n\n\n## NIST Internal Report NIST IR 8425\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nMichael Fagan Katerina N. Megas Paul Watrobski Jeffrey Marron Barbara B. Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8425\n\nSeptember 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n3.1.2 | Time Spent on Security Awareness ... 3.1.2 Time Spent on Security Awareness\n\n## Focus Groups\n\nThe focus group demographic survey asked what percentage of time participants spend on their security awareness duties."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. AI model producers, AI system producers, AI system acquirers, and others can use the SSDF to foster their communications regarding secure AI model development throughout the software development life cycle. 2 Following SSDF practices should help AI model producers reduce the number of vulnerabilities in their AI models, reduce the potential impacts of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of vulnerabilities to prevent recurrences. AI system producers can use the SSDF's common vocabulary when communicating with AI model producers regarding their security practices for AI model development and when integrating AI models into the software they are developing. AI system acquirers can also use SSDF terms to better communicate their cybersecurity requirements and needs to AI model producers and AI system producers, such as during acquisition processes. The SSDF Community Profile is not a checklist to follow, but rather a starting point for planning and implementing a risk-based approach to adopting secure software development practices involving AI models. The contents of the Profile are meant to be adapted and customized, as not all practices and tasks are applicable to all use cases."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "following components: (i) a control section; (ii) a supplemental guidance section; (iii) a control enhancements section; (iv) a references section; and (v) a priority and baseline allocation section.\nFigure 2: The Risk Management Framework\n\n\n\n## 3 Control Baselines and Tailoring\n\nTo assist organizations in making the appropriate selection of security controls for information systems, the concept of security control baselines is introduced. Security control baselines are the starting point for the security control selection process and are chosen based on the security category and associated impact level of information systems determined in accordance with FIPS Publication 199 and FIPS Publication 200, respectively (Step One of the RMF). SP 800-53 Rev. 4 states that 'the security controls and control enhancements listed in the initial baselines are not a minimum- but rather a proposed starting point from which controls and controls enhancements may be removed or added.' Appendix D provides a listing of baseline security controls corresponding to the low-impact, moderate-impact, and high-impact information systems, using the high water mark defined in FIPS Publication 200. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.2 (NIST 3.7.2)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.7.2 | Methods for Overcoming Difficulties | Methods for Overcoming Difficulties | 64 |\n| 3."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.7.2", "cmmc_practice_id": "MA.L2-3.7.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.2 (NIST 3.6.2)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.6.2 Resolution\n\nThe build has several layers of defense against this use case."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.6.2", "cmmc_practice_id": "IR.L2-3.6.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 2)"}, {"role": "assistant", "content": "ation services. The Laboratory consists of the following centers:\n\nAbsolute Physical Quantities' - Radiation Research - Thermodynamics and Molecular Science - Analytical Chemistry - Materials Science.\nTHE NATIONAL ENGINEERING LABORATORY provides technology and technical services to the public and private sectors to address national needs and to solve national problems; conducts research in engineering and applied science in support of these efforts; builds and maintains competence in the necessary disciplines required to carry out this research and technical service; develops engineering data and measurement capabilities; provides engineering measurement traceability services; develops test methods and proposes engineering standards and code changes; develops and proposes new engineering practices; and develops and improves mechanisms to transfer results of its research to the ultimate user. The Laboratory consists of the following centers:\n\nApplied Mathematics - Electronics and Electrical Engineering- Mechanical Engineering and Process Technology' - Building Technology - Fire Research Consumer Product Technology - Field Methods. THE INSTITUTE FOR COMPUTER SCIENCES AND TECHNOLOGY conducts research and provides scientific and technical services to aid Federal agencies in the selection, acquisition, application, and use of computer technology to improve effectiveness and economy in Government operations in accordance with Public Law 89-306 (40 U.S.C. 759), relevant Executive Orders, and other directives; carries out this mission by managing the Federal Information Processing Standards Program, developing Federal ADP standards guidelines, and managing Federal participation in ADP voluntary standardization activities; provides scientific and technological advisory services and assistance to Federal agencies; and provides the technical foundation for computer-related policies of the Federal Government."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 3)"}, {"role": "assistant", "content": "ilable at https://csrc.nist.gov/pubs/ir/8523/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA).\n## Abstract\n\nMost recent cybersecurity breaches have involved compromised credentials. Migrating from single-factor to multi-factor authentication (MFA) reduces the risk of compromised credentials and unauthorized access. Both criminal and noncriminal justice agencies need to access criminal justice information (CJI); to reduce the risk of unauthorized access, the Criminal Justice Information Services (CJIS) Security Policy now requires the use of MFA when accessing CJI. This document provides practical information to agencies that are implementing MFA, reflecting on lessons learned from agencies around the country and from CJI-related technology vendors. ## Keywords\n\nauthentication; credentials; criminal justice information (CJI); identity; identity federation; law enforcement; multi-factor authentication (MFA); single sign-on (SSO). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of information other than national security-related information in federal information systems."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.4.1 Frequency of phishing simulations... 3.4.1 Frequency of phishing simulations... 3.4.1 Frequency of phishing simulations\n\nParticipants indicated how often their organizations conducted phishing simulations."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 2. Preliminaries.......................................................................... | 3 |\n| 2.1. Auxiliary Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 7 |\n| 3. Ascon Permutations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.1. Internal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.2. Constant-Addition Layer 𝑝 𝐶 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.3. Substitution Layer 𝑝 𝑆 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 9 |\n| 3.4. Linear Diffusion Layer 𝑝 𝐿 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 4. Authenticated Encryption Scheme: Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1. Specification of Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.1. Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.2. Decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\ners? 6. When a vulnerability in your software becomes public but a patch, update, or upgrade is not available, how do you recommend that customers protect their computing assets running your software?\nWill you provide an emergency mitigation to prevent vulnerability exploitation while maintaining most or all software functionality? 7. When your software is patched or updated, how disruptive will that be to the operating software? For instance, will it require restarting the software, rebooting the asset on which the software is running, etc.? 8. How do you test your patches before release? How often do customers experience significant issues with your patches? Do you provide rollback capabilities for uninstalling patches?"}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8558/final, including related content, potential updates, and document history.\n\nThe team identified that firmware updates are critical to the cybersecurity of a smart teddy bear. Team participants also noted that privacy was also noted as a critical concern. The team envisioned utilizing videos and physical manuals to communicate with customers and users. They developed two manuals: one for parents and another for children, allowing for a more targeted audience approach. The adult manual was detailed and focused on salient tips and direct, easy access to resources. The child manual was designed around the idea that the child could help drive cybersecurity and that the product could help teach good cyber hygiene. For example, the eyes of the bear can glow red when an update is needed, prompting the child to seek help, as the team describes in their mock-up of the story book in Fig. 2."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.2.1 Scenario\n\nThe following scenario was simulated to test the architecture's defense against destructive malware."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Machine Learning for Access Control Policy Verification:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide?"}, {"role": "assistant", "content": "## NISTIR 8420B\n\n## The Federal Cybersecurity Awareness Workforce\n\nProfessional Backgrounds, Knowledge, Skills, and Development Activities\n\nJulie Haney Jody Jacobs Susanne Furman Fernando Barrientos\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8420B\n\n\n\n## NISTIR 8420B\n\n## The Federal Cybersecurity Awareness Workforce\n\nProfessional Backgrounds, Knowledge, Skills, and Development Activities\n\nJulie Haney Jody Jacobs Susanne Furman Fernando Barrientos Information Access Division Information Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8420B\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8420B 36 pages (March 2022)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8420B\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 8)"}, {"role": "assistant", "content": "ose. ## NIST SPECIAL PUBLICATION 1800-34B\n\n## Validating the Integrity of Computing Devices\n\n## Volume B:\n\nApproach, Architecture, and Security Characteristics\n\nTyler Diamond* Nakia Grayson William T.\nPolk Andrew Regenscheid Murugiah Souppaya\n\nNational Institute of Standards and Technology Information Technology Laboratory\n\n## Christopher Brown\n\nThe MITRE Corporation McLean, Virginia\n\n## Karen Scarfone\n\nScarfone Cybersecurity Clifton, Virginia\n\n*Former employee; all work for this publication was done while at employer\n\n## December 2022\n\nFINAL\n\nThis publication is available free of charge from https://doi.org/10.6028/NIST.SP.1800-34\n\n\n\n## DISCLAIMER\n\nCertain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. National Institute of Standards and Technology Special Publication 1800-34B, Natl. Inst. Stand. Technol. Spec. Publ. 1800-34B, 72 pages, (December 2022), CODEN: NSPUE2\n\n## FEEDBACK\n\nAs a private-public partnership, we are always seeking feedback on our practice guides. We are particularly interested in seeing how businesses apply NCCoE reference designs in the real world. If you have implemented the reference design, or have questions about applying it in your environment, please email us at supplychain-nccoe@nist.gov. All comments are subject to release under the Freedom of Information Act."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nScope and Applicability of SP 800-171. The security requirements in NIST SP 800-171 are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. Appropriately scoping requirements is an important factor in determining protection-related investment decisions and managing security risks for your business. You may limit the scope of the security requirements by isolating the system components in a separate security domain. Isolation can be achieved by implementing subnetworks with firewalls or other boundary protection devices. Security domains may employ physical separation, logical separation, or a combination of both. This approach can provide adequate security for CUI and avoid increasing the organization's security posture beyond what it requires for protecting its missions, operations, and assets.\n\n- Permit only qualified and authorized individuals to access the system for the purpose of initiating changes. Access restrictions include physical and logical access controls, software libraries, workflow automation, media libraries, abstract layers (i.e., changes implemented into external interfaces rather than directly into the system), and change windows (i.e., changes occur only during specified times)."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n2.3.3. Reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n2.3.3. Reauthentication\nPeriodic reauthentication of subscriber sessions SHALL be performed, as described in\nSec. 5.2. At AAL3, the overall timeout for reauthentication SHALL be no more than 12\nhours. The inactivity timeout SHOULD be no more than 15 minutes. Unlike AAL2, AAL3\nreauthentication requirements are the same as for initial authentication at AAL3.\n\nThe out-of-band device SHOULD be uniquely addressable by the verifier. Communication\nover the secondary channel SHALL use approved encryption unless sent via the public\nswitched telephone network (PSTN). For additional authenticator requirements that are\nspecific to using the PSTN for out-of-band authentication, see Sec. 3.1.3.3."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nAnother reason for monitoring the deployed patches is to see if the patched software's behavior changes after patching. As part of a layered security approach to mitigating supply chain risk, this might be helpful at detecting, responding to, and recovering from situations where the installed patch was itself compromised."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.1 (NIST 3.7.1)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.7.1 Global | 3. 3.7.1 Global by Data Base ; In this scheme, each data base is assigned a classification equal to that of the most sensitive data it contains."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.7.1", "cmmc_practice_id": "MA.L2-3.7.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.1.2, 3. 3.1.2, 3. 3.1.2 SP800161 : SA-4, SA-9, SA-9(1), SA-9(3), SA-10, SA-10(1), SA-15, SR-3, SR-4, SR-5 SP800181 : T0203, T0415; K0039; S0374; A0056, A0161 |\n| Implement Roles and Responsibilities (PO."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 4)"}, {"role": "assistant", "content": "cation provides practical guidance and resources that can be used by regulated entities of all sizes to safeguard ePHI and better understand the security concepts discussed in the HIPAA Security Rule.\n## Keywords\n\nadministrative safeguards; Health Insurance Portability and Accountability Act; implementation specification; physical safeguards; risk assessment; risk management; Security Rule; standards; technical safeguards. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Document Conventions\n\nThe terms 'should' and 'should not' indicate that, among several possibilities, one is recommended as particularly suitable without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. The terms 'may' and 'need not' indicate a course of action permissible within the limits of the publication. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical, or causal."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "s\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV.\n5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nRISK MANAGEMENT\n\nOrganizations must exercise due diligence in managing information security and privacy risk. This\nis accomplished, in part, by establishing a comprehensive risk management program that uses\nthe flexibility inherent in NIST publications to categorize systems, select and implement security\nand privacy controls that meet mission and business needs, assess the effectiveness of the\ncontrols, authorize the systems for operation, and continuously monitor the systems. Exercising\ndue diligence and implementing robust and comprehensive information security and privacy risk\nmanagement programs can facilitate compliance with applicable laws, regulations, executive\norders, and governmentwide policies. Risk management frameworks and risk management\nprocesses are essential in developing, implementing, and maintaining the protection measures\nnecessary to address stakeholder needs and the current threats to organizational operations\nand assets, individuals, other organizations, and the Nation. Employing effective risk-based\nprocesses, procedures, methods, and technologies ensures that information systems and\norganizations have the necessary trustworthiness and resiliency to support essential mission and\nbusiness functions, the U.S. critical infrastructure, and continuity of government. vi\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\n\n\n## NIST Interagency Report NIST IR 8562\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nKaterina N. Megas Michael Fagan Barbara Cuthill Brad Hoehn Evie Petrella\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8562\n\n\n\n## NIST Interagency Report NIST IR 8562\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nKaterina N. Megas Michael Fagan Barbara Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nBrad Hoehn HII\n\nEvie Petrella Electrosoft Services, Inc. This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8562\n\nApril 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nNational Institute of Standards and Technology\n\nCraig S. Burkhardt, Acting NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-03-21\n\n## How to Cite this NIST Technical Series Publication\n\nMegas K, Fagan M, Cuthill B, Hoehn N, and Petrella E (2025) Summary Report for 'Workshop on Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.4.2 | Audit Planning/Prioritization Process | Audit Planning/Prioritization Process | 51 |\n| | 3. 3.4.2 Interview Key Participants Customize | Audit Objectives | 83 |\n| | 4. 3.4.2 | Contracting/Purchase Audit Considerations | 85 |\n| | 4."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 6)"}, {"role": "assistant", "content": "forming the processes associated with implementing this guide. To provide comments or to learn more by arranging a demonstration of this example implementation, contact the NCCoE at ds-nccoe@nist.gov.\n## TECHNOLOGY PARTNERS/COLLABORATORS\n\nOrganizations participating in this project submitted their capabilities in response to an open call in the Federal Register for all sources of relevant security capabilities from academia and industry (vendors and integrators). The following respondents with relevant capabilities or product components (identified as 'Technology Partners/Collaborators' herein) signed a Cooperative Research and Development Agreement (CRADA) to collaborate with NIST in a consortium to build this example solution. \n\n\n\n\n\n\n\n\n\n\n\nCertain commercial entities, equipment, products, or materials may be identified by name or company logo or other insignia in order to acknowledge their participation in this collaboration or to describe an experimental procedure or concept adequately. Such identification is not intended to imply special status or relationship with NIST or recommendation or endorsement by NIST or NCCoE; neither is it\n\nintended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. The National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity challenges. Through this collaboration, the NCCoE develops modular, adaptable example cybersecurity solutions demonstrating how to apply standards and best practices using commercially available technology."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 8)"}, {"role": "assistant", "content": "ederal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui.\n- NIST is responsible for developing and publishing the security requirements for the protection of CUI. How requirements are mandated, and any compliance issues related to nonfederal implementation of SP 800-171, are the responsibility of the federal agency requiring its use , as expressed in a specific contract or agreement. ## Additional NIST Resources\n\n- NIST's Protecting CUI Frequently Asked Questions\n- Changes Between SP 800-171 Rev. 2 and Rev. 3 (.xlsx)\n- The NIST Cybersecurity and Privacy Reference Tool (CPRT) provides online, interactive versions of the updated security requirements in SP 800-171, Revision 3 and the updated assessment procedures in SP 800-171A, Revision 3\n- Event Recording: ' CUI Security Requirements Workshop ,' which provides a general overview of SP 800 -171 and SP 800-171A\n- NIST Small Business Cybersecurity Corner\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n## What to Expect\n\nThe following pages delve deeper into the SP 800-171 R3 publication to provide more details for those responsible for implementing the requirements 3 . The following pages cover:\n\n\n\nPage 8: Key differences between SP 800-171 R2 and R3. Pages 9-10: General tips for getting started. Pages 11-28: Tips for getting started, broken out by Control Family. 3 We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST.\n\nThe overall and inactivity timeout expiration limits depend on several factors, including\nthe AAL of the session, the environment in which the session is conducted (e.g., whether\nthe subscriber is in a restricted area), the type of endpoint being used (e.g., mobile\napplication, web-based), whether the endpoint is a managed device,7 and the nature\nof the application itself. The limits MAY also be extended when higher security session\nmaintenance technologies (e.g., device-bound mechanisms) are used. Agencies SHALL\nestablish and document the inactivity and overall time limits being enforced in a system\nsecurity plan, such as that described in [SP800-39]. Detailed requirements for each AAL\nare given in Sec. 2.1.3, Sec. 2.2.3, and Sec. 2.3.3."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\n| 3.14 MINIMUM SECURITY CONTROLS............................................................................................ | 24 |\n|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 3.15 COMPLETION AND APPROVAL DATES .................................................................................... | 26 |\n| 3.16 ONGOING SYSTEM SECURITY PLAN MAINTENANCE .............................................................. | 26 |\n| APPENDIX A: SAMPLE INFORMATION SYSTEM SECURITY PLAN TEMPLATE...... 27 | APPENDIX A: SAMPLE INFORMATION SYSTEM SECURITY PLAN TEMPLATE...... 27 |\n| APPENDIX B: GLOSSARY.......................................................................................................... 31 | APPENDIX B: GLOSSARY.......................................................................................................... 31 |\n| APPENDIX C: REFERENCES..................................................................................................... 41 | APPENDIX C: REFERENCES....................................................................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does A Data Structure for Integrity Protection with Erasure Capability provide?"}, {"role": "assistant", "content": "## A Data Structure for Integrity Protection with Erasure Capability\n\nD. Richard Kuhn Computer Security Division Information Technology Laboratory\n\nMay 20, 2022\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.CSWP.25\n\nThis publication is a final version of a draft cybersecurity white paper originally published on May 31, 2018: https://csrc.nist.gov/publications/detail/white-paper/2018/05/31/data-structure-for-integrityprotection-with-erasurecapability/draft. \n\n## Abstract\n\nThis document describes a data structure, referred to as a data block matrix, that supports the ongoing addition of hash-linked records while also allowing for the deletion of arbitrary records, thereby preserving hash-based integrity assurance that other blocks are unchanged. The block matrix data structure may have utility for incorporation into applications requiring integrity protection that currently use permissioned blockchains. This capability could for example be useful in meeting privacy requirements such as the European Union General Data Protection Regulation (GDPR), which requires that organizations make it possible to delete all information related to a particular individual, at that person's request. ## Keywords\n\nblockchain; computer security; data structure; distributed ledger; hash; integrity protection. ## Patent and Licensing\n\nThe data block matrix technology (US Patent #11,175,826) is available to be licensed . For information on patent and licensing see NIST Technology Partnerships Office (TPO). Parties interested in licensing a NIST-owned invention may contact TPO, or may complete a research license application or commercial use license application. Instructions on how to submit the license application are provided at the end of each application. When a license application is received, TPO will contact you regarding the licensing process and to obtain additional information that may be necessary for the application process."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Developing Security Plans for Federal Information Systems provide? (Part 8)"}, {"role": "assistant", "content": "|\n| 3.4 AUTHORIZING OFFICIAL ..........................................................................................................\n| 20 |\n| 3.5 OTHER DESIGNATED CONTACTS.............................................................................................. | 20 |\n| 3.6 ASSIGNMENT OF SECURITY RESPONSIBILITY ........................................................................... | 21 |\n| 3.7 SYSTEM OPERATIONAL STATUS............................................................................................... | 21 |\n| 3.8 INFORMATION SYSTEM TYPE ................................................................................................... | 21 |\n| 3.9 GENERAL DESCRIPTION/PURPOSE............................................................................................ | 21 |\n| 3.10 SYSTEM ENVIRONMENT ........................................................................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 8)"}, {"role": "assistant", "content": "xcellent coordination activities while the workshop sessions were in progress; Dennis K. Branstad for the photographs taken during the workshop; and Tina Faecke for her steadfast typing support. Z. G.\nRuthberg, Editor\n\n## TABLE OF CONTENTS\n\n| FOREWORD | FOREWORD | FOREWORD | HI |\n|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------|\n| ABSTRACT | ABSTRACT | ABSTRACT | Iv |\n| ACKNOWLEDGEtENTS | ACKNOWLEDGEtENTS | ACKNOWLEDGEtENTS | Iv |\n| EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | xlll |\n| PART T: INTRODUCTION | PART T: INTRODUCTION | PART T: INTRODUCTION | 1-] |\n| 1."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\novided by stateful inspection, this has capabilities related to finding hidden threats within the data stream, such as attempts at data exfiltration, violations of content policies, malware, and more.\n- Threat detection and response: Modern firewalls can gather and analyze enough data across multiple packets and sessions to detect threats and security incidents targeted at a particular system or a family of systems. These data from multiple firewalls can also be directed toward security information and event management (SIEM) and correlated with data from other security tools and IT systems to detect enterprise-wide attacks that span multiple systems and network layers. In addition, these data can be used to understand evolving threats and define new access rules, attack patterns, and defensive strategies [6]. - Logging and auditing capabilities: Logging and auditing capabilities result in the construction of network events that can be used to identify patterns of performance and security issues. - Access control functions: Access control functions enforce granular sophisticated access control policies. - Multiple locations and functions: Firewalls reside at different locations to perform different functions. Firewalls at the network edge perform the network perimeter protection function by filtering disallowed sources and destinations and blocking the packets of potential threats. Firewalls inside a data center can segment the internal network to prevent the lateral movement of traffic and isolate sensitive resources (e.g., services and data stores). Device-based firewalls prevent malicious traffic in and out of endpoints. - Open Application Programming Interfaces (APIs): These enable integration with many networking products that provide additional security capabilities."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## 3.3. Analyze Stages of Hardware Development Life Cycle for Exploitability of the Threat"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nThe National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to\nstrengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this\nend, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and\ntechnological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to pro-\nmote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute\nfor Applied Technology, the Institute for Computer Sciences and Technology, the Office for Information Programs, and the\nOffice of Experimental Technology Incentives Program.\n\nTHE INSTITUTE FOR BASIC STANDARDS provides the central basis within the United States of a complete and consist-\nent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essen-\ntial services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry,\nand commerce. The Institute consists of the Office of Measurement Services, and the following center and divisions:\n\nAnalytical Chemistry — Polymers — Metallurgy — Inorganic Materials — Reactor Radiation — Physical Chemistry.\nTHE INSTITUTE FOR APPLIED TECHNOLOGY provides technical services developing and promoting the use of avail-\nable technology; cooperates with public and private organizations in developing technological standards, codes, and test meth-\nods; and provides technical advice services, and information to Government agencies and the public. The Institute consists of\nthe following divisions and centers:"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.5.1 | | |\n| | 3. 3.5.1 Testing\n\nISCP testing is a critical element of a viable contingency capability."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 6)"}, {"role": "assistant", "content": "| General.......................................................................................................................\n2 |\n| | Modifications .............................................................................................................. 2 |\n| | Security Requirements .................................................................................................... 3 |\n| | Changes to ISO/IEC 24759 Section 6.14 and ISO/IEC 19790 Annex B Requirements3 |\n| | Documentation Requirement Additions....................................................................... 4 |\n| | Documentation Input, Structure, and Formatting......................................................... 6 |\n| Appendix A. Document Revisions......................................................................................24 | Appendix A. Document Revisions......................................................................................24 |\n| Appendix B. List of Symbols, Abbreviations, and Acronyms...........................................25 | Appendix B."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThe system component inventory includes system-specific information required for component accountability and to provide support to identify, control, monitor, and verify configuration items in accordance with the authoritative source. The information necessary for effective accountability of system components includes the system name, hardware and software component owners, hardware inventory specifications, software license information, software version numbers, andfor networked components-the machine names and network addresses. Inventory specifications include the manufacturer, supplier information, component type, date of receipt, cost, model, serial number, and physical location. Organizations also use automated mechanisms to implement and maintain authoritative (i.e., up-to-date, complete, accurate, and available) baseline configurations for systems that include hardware and software inventory tools, configuration management tools, and network management tools. Tools can be used to track version numbers on operating systems, applications, types of software installed, and current patch levels.\n\n- 3.11.6e Assess, respond to, and monitor supply chain risks associated with organizational systems and system components.\n\nSupply chain events include disruption, use of defective components, insertion of counterfeits, theft, malicious development practices, improper delivery practices, and insertion of malicious code. These events can have a significant impact on a system and its information and, therefore, can also adversely impact organizational operations (i.e., mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation. The supply chain-related events may be unintentional or malicious and can occur at any point during the system life cycle. An analysis of supply chain risk can help an organization identify systems or components for which additional supply chain risk mitigations are required."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 10)"}, {"role": "assistant", "content": "eiving input from stakeholders. It represents a coordinated effort to produce a definition of common capabilities not an exhaustive list. The core baseline is intended to be a flexible starting point.\nManufacturers and supporting parties can use the IoT non-technical supporting capability core baseline in the context of the activities in NISTIR 8259 and that is appropriate to them. It is important to note that manufacturers and supporting third parties should implement the non-technical supporting capabilities that support the risk management needs of customers of the IoT device within its intended digital ecosystem. This will then result in each of the individual non-technical supporting capabilities in the baseline being implemented in a manner consistent with the needs and expectations of those customers. If additional supporting capabilities are necessary to enable secure use of the devices, organizations are encouraged to consider defining additional supporting capabilities that better suit their use case(s). 1 One resource supporting both Information Reception and Information Dissemination to others in the ecosystem about vulnerabilities is found in Draft NIST SP 800-216: Federal Vulnerability Disclosure Guidelines [17] . This document recommends guidance for establishing a federal vulnerability disclosure framework and highlights the importance of proper handling of vulnerability reports and communicating the minimization or elimination of vulnerabilities. ## 2 The IoT Non-Technical Supporting Capability Core Baseline\n\nTable 1 defines the IoT device non-technical supporting capability core baseline, which, in combination with the device cybersecurity (technical) capability core baseline of NISTIR 8259A, can make it possible to secure an IoT device."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nLoss of visibility into received network traffic can impair critical functions such as network and application performance monitoring, security logging, and diagnostics, which undermines the effectiveness of network and security operations and engineering teams. Without the ability to decrypt network data for deep packet inspection (DPI), monitoring, or diagnostics, enterprises will rely on endpoint devices for performance and security information. The incoming network data stream can contain information or perspectives that individual endpoint devices, like workstations, servers, etc., that support a security client are not capable of providing. Reliance on endpoints in the absence of visibility into network traffic introduces security and operational risks for network and data center operations in the following ways :\n\n- Visibility into network data is even more critical when the endpoints are having problems or are in any way compromised. A degraded or compromised endpoint device may fail to report incidents that can be detected within the incoming network data stream. -  Visibility into network data is essential to enable the ability to discover issues that involve multiple platforms or multiple organizations within the enterprise. -  Visibility into network data is required when sessions span across devices that do not log information well or at all. Even with devices that do logging well, it is frequently necessary to augment that logging by having visibility to related network data. Even where endpoint data is adequate, it still needs to be collected, consolidated, centralized, and correlated. -  When logging of network traffic is turned off or reduced, which is often the case, visibility into network data may be the only alternative to see anomalies."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 2)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-12-19 Supersedes NIST Internal Report 8450 (September 2023) https://doi.org/10.6028/NIST.IR.8450\n\n## How to Cite this NIST Technical Series Publication:\n\nHu VC (2023) Overview and Considerations of Access Control Based on Attribute Encryption. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8450-upd1, Includes updates as of December 20, 2023. https://doi.org/10.6028/NIST.IR.8450-upd1\n\n## Author ORCID iDs\n\nVincent C. Hu: 0000-0002-164 6 -0584\n\n## Contact Information\n\nir8450-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nEncryption technology can be incorporated into access control mechanisms based on user identities, user attributes, or resource attributes. Traditional public-key encryption requires different data to have different keys that can be distributed to users who satisfy perspective access control policies along with the encrypted version of the data. However, some distributed or pervasive system environments wish to avoid the public-key encryption's all-or-nothing data access limitation when considering their performance requirements."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "etary of Commerce, OMB Director, or any other federal official. This\npublication may be used by nongovernmental organizations on a voluntary basis and is not\nsubject to copyright in the United States.\nAttribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-53A Revision 5\nNatl. Inst. Stand. Technol. Spec. Publ. 800-53A, Rev. 5, 733 pages (January 2022)\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53Ar5\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an\nexperimental procedure or concept adequately. Such identification is not intended to imply\nrecommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or\nequipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities. The information in this publication, including\nconcepts, practices, and methodologies may be used by federal agencies even before the completion of\nsuch companion publications. Thus, until each publication is completed, current requirements, guidelines,\nand procedures, where they exist, remain operative. For planning and transition purposes, federal\nagencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the designated public comment periods\nand provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at\nhttps://csrc.nist.gov/publications."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 2. Preliminaries.......................................................................... | 3 |\n| 2.1. Auxiliary Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 7 |\n| 3. Ascon Permutations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.1. Internal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.2. Constant-Addition Layer 𝑝 𝐶 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.3. Substitution Layer 𝑝 𝑆 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 9 |\n| 3.4. Linear Diffusion Layer 𝑝 𝐿 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 4. Authenticated Encryption Scheme: Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1. Specification of Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.1. Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.2. Decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|\n| that they can be remediated more quickly in accordance with risk, reducing the window of opportunity for attackers. | and third-party components that the software uses, and investigate all credible reports."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n| 1 | Summary..............................................................................................1 | Summary..............................................................................................1 | |-----|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | 1.2 | Solution..........................................................................................................................2 | | | 1.3 | Benefits..........................................................................................................................3 | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | 2.1 | Typographic Conventions..............................................................................................5 | | 3 | Approach .............................................................................................6 | Approach .............................................................................................6 | | | 3.1 | Audience........................................................................................................................6 | | | 3.2 | Scope .............................................................................................................................6 | | | 3.3 | Assumptions..................................................................................................................7 | | | 3.4 | Risk Assessment ............................................................................................................7 | | | 3.4.1 | Risk................................................................................................................................8 | | | | 3.4.2 Security Control Map....................................................................................................9 | | | 3.5 Technologies................................................................................................................13 | 3.5 Technologies................................................................................................................13 | | 4 | Architecture .......................................................................................16 | Architecture .......................................................................................16 | | | 4.1 Architecture Description .............................................................................................16 | 4.1 Architecture Description .............................................................................................16 | | | 4.1.1 | High-Level Architecture ..............................................................................................16 | | | 4.1.2 | Architecture Components...........................................................................................17 | | 5 | Security Characteristic Analysis..........................................................20 | Security Characteristic Analysis..........................................................20 | | | 5.1 Assumptions and Limitations | ......................................................................................20 | | | 5.2 Build | Testing................................................................................................................20 | | | 5.3 | Scenarios and Findings................................................................................................21 | | | 5.3.1 | Ransomware via Web Vector and Self-Propagation...................................................21 | | | 5.3.2 | Destructive Malware via USB Vector..........................................................................22 | | |"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................4 |\n| 2. HIPAA Security Rule .......................................................................................................................9 |\n| 3. Risk Assessment Guidance............................................................................................................14 |\n| 4. Risk Management Guidance .........................................................................................................24 |\n| 5. Considerations When Implementing the HIPAA Security Rule........................................................28 |\n| 5.1.2. Assigned Security Responsibility (§ 164.308(a)(2)) ....................................................................35 |\n| 5.1.3. Workforce Security (§ 164.308(a)(3)).........................................................................................36 |\n| 5.1.4. Information Access Management (§ 164.308(a)(4)) ..................................................................38 |\n| 5.1.5. Security Awareness and Training (§ 164.308(a)(5)) ...................................................................41 |\n| 5.1.6. Security Incident Procedures (§ 164.308(a)(6)) .........................................................................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n## Incident Response Recommendations and Considerations for Cybersecurity Risk Management\n\n## Incident Response Recommendations and Considerations for Cybersecurity Risk Management\n\nNelson A, Rekhi S, Souppaya M, Scarfone K (2025) Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-61r3. https://doi.org/10.6028/NIST.SP.800-61r3"}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nOrganizations are concerned about the risks associated with products and services that may potentially contain malicious functionality, are counterfeit, or are vulnerable due to poor manufacturing and development practices within the supply chain. These risks are associated with an enterprise's decreased visibility into and understanding of how the technology they acquire is developed, integrated, and deployed or the processes, procedures, standards, and practices used to ensure the security, resilience, reliability, safety, integrity, and quality of the products and services.\n\nThis publication provides guidance to organizations on identifying, assessing, and mitigating cybersecurity risks throughout the supply chain at all levels of their organizations. The publication integrates cybersecurity supply chain risk management (C-SCRM) into risk management activities by applying a multilevel, C-SCRM-specific approach, including guidance on the development of C-SCRM strategy implementation plans, C-SCRM policies, C-SCRM plans, and risk assessments for products and services."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n, September 2014. https://doi.org/10.6028/NIST.SP.800-56Br1\n- [SP 800-56C] Special Publication 800-56C Revision 1, Recommendation for Key Derivation Methods in Key Establishment Schemes , April 2018.\nhttps://doi.org/10.6028/NIST.SP.800-56Cr1\n- [SP 800-57] Special Publication 800-57 Part 1 Revision 4, Recommendation for Key Management , January 2016. https://doi.org/10.6028/NIST.SP.800-57pt1r4\n- [SP 800-89] Special Publication (SP) 800-89, Recommendation for Obtaining Assurances for Digital Signature Applications , November 2006. https://doi.org/10.6028/NIST.SP.800-89\n- [SP 800-90] Special Publication 800-90 series: Special Publication 800-90A Revision 1, Recommendation for Random Number Generation Using Deterministic Random Bit Generators , June 2015. https://doi.org/10.6028/NIST.SP.800-90Ar1"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 6)"}, {"role": "assistant", "content": "............................... 1 | Executive Summary.................................................................................................................\n1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Introduction ...................................................................................................................... | Introduction ...................................................................................................................... | 2 |\n| | Background - Zero Trust Principles and Zero Trust Architecture................................"}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.3.1 Education... 3.3.1 Education... 3.3.1 Education..."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\ns to interested specialists in the academic and private sectors. Those wishing to receive notices of publications in this series should complete and return the form at the end of this publicaton. | 3.\n| POLICY | AND CONTROL STANDARDS | 3-6 |\n|------|----------------|-------------------------------------------------------------------------------------------------------|-----------|\n| | 3.1 | General | 3-6 |\n| | 3.2 | Assessing Security Safeguards | 3-6 |\n| | 3.3 | Establishing Control Standards | 3-6 |\n| | 3.4 | Require a Plan to Implement Controls | 3-7 |\n| | 3.5 | Establish Personnel Security Policies | 3-7 |\n| 4. | ALLOCATE | RESOURCES | 3-7 |\n| | 4.1 | General | 3-7 3-8 |\n| 5. | REPORT | ON SECURITY | |\n| | 5.1 | General | 3-8 |\n| Fig. | 1 | Responsibilities and Duties to Provide Security for Data Processing System .."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Updates to the Security Requirements and Families\n\n- It is important to identify permitted and prohibited actions regarding software installation when users have the ability to install software on organizational systems. Permitted software installations could include updates and security patches to existing software and downloading new applications from organizationapproved 'app stores.' Companies might prohibit employees from downloading certain programs, services, software versions, etc ."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 3)"}, {"role": "assistant", "content": "ering — Center for Building Technology; Structures, Materials, and Safety; Building\nEnvironment; Technical Evaluation and Application — Center for Fire Research: Fire Science; Fire Safety Engineering.\nTHE INSTITUTE FOR COMPUTER SCIENCES AND TECHNOLOGY conducts research and provides technical services\ndesigned to aid Government agencies in improving cost effectiveness in the conduct of their programs through the selection,\nacquisition, and effective utilization of automatic data processing equipment: and serves as the principal focus wthin the exec-\nutive branch for the development of Federal standards for automatic data processing equipment, techniques, and computer\nlanguages. The Institute consist of the following divisions:\n\nComputer Services — Systems and Software — Computer Systems Engineering — Information Technology. THE OFFICE OF EXPERIMENTAL TECHNOLOGY INCENTIVES PROGRAM seeks to affect public policy and process\nto facilitate technological change in the private sector by examining and experimenting with Government policies and prac-\ntices in order to identify and remove Government-related barriers and to correct inherent market imperfections that impede\nthe innovation process. THE OFFICE FOR INFORMATION PROGRAMS promotes optimum dissemination and accessibility of scientific informa-\ntion generated within NBS; promotes the development of the National Standard Reference Data System and a system of in-\nformation analysis centers dealing with the broader aspects of the National Measurement System; provides appropriate services\nto ensure that the NBS staff has optimum accessibility to the scientific information of the world. The Office consists of the\nfollowing organizational units:\n\nOffice of Standard Reference Data — Office of Information Activities — Office of Technical Publications — Library —\nOffice of International Standards — Office of International Relations."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 5)"}, {"role": "assistant", "content": "ation 800-53A; NIST Special Publication 800-171; NIST Special Publication 800-172; NIST Special Publication 800-172A; nonfederal organization; nonfederal system; security assessment; security control.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgments\n\nThe authors wish to recognize the research staff from the NIST Computer Security Division and the Applied Cybersecurity Division for their contributions in helping to improve the content of this publication. A special note of thanks is given to Jeff Brewer, Jim Foti, Cristina Ritfeld, Isabel Van Wyk, and the NIST web team for their outstanding administrative support, and to Kevin Dulany, Chris Enloe, and Ned Goren for their technical review and feedback. The authors also wish to acknowledge the contributions from individuals and organizations in the public and private sectors - nationally and internationally - whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 5)"}, {"role": "assistant", "content": "for details about the SP 800-140x series publications and their relationships to ISO/IEC 19790 and ISO/IEC 24759. ## Audience\n\nThis document is intended for use by vendors, testing labs, and the CMVP.\n## Table of Contents\n\n| | Scope ................................................................................................................................ 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Normative references....................................................................................................... 1 |\n| | Terms and definitions ......................................................................................................"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nDevice cybersecurity capabilities are cybersecurity features or functions that computing devices provide through their own technical means (i.e., device hardware and software). This publication defines an Internet of Things (IoT) device cybersecurity capability core baseline, which is a set of device capabilities generally needed to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. Internet of Things (IoT) devices often lack built-in device cybersecurity capabilities, as well as non-technical support relevant to cybersecurity. Customers can use this type of information to help mitigate cybersecurity risks related to the IoT devices and their use. The wide range of connectivity possible for IoT devices, and the ability for these devices to interact with the physical world, means securing these devices often becomes a priority; but it is a challenge for customers when they are not adequately supported."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n| 1 | | 1.1 | | Purpose and Scope...................................................................................................1 | | | | 1.2 | Audience ...................................................................................................................1 | | | | 1.3 | Document Structure | ..................................................................................................1 | | 2."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 5)"}, {"role": "assistant", "content": "la empresa o personal). La autenticación y la autorización (tanto del sujeto como del dispositivo) son funciones discretas que se realizan antes de establecer una sesión con un recurso de la empresa.\nLa confianza cero es una respuesta a las tendencias de las redes empresariales que incluyen usuarios remotos, dispositivos personales (BYOD, por su nombre en inglés bring-your-owned-device ) y activos basados en la nube que no se encuentran dentro de los límites de una red propiedad de la empresa. La confianza cero se centra en proteger los recursos (activos, servicios, flujos de trabajo, cuentas de red, etc.), no los segmentos de red, ya que la ubicación de la red ya no se considera el componente principal de la postura de seguridad del recurso. Este documento contiene una definición abstracta de la arquitectura de confianza cero (ZTA) y ofrece modelos generales de despliegue y casos de uso en los que la confianza cero podría mejorar la postura global de seguridad de las tecnologías de la información de una empresa. ## Palabras claves\n\nArquitectura, ciberseguridad, empresa, seguridad de la red, confianza cero. ## Agradecimientos\n\nEste documento es fruto de la colaboración entre múltiples agencias federales y está supervisado por el Consejo Federal de CIO. El subgrupo de arquitectura es responsable del desarrollo de este documento, pero hay personas concretas que merecen reconocimiento. Entre ellas se encuentran Greg Holden, director del proyecto ZTA del Consejo Federal de CIO; Alper Kerman, director del proyecto ZTA del NIST/Centro Nacional de Ciberseguridad; y Douglas Montgomery."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.2.5. 3.2.5."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nOffice of Management and Budget, Circular Number A-130: Managing Information as a Strategic Resource [13]\n- NIST SP 800-61 Rev. 2: Computer Security Incident Handling Guide [14]\n- NIST SP 800-83 Rev.\n1: Guide to Malware Incident Prevention and Handling for Desktops and Laptops [15]\n- NIST SP 800-150: Guide to Cyber Threat Information Sharing [16]\n- NIST SP 800-184: Guide for Cybersecurity Event Recovery [17]\n\n| Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | Standards & Best Practices | Standards & Best Practices |\n|--------------------------------|--------------------------------------------|----------------------------------------------------------------------------------------------------|---------------------------------------------------|------------------------------|------------------------------|\n| Function | Category | Subcategory | NIST SP 800- 53 R4 | ISO/IEC 27001:2013 | NIST SP 800- 181 |\n| | Security Con- tinuous Moni- toring (DE.CM) | DE.AE-5: Incident alert thresholds are estab- lished. | IR-4, IR-5, IR-8 | A.16.1.4 | PR-CIR-001 |\n| | | DE.CM-1: The network is monitored to detect po- tential cybersecurity events. | AC-2, AU- 12, CA-7, CM-3, SC-5, SC-7, SI-4 | | OM-NET-001 |\n| | | DE.CM-3: Personnel ac- tivity is monitored to de- tect potential cybersecu- rity events."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 8)"}, {"role": "assistant", "content": "ware development practices, express their secure software development requirements to third-party suppliers using SSDF conventions, and acquire software that meets the practices described in the SSDF.\nUsing the SSDF helps organizations to meet the following secure software development recommendations:\n\n- Organizations should ensure that their people, processes, and technology are prepared to perform secure software development. - Organizations should protect all components of their software from tampering and unauthorized access. - Organizations should produce well-secured software with minimal security vulnerabilities in its releases. - Organizations should identify residual vulnerabilities in their software releases and respond appropriately to address those vulnerabilities and prevent similar ones from occurring in the future. The SSDF does not prescribe how to implement each practice. The focus is on the outcomes of the practices rather than on the tools, techniques, and mechanisms to do so. This means that the SSDF can be used by organizations in any sector or community, regardless of size or cybersecurity sophistication. It can also be used for any type of software development, regardless of technology, platform, programming language, or operating environment. The SSDF defines only a high-level subset of what organizations may need to do, so organizations should consult the references and other resources for additional information on implementing the practices. Not all practices are applicable to all use cases; organizations should adopt a risk-based approach to determine what practices are relevant, appropriate, and effective to mitigate the threats to their software development practices. Organizations can communicate how they are addressing the clauses from Section 4 of the President's Executive Order (EO) on 'Improving the Nation's Cybersecurity (14028)' by referencing the SSDF practices and tasks described in Appendix A."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Maintenance?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n1 | Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | Documentation : The ability for the manufacturer and/or the manufacturer's supporting entity, to create, gather, and store information relevant to cybersecurity of the IoT device prior to customer purchase, and throughout the development of a device and its subsequent lifecycle."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 5)"}, {"role": "assistant", "content": "he risk of side-channel analysis is more common in chip use scenarios, whereas the risk of a hardware Trojan is more common in the early stages of design and manufacturing, as shown in Fig. 1. Fig. 1.\nSecurity challenges in the semiconductor supply chain\n\n\n\nThis implies that threat analysis must consider both the type of threat and the various phases of the supply chain in which the threat is most effective. Moreover, one or more adversaries from different stages of supply chain can collaborate to compromise a hardware, which increases the severity of threats. Such insider threats are called collusion threats [6]. This document focuses on potential collusion risks in the hardware supply chain and is organized as follows:\n\n- Section 2 outlines the different phases of a semiconductor supply chain. - Section 3 describes a framework for analyzing supply chain threats. - Section 4 presents two real-life examples of hardware security threats to provide a comprehensive explanation of the proposed framework. - Section 5 concludes the discussion and provides directions for future work. ## 2. Stages of Semiconductor Supply Chain Stages\n\nThe first step in analyzing security concerns in the semiconductor supply chain is to outline the various stages of the supply chain and identify potential threats associated with each. There is no standard set of stages. However, for our analysis we will use seven stages as defined by Areno [7]. The user stage has been merged with the deployment stage since they have similar attack surfaces. An end-of-life stage has also been added to the seven stages originally defined by Areno [7]. A brief explanation of the stages is described below\n\n1. Concept: Concept stage is the birthplace of an Integrated Circuit (IC). At this stage, the goals and purpose of an integrated circuit (IC) are formulated, and the scope and target of a hardware component are discussed."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | ## 1 Introduction In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 8)"}, {"role": "assistant", "content": "....................25 | |\n| 6.\nConclusion.......................................................................................................................27 | 6. Conclusion.......................................................................................................................27 | |\n| References ..............................................................................................................................28 | References ..............................................................................................................................28 | |\n| Appendix A. Change Log ....................................................................................................34 | Appendix A. Change Log ....................................................................................................34 | |\n| List of Figures | List of Figures | List of Figures |\n| Fig. 1."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n| title: \"Apple macOS 11 (Big Sur) Test Baseline\" description: | This guide describes the prudent actions to take when securing a system against the Test Baseline. authors: | |=== |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| profile: |\n| - section: \"Authentication\" rules: - auth_pam_login_smartcard_enforce - auth_pam_su_smartcard_enforce - auth_pam_sudo_smartcard_enforce - auth_smartcard_allow - section: \"Auditing\" rules: - audit_acls_files_configure - audit_acls_files_mode_configure - audit_acls_folder_wheel_configure |\n\n- audit - OpenBSM 3\n- auth - Smartcard authentication\n- icloud - Apple's iCloud/Apple ID service\n- os - Rules to configure the operating system that do not fit into the other categories\n- pwpolicy - Password policy\n- system\\_settings or sysprefs - Settings controlled within the System Settings or System Preferences application\n\n```\ntitle: \"Limit SSHD to FIPS 140 Validated Ciphers\" discussion: | If SSHD is enabled, then it _MUST_ be configured to limit the ciphers to algorithms that are FIPS 140-validated. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets federal requirements. Operating systems utilizing encryption _MUST_ use FIPS-validated mechanisms for authenticating to cryptographic modules."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Access Control on NoSQL Databases provide? (Part 8)"}, {"role": "assistant", "content": "attributes for wide-column and document models......11 |\n| Fig. 9.\nExample of defining subject and object attributes for a graph model.......................................12 |\n| Fig. 10. Example of defining subject and object attributes for graph models using edges for permitted actions to embed an access control policy ........................................................................................13 |\n| Fig. 11. Generic resource federation model.......................................................................................23 |\n| Fig. 12. Resource federation scheme.................................................................................................23 |\n\n## Acknowledgments\n\nThe author would like to express his thanks to Isabel Van Wyk and Jim Foti of NIST for their detailed editorial review of both the public comment version and the final publication. ## Executive Summary\n\nNoSQL stands for 'not only SQL' or 'non-SQL,' which typically refer to any non-relational database that stores data in a format other than relational tables. It shifts away from relational database management systems (RDBMS) for dealing with enormous and constantly growing data and infrastructure needs and increasingly uses the Web 3.0 framework for big data and real-time web applications, including handling unstructured data like documents, emails, and social media. NoSQL databases are particularly useful for managing unstructured or very large data objects stored across distributed and cooperating devices."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\nof Standards and Technology (2024) Module-Lattic-Based Digital Signature Standard. (Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) NIST FIPS 204.\nhttps://doi.org/ 10.6028/NIST.FIPS.204\n- [5] National Institute of Standards and Technology (2024) Stateless Hash-Based Digital Signature Standard. (Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) NIST FIPS 205. https://doi.org/ 10.6028/NIST.FIPS.205\n- [6] Aragon N, Barreto PSLM, Bettaieb S, Bidoux L, Blazy O, Deneuville JC, Gaborit P, Ghosh S, Gueron S, Güneysu T, Melchor CA, Misoczk R, Persichetti E, Richter-Brockmann J, Sendrier N, Tillich JP, Vasseur V, Zémor G (2022) BIKE: Bit Flipping Key Encapsulation, 4th Round submission to the NIST's post-quantum cryptography standardization process. https://csrc.nist.gov/projects/post-quantum-cryptography/round-4-submiss ions. - [7] Bernstein DJ, Chou T, Cid C, Gilcher J, Lange T, Maram V, von Maurich I, Misoczki R, Niederhagen R, Persichetti E, Peters C, Sendrier N, Szefer J, Tjhai CJ, Tomlinson M, Wang W (2022) Classic McEliece algorithm specifications and supporting documentation, 4th Round submission to the NIST's post-quantum cryptography standardization process. https://csrc.nist.gov/projects/post-quantum-cryptography/round-4-s ubmissions. - [8] Melchor CA, Aragon N, Bettaieb S, Bidoux L, Blazy O, Deneuville JC, Gaborit P, Persichetti E, Zémor G, Bos J, Dion A, Lacan J, Robert JM, Veron P (2022) HQC algorithm specifications and supporting documentation, 4th Round submission to the NIST's post-quantum cryptography standardization process. https://csrc.nist.gov/projects /post-quantum-cryptography/round-4-submissions. - [9] Jao D, Azarderakhsh R, Campagna M, Costello C, Feo LD, Hess B, Jalali A, Koziel B, LaMacchia B, Longa P, Naehrig M, Renes J, Soukharev V, Urbanik D, Pereira G, Karabina K, Hutchinson A (2022) Supersingular Isogeny Key Encapsulation, 4th Round"}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. In 2015, Executive Order 13702 established the National Strategic Computing Initiative (NSCI) to maximize the benefits of high-performance computing (HPC) for economic competitiveness and scientific discovery. The ability to process large volumes of data and perform complex calculations at high speeds is a key part of the Nation's vision for maintaining its global competitive edge. Security is essential to achieving the anticipated benefits of HPC."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| Chapter 1."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\n## Proceedings of the Cybersecurity in CyberPhysical Systems Workshop, April 23 - 24, 2012\n\n## Proceedings of the Cybersecurity in CyberPhysical Systems Workshop, April 23 - 24, 2012\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| | Introduction ....................................................................................................1 | | |-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | 1.1 | | Purpose.......................................................................................................................1 | | | 1.2 | | Scope..........................................................................................................................2 | | | 1.3 | | Audience.....................................................................................................................3 | | | 1.4 | Document | Structure....................................................................................................4 | | | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 10)"}, {"role": "assistant", "content": "hings connected to the cyber world, there are known and unknown threats lurking that threaten the reliability and safety of these devices as well the privacy of patients who depends on them. ## II.\nRegulation of Implantable Medical Devices\n\nWithin the United States, the Food and Drug Administration (FDA) regulates the manufacturers, importers and resellers of these devices through the Center for Devices and Radiological Health (CDRH). A review of a sampling of FDA testing guidance (e.g. for implantable cardiac pacemakers) reveals that the 'tests are designed to reasonably assure safe and effective functioning of the pacemaker in the patient, according to written specifications of performance, and its survival under expected environmental conditions in the body and during storage, shipping and handling' [1]. FDA testing guidelines do not appear to address the resistance and resilience of these devices in the face of cyber attacks. ## III. Review of Recent Research\n\nHalperin et al have shown that a recent (2003) model of implantable cardioverter defibrillator (ICD), designed to com- municate wirelessly with an external programmer in the 175 kHz frequency range, is vulnerable to several radio-based attacks that threaten patient safety and privacy [2]. Several other research papers have pointed out similar vulnerabilities to cyber threats and possible mitigation mechanisms [3, 4, 5, 6]. ## IV. Security Analysis of IMDs\n\nIMDs are tiny computing platforms that run firmware in extremely power constrained environments. They offer data storage for static data (such as device information), relatively static data (such as patient identification, medical condition, therapy configuration) and dynamic data (such as recent patient readings and audit logs). IMDs offer wireless access for read and write operations to the data on the IMD (including the firmware) to a variety of stakeholders and roles. ## A."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nThe macOS Security Compliance Project (mSCP) provides resources that system administrators, security professionals, security policy authors, information security officers, and auditors can leverage to secure and assess macOS desktop and laptop system security in an automated way. This publication introduces the mSCP and gives an overview of the resources available from the project's GitHub site, which is continuously curated and updated to support each new release of macOS. The GitHub site provides practical, actionable recommendations in the form of secure baselines and associated rules. This publication also describes use cases for leveraging the mSCP content. Updates from the previous version of this publication mainly involve the new mSCP capability to create a custom benchmark by tailoring a baseline.\n\nThe authors wish to thank Jason Blake and Stephanie Roberts from NIST; Gary Gapinski, Elyse Anderson, and Joshua Glemza from NASA; and Jamie Richardson and Chris Stone from Apple for their contributions to the mSCP. The authors appreciate Bob McSulla and Ryan Jaynes from Tenable for developing audit files based on the mSCP, testing the baselines for different macOS versions, and contributing to Appendix C. The authors also thank Isabel Van Wyk from NIST for editing the document. Finally, portions of this document are based on content from the mSCP Wiki, so the work of all Wiki contributors is appreciated.\n\nThis document and the mSCP GitHub site are intended for system administrators, security professionals, policy authors, privacy officers, and auditors who have responsibilities involving"}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 8)"}, {"role": "assistant", "content": "............................................................................... | Executive Summary.....................................................................................................\n| iv |\n|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|\n| 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | |\n| | 1.1 | Purpose and Scope ........................................................................................"}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nAppViewX partnered with NETSCOUT to contribute a prototype TLS 1.3 key governance platform that it plans to formalize as an open industry standard. Key governance platform pairs with a Secure Key Orchestration initiative to secure and automate the management of all encryption keys across distributed and hybrid enterprise environments. The AppViewX Cloud -native Identity and Security Platform is used in critical infrastructures to reduce cybersecurity risk and meet security compliance requirements. Thanks to streamlined automation workflows, the AppViewX Platform supports enterprisewide central certificates and key governance and lifecycle management. The modular AppViewX Platform and its CERT+ and PKI+ products are delivered as a service to address digital a nd machine identity challenges. AppViewX provisions private and public trust certificates from any CA, alerts to expiring certificates, and automates renewals and revocations. CERT+ is an automated certificate lifecycle management (CLM) solution for simplified PKI and certificate management. PKI+ is a turnkey PKI-as-aService for private trust use cases that reduces PKI hardware requirements, simplifies private PKI architectures, and sets up tailored custom CAs. For more details, visit https://www.appviewx.com. DigiCert provides scalable TLS and PKI solutions for identity and encryption. The company is known for its expertise in identity and encryption for web servers and Internet of Things devices. DigiCert supports TLS/ Secure Sockets Layer ( SSL) and other digital certificates for PKI deployments at any scale through its certificate lifecycle management platform, CertCentral® . The company provides enterprise -grade certificate management platforms, responsive customer support, and advanced security solutions. If availability and operational problems occur , e nterprises that provide these services to customers, partners, and employees need to rapidly troubleshoot and fix these issues."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n1. The high-performance computing zone consists of a pool of compute nodes connected by one or more high-speed networks. The high-performance computing zone provides key services specifically designed to run parallel jobs at scale. 2. The data storage zone comprises one or multiple high-speed parallel file systems that provide data storage service for user data. The high-speed parallel file systems are designed to store very large data sets and provide fast access to data for reading and writing. 3. The access zone has one or more nodes that are connected to external networks, such as the broader organizational network or the internet. This zone provides the means for authenticating and authorizing the access and connections of users and administrators. The access zone provides various services, including interactive shells, web-based portals, data transfer, data visualization, and others. 4. The management zone comprises multiple management nodes and/or cloud service clusters through which HPC management services are provided. The management zone allows HPC system administrators to configure and manage the HPC system, including the configuration of compute nodes, storage, networks, provisioning, identity management, auditing, system monitoring, and vulnerability assessment. Various management software modules (e.g., job schedulers, workflow management, and the Domain Name System [DNS]) run in the management zone. One important characteristic of the management zone is that it has a separate security posture because non-privileged users do not need to access the management servers or services in a direct way. Privileged users responsible for configuring, maintaining, and operating the HPC system access the management zone servers and switches through extra security controls."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n-  The solution was developed in a lab environment. The environment is based on a basic organization ʼ s IT enterprise. It does not reflect the complexity of a production environment: for example, building across numerous physical locations, accommodating extreme working conditions, or configuring systems to meet specific network/user needs. These demands can all increase the level of complexity needed to implement a DI solution.\n-  An organization has access to the skill sets and resources required to implement an event detection and response system.\n-  A DI event is taking place, and the organization is seeking to detect and mitigate the damage that an event is causing.\n\nUSB attacks do not always come in the form of disguised file-based malware. As USB attacks allow direct interfacing with the hardware of the system, they can aim to destroy the system via electrical attacks or involve impersonation of a keyboard or other devices to avoid detection and gain privileges. These attacks may be better mitigated through a thorough physical security policy and restrictions on the types of allowed connected devices. Advanced attacks that involve manipulation of hardware can become increasingly difficult to detect once plugged into the system. A prevention solution involving backups, physical security, and employee education is often more effective.\n\nThe process of granting or denying specific requests to: 1) obtain and use information and related information processing services; and 2) enter specific physical facilities (e.g., federal buildings, military establishments, border crossing entrances)"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.4.1 | Backup and Recovery ... 3.4.1 Backup and Recovery\n\nBackup and recovery methods and strategies are a means to restore system operations quickly and effectively following a service disruption."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.5.4\n\n12-12\n\no\n\n. 3.5.4\n\nReview Test Results and Determine if Further Tests Are Required\n\nThis step is an analysis and evaluation function to ensure that the\n\ntest results are valid."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.5.4", "cmmc_practice_id": "IA.L2-3.5.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n- e. See Section 5.6.2.2.3.1.\n2. f However, see Section 5.6.2.2.4.\n\nKey confirmation can be provided in either or both directions as part of a C(0e, 2s) scheme by using the methods specified in Section 6.3.3.1. This allows the key confirmation recipient to obtain assurance that the key-confirmation provider has possession of the MacKey derived from the shared secret Z and has used it with the appropriate MacData to compute the received MacTag . In the absence of a compromise of private information (e.g., a static private key or the static shared secret, Z ), a key-confirmation recipient can obtain assurance that the appropriate identifier has been used to label the key-confirmation provider, and that the provider is the owner of the static public key associated with that identifier. A keyconfirmation recipient can also receive assurance of active (and successful) participation by the key-confirmation provider in the key-agreement transaction."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nVisual authentication entails inspection of the topographical features on the front and back of the PIV Card. The human guard checks to see that the PIV Card looks genuine, compares the cardholder's facial features with the picture on the card, checks the expiration date printed on the card, verifies the correctness of other data elements printed on the card, and visually verifies the security feature(s) on the card. The effectiveness of this mechanism depends on the training, skill, and diligence of the guard (to match the face in spite of changes in physical appearance beard, mustache, hair coloring, eye glasses, etc.) - counterfeit IDs can pass visual inspections easily. Digital scanners, printers, and image editing software have made counterfeiting easier. Moreover, the visual verification of security features does not scale well across agencies since each agency may implement different security features. For these reasons, [FIPS201] has downgraded this authentication mechanism to indicate that it provides 'LITTLE or NO' confidence in the identity of the cardholder."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nuirements. When deciding whether to require and implement C-SCRM practices and controls, acquirers should consider both the costs of implementing these controls and the risks of not implementing them.\napplicable existing data and documentation that may provide evidence\n\n| Levels | Level Name | Generic Stakeholder | Activities |\n|----------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 3 | Operational | Systems Management: Architects, developers, system owners, QA/QC, testing, contracting personnel, C-SCRM PMO staff, control engineer and/or control system operator, etc. | • Develop C-SCRM plans. • Implement C-SCRM policies and requirements. • Adhere to constraints provided by Level 1 and Level 2. • Tailor C-SCRM to the context of the individual system, and apply it throughout the SDLC. • Report on C-SCRM to Level 2. |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nSecurity and privacy control assessments are not about checklists, simple pass/fail results, or\ngenerating paperwork to pass inspections or audits. Rather, control assessments are the\nprincipal vehicle used to verify that selected security and privacy controls are implemented and\nmeeting stated goals and objectives. Special Publication (SP) 800-53A, Assessing Security and\nPrivacy Controls in Information Systems and Organizations, facilitates security control\nassessments and privacy control assessments conducted within an effective risk management\nframework. A major design objective for SP 800-53A is to provide an assessment framework and\ninitial starting point for assessment procedures that are flexible enough to meet the needs of\ndifferent organizations while providing consistency in conducting control assessments. Control\nassessment results provide organizational officials with:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "..................................................................115 | |\n| A.2.13.\nFAMILY: PHYSICAL AND ENVIRONMENTAL PROTECTION......................................................116 | |\n| A.2.14. FAMILY: PLANNING ................................................................................................................120 | |\n| A.2.15. FAMILY: PROGRAM MANAGEMENT ......................................................................................123 | |\n| A.2.16. FAMILY: PERSONNEL SECURITY..............................................................................................129 | |\n| A.2.17. FAMILY: PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY | ....132 |\n| A.2.18. FAMILY: RISK ASSESSMENT....................................................................................................132 | |\n| A.2.19. FAMILY: SYSTEM AND SERVICES ACQUISITION......................................................................136 | |\n| A.2.20."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\n\n\n## NIST Internal Report NIST IR 8425\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nMichael Fagan Katerina Megas Paul Watrobski Jeffery Marron Barbara Cuthill\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8425\n\n\n\n## NIST Internal Report NIST IR 8425\n\n## Profile of the IoT Core Baseline for Consumer IoT Products\n\nMichael Fagan Katerina N. Megas Paul Watrobski Jeffrey Marron Barbara B. Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8425\n\nSeptember 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.5. MQOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.5. MQOM"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 10)"}, {"role": "assistant", "content": "|\n| 4.2 Key-Agreement Process....................................................................................................\n19 | 4.2 Key-Agreement Process.................................................................................................... 19 | 4.2 Key-Agreement Process.................................................................................................... 19 |\n| 4.3 Key-Transport Process...................................................................................................... 20 | 4.3 Key-Transport Process......................................................................................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Security Assessment?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n03600\\_103699/103645/01.01.01\\_60/ts\\_103645v01 0101p.pdf\n- [12] Groupe Spéciale Mobile Association (GSMA) (2017) GSMA IoT Security Assessment. (Groupe Spéciale Mobile Association [GSMA], London, UK).\nhttps://www.gsma.com/iot/iot-security-assessment/\n- [13] International Electrotechnical Commission (IEC) (2019) IEC 62443-4-2, Edition 1.0, Security for industrial automation and control systems, Part 4-2: Technical security requirements for IACS components. (International Electrotechnical Commission [IEC], Geneva, Switzerland). https://webstore.iec.ch/publication/34421\n- [14] Industrial Internet Consortium (IIC) (2016) Industrial Internet of Things Volume G4: Security Framework. (Industrial Internet Consortium [IIC], Needham, MA). https://www.iiconsortium.org/IISF.htm\n- [15] IoT Security Foundation (IoTSF) (2018) IoT Security Compliance Framework, Release 2. (IoT Security Foundation [IoTSF], Livingston, Scotland). https://www.iotsecurityfoundation.org/best-practice-guidelines/\n- [16] Online Trust Alliance (OTA) (2017) IoT Security & Privacy Trust Framework v2.5. (Online Trust Alliance [OTA], an Internet Society initiative). https://www.internetsociety.org/resources/doc/2018/iot-trust-framework-v2-5/\n- [17] National Electrical Manufacturers Association (NEMA) (2018) Cyber Hygiene Best Practices. (National Electrical Manufacturers Association [NEMA], Rosslyn, VA). https://www.nema.org/Standards/Pages/Cyber-Hygiene-Best-Practices.aspx\n- [18] Open Connectivity Foundation (OCF) (2020) OCF Security Specification Version 2.1.2. (Open Connectivity Foundation [OCF], Beaverton, Oregon). https://openconnectivity.org/specs/OCF\\_Security\\_Specification\\_v2.1.2.pdf\n- [19] Platform Security Architecture (PSA) Joint Stakeholder Agreement (JSA) Members (2020) PSA Certified™ Level 1 Questionnaire, Version 2.0 Beta. (Arm Limited, Cambridge, United Kingdom)."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 9)"}, {"role": "assistant", "content": "are addressing the clauses from Section 4 of the President's Executive Order (EO) on 'Improving the Nation's Cybersecurity (14028)' by referencing the SSDF practices and tasks described in Appendix A.\n## Table of Contents\n\n| Executive Summary..................................................................................................... vi | Executive Summary....................................................................................................."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 4)"}, {"role": "assistant", "content": "e and disruption and necessitating extensive recovery efforts within most organizations. This publication provides recommendations for improving an organization's malware incident prevention measures.\nIt also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones. ## Keywords\n\nincident response; information security; malware\n\n## Acknowledgments\n\nThe authors, Murugiah Souppaya of the National Institute of Standards and Technology (NIST) and Karen Scarfone of Scarfone Cybersecurity, thank their colleagues who assisted with developing this revision of the publication. ## Acknowledgments, Original Version of SP 800-83\n\nThe authors, Peter Mell of the National Institute of Standards and Technology (NIST) and Karen Kent and Joseph Nusbaum of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. The authors would particularly like to acknowledge Tim Grance and Murugiah Souppaya of NIST and Lucinda Gagliano, Thomas Goff, and Pius Uzamere of Booz Allen Hamilton for their keen and insightful assistance throughout the development of the document. The authors would also like to express their thanks to security experts Mike Danseglio (Microsoft), Kurt Dillard (Microsoft), Michael Gerdes (Getronics RedSiren Security Solutions), Peter Szor (Symantec), Miles Tracy (U.S. Federal Reserve System), and Lenny Zeltser (Gemini Systems LLC), as well as representatives from the General Accounting Office, and for their particularly valuable comments and suggestions. The National Institute of Standards and Technology would also like to express its appreciation and thanks to the Department of Homeland Security for its sponsorship and support of NIST Special Publication 80083."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nThe software development and use of AI models and AI systems inherit much of the same risk as any other digital system. A unique challenge for this community is the blurring of traditional boundaries between system code and system data, as well as the use of plain human language as the means of interaction with the systems. AI models and systems, their configuration parameters (e.g., model weights), and the data they interact with (e.g., training data, user queries, etc.) can form closed loops that can be manipulated for unintended functionality.\n\nThe SSDF provides a common language for describing secure software development practices throughout the software development life cycle. This document augments the practices and tasks defined in SSDF version 1.1 by adding recommendations, considerations, notes, and informative references that are specific to generative AI and dual-use foundation model development. These additions are documented in the form of an SSDF Community Profile ('Profile'), which is a baseline of SSDF practices and tasks that have been enhanced to address a particular use case. An example of an addition is, 'Secure code storage should include AI models, model weights, pipelines, reward models, and any other AI model elements that need their confidentiality, integrity, and/or availability protected.'\n\nNote that a value of 'No additions to SSDF 1.1' in this column indicates that the Profile does not contain recommendations, considerations, or notes specific to AI model development for the task. Refer to SSDF version 1.1 [6] for baseline guidance on the secure development task in question and to the other references in this document for additional information related to the task."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "following components: (i) a control section; (ii) a supplemental guidance section; (iii) a control enhancements section; (iv) a references section; and (v) a priority and baseline allocation section.\nFigure 2: The Risk Management Framework\n\n\n\n## 3 Control Baselines and Tailoring\n\nTo assist organizations in making the appropriate selection of security controls for information systems, the concept of security control baselines is introduced. Security control baselines are the starting point for the security control selection process and are chosen based on the security category and associated impact level of information systems determined in accordance with FIPS Publication 199 and FIPS Publication 200, respectively (Step One of the RMF). SP 800-53 Rev. 4 states that 'the security controls and control enhancements listed in the initial baselines are not a minimum- but rather a proposed starting point from which controls and controls enhancements may be removed or added.' Appendix D provides a listing of baseline security controls corresponding to the low-impact, moderate-impact, and high-impact information systems, using the high water mark defined in FIPS Publication 200. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nmponents (e.g., IoT sensors) may not be able to support some solutions such as configuration agents, application sandboxing, etc. so compensating technologies or alternative mitigations may be needed.\nIf the resource lacks certain security capabilities, the enterprise may need to add a PEP component to provide that functionality. - II. The enterprise monitors and measures the integrity and security posture of all owned and associated resources. This tenet deals with the aspects of cyber hygiene for both enterprise-owned resources and those that may not be owned, but used in an enterprise workflow such as configuration, patching, application loading, etc. The state of resources should be monitored, and appropriate action taken when new information such as a new vulnerability or attack is reported or observed. The confidentiality and integrity of data on the resource should be protected. This requires enterprise admins to know how resources are configured, maintained, and monitored."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "ibed in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs.\nOrganizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control. - Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities. ## 4 Documenting the Control Selection Process\n\nTo aid in review activities, security planning, and risk assessments, organizations document the relevant decisions taken during the security control selection process, providing a sound rationale for those decisions. This documentation is essential when examining the security considerations for organizational information systems with respect to the potential impact on an organization's mission and business."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| PW.2.1 : Have 1) a qualified person (or people) who were not involved with the design and/or 2) automated processes instantiated in the toolchain review the software design to confirm and enforce that it meets all of the security requirements and satisfactorily addresses the identified risk information. | Example 1 : Review the software design to confirm that it addresses applicable security requirements. Example 2 : Review the risk models created during software design to determine if they appear to adequately identify the risks. Example 3 : Review the software design to confirm that it satisfactorily addresses the risks identified by the risk models. Example 4 : Have the software's designer correct failures to meet the requirements. Example 5 : Change the design and/or the risk response strategy if the security requirements cannot be met. Example 6 : Record the findings of design reviews to serve as artifacts (e.g., in the software specification, in the issue tracking system, in the threat model)."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 4)"}, {"role": "assistant", "content": "Controls and Security: A System Development Life Cycle Approach\n\nEditors/Authors:\n\nZella G. Ruthberg\n\nBonnie T. Fisher\n\nWilliam E' Perry\n\nJohn W. Lainhart SV\n\nJames G. Cox\n\n'\n\nMark Gillen\n\nDouglas B.\nHunt\n\nCo-Sponsored by:\n\nPresident's Council on Integrity and Efficiency\n\nInstitute for Computer Sciences and Technology and National Bureau of Standards\n\nGaithersburg, MD 20899\n\nApril 1988\n\n\n\nU.S. DEPARTMENT OF COMMERCE\n\nC. William Verity, Secretary\n\nNational Bureau of Standards\n\nErnest Ambler, Director\n\nResearch Information Center National Bureau of Standards Gaithersburg, Maryland 20899\n\n\n\n## Reports on Computer Science and Technology\n\nThe National Bureau of Standards has a special responsibility within the Federal Government for computer science and technology activities. The programs of the NBS Institute for Computer Sciences and Technology are designed to provide ADP standards, guidelines, and technical advisory services to improve the effectiveness of computer utilization in the Federal sector, and to perform appropriate research and development efforts as foundation for such activities and programs. This publication series will report these NBS efforts to the Federal computer community as well as to Interested specialists in the academic and private sectors. Those wishing to receive notices of publications in this series should complete and return the form at the end of this publication. Library of Congress Catalog Card Number: 88-600518 National Bureau of Standards Special Publication 500-153 Natl. Bur. Stand. (U.S.), Spec. Publ. 500-153, 266 pages (Apr. 1988) CODEN: XNBSAV\n\nU.S."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to A Data Structure for Integrity Protection with Erasure Capability:\n\n## A Data Structure for Integrity Protection with Erasure Capability\n\nThis publication is a final version of a draft cybersecurity white paper originally published on May 31, 2018: https://csrc.nist.gov/publications/detail/white-paper/2018/05/31/data-structure-for-integrityprotection-with-erasurecapability/draft.\n\nThis document describes a data structure, referred to as a data block matrix, that supports the ongoing addition of hash-linked records while also allowing for the deletion of arbitrary records, thereby preserving hash-based integrity assurance that other blocks are unchanged. The block matrix data structure may have utility for incorporation into applications requiring integrity protection that currently use permissioned blockchains. This capability could for example be useful in meeting privacy requirements such as the European Union General Data Protection Regulation (GDPR), which requires that organizations make it possible to delete all information related to a particular individual, at that person's request."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-53A\nRevision 5\n\nAssessing Security and Privacy Controls in\nInformation Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53Ar5\n\n\f NIST Special Publication 800-53A\nRevision 5\n\n Assessing Security and Privacy Controls\nin Information Systems and\nOrganizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53Ar5\n\nJanuary 2022\n\nNational Institute of Standards and Technology\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce\nfor Standards and Technology & Director, National Institute of Standards and Technology\n\nU.S. Department of Commerce\nGina M. Raimondo, Secretary\n\n\fAuthority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the\nFederal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq., Public Law\n(P.L.) 113-283. NIST is responsible for developing information security standards and guidelines,\nincluding minimum requirements for federal information systems. Such information security\nstandards and guidelines shall not apply to national security systems without the express\napproval of the appropriate federal officials exercising policy authority over such systems. This\nguideline is consistent with the requirements of the Office of Management and Budget (OMB)\nCircular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made\nmandatory and binding on federal agencies by the Secretary of Commerce under statutory\nauthority. Nor should these guidelines be interpreted as altering or superseding the existing\nauthorities of the Secretary of Commerce, OMB Director, or any other federal official. This\npublication may be used by nongovernmental organizations on a voluntary basis and is not\nsubject to copyright in the United States."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 3)"}, {"role": "assistant", "content": "'check-the-box' activity. While prior surveys and research have examined programs in the private sector, there is little understanding of whether these findings also apply within the U.S. government.\nTo address this gap and better understand the needs, challenges, practices, and necessary competencies of federal security awareness teams and programs, NIST conducted a research study that leveraged both qualitative and quantitative methodologies. This companion document to NISTIR 8420 'Federal Cybersecurity Awareness Programs: A Mixed Methods Research Study' reports on a subset of study results focused on identifying the current approaches and challenges of security awareness programs within the federal government. Insights gained from these results are informing guidance and other initiatives to aid federal organizations in building effective security awareness programs. While focused on the U.S. government, findings may also have implications for organizational security awareness programs in other sectors. ## Keywords\n\ncybersecurity; cybersecurity awareness; focus groups; measures of effectiveness; mixed methods; phishing; security professionals; survey; training; usable cybersecurity\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Executive Summary\n\nSecurity awareness programs aim to help employees recognize and appropriately respond to security issues, with a goal of achieving long-term behavior change. Industry and research surveys have revealed that organizational security awareness programs face a number of challenges, including lack of resources, difficulty measuring the impact of the program, and perceptions among the workforce that training is a boring, 'check-the-box' activity."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 7)"}, {"role": "assistant", "content": "nterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards.\nEducating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle. The National Strategy on Microelectronics Research has emphasized the prioritization of hardware integrity and security. In response, NIST convened its inaugural workshop, 'Enhancing Security of Devices and Components Across the Supply Chain' 1 on February 27, 2024, at the National Cybersecurity Center of Excellence (NCCoE) facility. At this workshop,\n\n1 See https://csrc.nist.gov/Events/2024/enhancing-security-of-devices-and-components. government, academia, and industry experts gathered to collaborate on research efforts, drive innovation, and establish standards, guidance, and practical implementations in a rapidly evolving landscape. The workshop was primarily an in-person event with a few remote speakers and participants. In total, there were 98 participants, with 79 participants almost evenly distributed from government and industry. The remaining 19 attendees were from academia and standards developing organizations (SDOs). Figure 2 shows the distribution of participants. Fig. 2. Distribution of workshop participants\n\n\n\n## 2. Workshop Sessions\n\n## 2.1. Hardware Development Life Cycle\n\nSemiconductor and integrated circuit (IC) development is complex, non-linear, and varies from one manufacturer to another. Development of hardware is complex with many business drivers, relying on expertise at best cost across a global supply chain. This panel discussion focused on open security concerns in the hardware development life cycle. ## 2.1.1."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 2)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-09-12\n\nSupersedes NIST SP 800-88r1 (Revision 1) (December 2014) https://doi.org/10.6028/NIST.SP.800-88r1\n\n## How to Cite this NIST Technical Series Publication\n\nChandramouli R, Hibbard EA (2025) Guidelines for Media Sanitization."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Machine Learning for Access Control Policy Verification:\n\n## Machine Learning for Access Control Policy Verification\n\n## Machine Learning for Access Control Policy Verification\n\nAccess control policy verification ensures that there are no faults within the policy that leak or block access privileges. As a software test, access control policy verification relies on methods such as model proof, data structure, system simulation, and test oracle to verify that the policy logic functions as expected. However, these methods have capability and performance issues related to inaccuracy and complexity limited by applied technologies. For instance, model proof, test oracle, and data structure methods initially assume that the policy under verification is faultless unless the policy model cannot hold for test cases. Thus, the challenge of the method is to compose test cases that can comprehensively discover all faults. Alternatively, a system simulation method requires translating the policy to a simulated system. The translation between systems may be difficult or impractical to implement if the policy logic is complicated or the number of policy rules is large. To answer these challenges, this internal report (IR) proposes an efficient and straightforward method for access control policy verification by applying a classification algorithm of machine learning, which does not require comprehensive test cases, oracle, or system translation but rather checks the logic of policy rules directly, making it more efficient and feasible compared to traditional methods."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n-  Secure a dequate funding to maintain a robust security information and event management (SIEM) infrastructure\n-  Make trained personnel available to manage an SIEM or similar tool to create and administer correlation rules to produce timely, accurate alerts related to anomalous activity.\n- Implement appropriate configuration of all cogent log-generating agents on the endpoint (e.g., instant log transfer to SIEM vs. periodic transfer of batched logs that can be deleted by an attacker to hide their activity)."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Configuration Management?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nr risk domains such as cybersecurity. The NIST Privacy Framework helps organizations understand the relationship between privacy and cybersecurity risks in the context of the Internet of Things (IoT).\nProblematic data actions, such as deriving inferences about individuals, can pose significant privacy risks, particularly in consumer IoT. A key factor in managing privacy risks is an organization's role in t he data processing ecosystem, which includes the complex relationships among entities involved in data processing. An organization's role(s) in the IoT ecosystem can affect its legal obligations and the measures it should take to manage privacy risk. High-level goals for mitigating cybersecurity and privacy risks include protecting device security, data security, and individual privacy. The privacy engineering objectives of predictability, manageability, and disassociability can be useful to meet these goals by supporting the determination of privacy capabilities in IoT products. Gilbert also discussed specific privacy risks related to IoT, such as interactions with the physical world leading to reputational harm or safety issues. Data processing might exceed the product's intended scope, and access, management, and monitoring features could result in loss of trust and economic loss. Additionally, privacy capability availability, efficiency, and effectiveness are crucial to prevent issues like discrimination and to maintain trust. IoT products need the capabilities to support configurations such as remote activation, prevention, and data minimization."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "g/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-171r3. https://doi.org/10.6028/NIST.SP.800-171r3\n\n## Author ORCID iDs\n\nRon Ross: 0000-0002-1099-9757\n\nVictoria Pillitteri: 0000-0002-7446-7506\n\n## Submit Comments\n\n## 800-171comments@list.nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/171/r3/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe protection of Controlled Unclassified Information (CUI) is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides federal agencies with recommended security requirements for protecting the confidentiality of CUI when the information is resident in nonfederal systems and organizations. The requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. The security requirements are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations. This publication can be used in conjunction with its companion publication, NIST Special Publication 800-171A, which provides a comprehensive set of procedures to assess the security requirements."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n## Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process\n\n## Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process\n\nAlagic G, Bros M, Ciadoux P, Cooper D, Dang Q, Dang T, Kelsey J, Lichtinger J, Liu YK, Miller C, Moody D, Peralta R, Perlner R, Robinson A, Silberg H, Smith-Tone D, Waller N (2025) Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Internal Report (IR) NIST IR 8545. https://doi.org/10.6028/NIST.IR.8545"}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nCDM System (sistema CDM). Industry Compliance (cumplimiento de la industria). Threat Intelligence (inteligencia sobre amenazas). Activity Logs (registros de actividades). Control Plane (plano de control). Policy Engine (motor de políticas). Policy Administrator (administrador de políticas). Policy Decision Point (punto de decisión de políticas). Data plane (plano de datos). Subject (sujeto). System (sistema). Untrusted (no confiable). Policy Enforcement Point (punto de aplicación de políticas). Trusted (confiable). Enterprise Resource (recurso de la empresa). Date Access Policy (política de acceso a los datos). PKI, public key infrastructure (infraestructura de clave pública). ID Management (gestión de identidades). SIEM System (sistemas de seguridad de la información y gestión de eventos).\n\nAccess Request (solicitud de acceso). Subject Database and History (datos e historial del sujeto). Asset Database (datos del activo). Resource Policy Requirements (requerimientos de la política de recursos). Threat Intelligence and Logs (inteligencia de amenazas y registros). Trust Algorithm (algoritmo de confianza)."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-204D\n\n## Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines\n\nRamaswamy Chandramouli Frederick Kautz Santiago Torres-Arias\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-204D\n\n\n\n## NIST Special Publication 800 NIST SP 800-204D\n\n## Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines\n\nRamaswamy Chandramouli Computer Security Division Information Technology Laboratory\n\nFrederick Kautz TestifySec\n\nSantiago Torres-Arias Electrical and Computer Engineering Department Purdue University\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-204D\n\nFebruary 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nFiles and keychain elements are both protected by one of a number of access control keys, which are also encrypted in a way that incorporates the user's device passcode. The passcode"}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 7)"}, {"role": "assistant", "content": "| Modification ................................................................................................................\n2 |\n| CMVP-approved sensitive security parameter generation and establishment requirements............................................................................................................................ | CMVP-approved sensitive security parameter generation and establishment requirements............................................................................................................................ |\n| | Purpose...................................................................................................................... 2 |\n| | Sensitive security parameter generation and establishment methods......................... 2 |\n| Appendix A. Document Revisions....................................................................................... 3 | Appendix A. Document Revisions......................................................................................."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 10)"}, {"role": "assistant", "content": "utions, hardware acceleration technology, and others - have the potential to influence the HPC reference architecture and security posture. Consequently, this document will be updated as needed. ## 2.\nHPC System Reference Architecture and Main Components\n\nThe HPC system is complex and evolving, and a common lexicon can help describe and identify an HPC system's architecture, critical elements, security threats, and potential risks. An HPC system is divided into four function zones:\n\n1. The high-performance computing zone consists of a pool of compute nodes connected by one or more high-speed networks. The high-performance computing zone provides key services specifically designed to run parallel jobs at scale. 2. The data storage zone comprises one or multiple high-speed parallel file systems that provide data storage service for user data. The high-speed parallel file systems are designed to store very large data sets and provide fast access to data for reading and writing. 3. The access zone has one or more nodes that are connected to external networks, such as the broader organizational network or the internet. This zone provides the means for authenticating and authorizing the access and connections of users and administrators. The access zone provides various services, including interactive shells, web-based portals, data transfer, data visualization, and others. 4. The management zone comprises multiple management nodes and/or cloud service clusters through which HPC management services are provided. The management zone allows HPC system administrators to configure and manage the HPC system, including the configuration of compute nodes, storage, networks, provisioning, identity management, auditing, system monitoring, and vulnerability assessment. Various management software modules (e.g., job schedulers, workflow management, and the Domain Name System [DNS]) run in the management zone. The HPC system reference architecture is depicted in Fig. 1 . Fig. 1."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n## 3.1. Preparation and Lessons Learned\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------|\n| PR.AA (Identity Management, Authentication, and Access Control) | Access to physical and logical assets is limited to authorized users, services, and hardware and managed commensurate with the assessed risk of unauthorized access | Medium | N1: See the notes for PR. |\n| PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed by the organization | Medium | N1: See the notes for PR. |\n| PR.AA-02 | Identities are proofed and bound to credentials based on the context of interactions | Medium | N1: See the notes for PR. |\n| PR.AA-03 | Users, services, and hardware are authenticated | Medium | N1: See the notes for PR."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 2)"}, {"role": "assistant", "content": "locks/data-integrity/detect-respond. \n\n## Executive Summary\n\nThe CIA triad represents the three pillars of information security: confidentiality, integrity, and availability, as follows.\n-  Confidentiality - preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information\n-  Integrity - guarding against improper information modification or destruction and ensuring information non-repudiation and authenticity\n-  Availability - ensuring timely and reliable access to and use of information\n\n\n\nThis series of practice guides focuses on data integrity: the property that data has not been altered in an unauthorized manner. Data integrity covers data in storage, during processing, and while in transit. (Note: These definitions are from National Institute of Standards and Technology (NIST) Special Publication (SP) 800-12 Rev 1, An Introduction to Information Security .)\n\n-  Destructive malware, ransomware, malicious insider activity, and even honest mistakes all set the stage for why organizations need to detect and respond to an event that impacts data integrity. Businesses must be confident that these events are detected in a timely fashion and responded to appropriately. -  Attacks against an organization's data can compromise emails, employee records, financial records, and customer information-impacting business operations, revenue, and reputation. -  Examples of data integrity attacks include unauthorized insertion, deletion, or modification of data to corporate information such as emails, employee records, financial records, and customer data."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.1.1, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nSemiconductor-based hardware is the foundation of modern-day electronics - from smartphones, computers, and telecommunications to transportation and critical infrastructure. The semiconductor hardware supply chain is a complex network of companies that collectively provide intellectual property, designs, and raw materials and manufacture, test, package, and distribute products. Coordination among the components of a supply chain is required at different stages, including inception, deployment to end users, maintenance during use, and disposal or end of life. Securing semiconductor-based hardware and their supply chains help protect sensitive information, maintain the integrity of systems, and ensure overall stability across the infrastructure and connected world.\n\nThese activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle.\n\nThe National Strategy on Microelectronics Research has emphasized the prioritization of hardware integrity and security. In response, NIST convened its inaugural workshop, 'Enhancing Security of Devices and Components Across the Supply Chain' 1 on February 27, 2024, at the National Cybersecurity Center of Excellence (NCCoE) facility. At this workshop,"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-07-25\n\n## How to Cite this NIST Technical Series Publication\n\nBooth H, Souppaya M, Vassilev A, Ogata M, Stanley M, Scarfone K (2024) Secure Development Practices for Generative AI and Dual-Use Foundation AI Models: An SSDF Community Profile. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-218A. https://doi.org/10.6028/NIST.SP.800-218A\n\n## Author ORCID iDs\n\nHarold Booth: 0000-0003-0373-6219 Murugiah Souppaya: 0000-0002-8055-8527 Apostol Vassilev: 0000-0002-9081-3042 Michael Ogata: 0000-0002-8457-2430 Karen Scarfone: 0000-0001-6334-9486\n\n## Contact Information\n\nssdf@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/218/a/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis document augments the secure software development practices and tasks defined in Secure Software Development Framework (SSDF) version 1.1 by adding practices, tasks, recommendations, considerations, notes, and informative references that are specific to AI model development throughout the software development life cycle."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n## Family: Incident Response"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.2.1 Data Entry | |\n| | | 3. 3.2.1 | Natural Hazards | 6-10 |\n| | 3. 3.2.1 Data Entry ."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 8)"}, {"role": "assistant", "content": "e 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.\nThe protection of a specific service to include CUI that is processed, stored or transmitted during the provision of that service, is achieved by implementing the enhanced security requirements for the service, or the system or system components responsible for providing that service. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. The term organizational system is used in many of the enhanced security requirements. It has a specific meaning regarding the applicability of the enhanced requirements as described above. Appropriate scoping considerations for the requirements are important factors in determining protection-related investment decisions and managing security risk for nonfederal organizations that have the responsibility of protecting CUI associated with critical programs and high value assets. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## FRAMEWORK FOR IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY\n\nOrganizations that have implemented or plan to implement the NIST Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 7)"}, {"role": "assistant", "content": "publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication.\n## Table of Contents\n\n| 1 | Executive Summary.............................................................................1 | Executive Summary.............................................................................1 |\n|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | Introduction........................................................................................2 | Introduction........................................................................................2 |\n| | 2.1 | Audience ......................................................................................................................"}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "tise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D.\nThe controls described assist organizations in defining the controls needed to satisfy minimum assurance requirements. Where additional assurance is desired to achieve risk management objectives, Table E-4 provides additional security controls and control enhancements to achieve enhanced assurance. Implementers should note that designation of assurance-related controls is not intended to imply a greater level of importance for such controls. Achieving adequate security for organizational information systems requires the correct combination of both functionality- and assurance-related security controls. ## 6 Security Controls\n\nAppendix F, the Security Control Catalog, provides a comprehensive range of countermeasures for organizations and information systems. The security controls are designed to be technologyneutral such that the focus is on the fundamental countermeasures needed to protect organizational information during processing, storage, or transmission. SP 800-53 Rev. 4, therefore, does not provide guidance on the application of security controls to specific technologies, environments of operation, or missions/business functions. These specific areas may be addressed using overlays (see below). Control enhancements are included with many security controls and are selected in order to increase the strength of the base control. Control enhancements are intended to be implemented only in conjunction with implementation of the base control. Some security controls and control enhancements include one or more assignment and selection statements. These are variable 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."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n| Phase | User Base | Rationale | Outcome |\n|---------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 | IT support and help desk personnel | IT support and help desk personnel are tech-savvy users who can also anticipate potential support issues that the larger user base may have with the solution. | • Test multiple authenticator types and gain feedback on the processes of obtaining and using each authenticator. • Enumerate potential support issues. • Gain feedback on MFA instructions and communication tools. • Confirm authenticator type selection. |\n| 2 | General IT staff | This is a larger, but still technically literate, user base. | • Test authenticators selected from phase 1. • Gain feedback on MFA instructions and communication tools. • Update communications and/or policy based on feedback. |\n| 3 | General user cohort | A representative cohort of general users can help test the MFA solution before a general user rollout. | • Take volunteers or a selection of the general cohort to test the MFA solution."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.3. 3.1.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.5.1. 3.5.1. 3.5.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | xiii | |-------------------------|------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|--------| | CHAPTER 1 | CHAPTER 1 | CHAPTER 1 | CHAPTER 1 | | | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | GENERALADP AUDIT ISSUES | 1 | | 1.1 | INTRODUCTION | INTRODUCTION | INTRODUCTION | 1 | | | 1.1.1 | Scope of the Audit Guide | Scope of the Audit Guide | 1 | | | 1.1.2 | How to Use the Audit Guide | How to Use the Audit Guide | 2 | | | 1.1.3 | Auditor Skills Needed | Auditor Skills Needed | 2 | | | 1.1.4 | Auditing in a Computerized Environment | Auditing in a Computerized Environment | 3 | | | 1.1.4.1 | 1.1.4.1 | The Need | 3 | | | 1.1.4.2 | 1.1.4.2 | The Scope of Audit in a Computerized Environment | 3 | | | 1.1.4.3 | 1.1.4.3 | Relationship Between Systems Development Audits and | | | | Operational Audits of Automated Information Systems (AISs) | Operational Audits of Automated Information Systems (AISs) | Operational Audits of Automated Information Systems (AISs) | 4 |"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Access Control on NoSQL Databases provide? (Part 6)"}, {"role": "assistant", "content": ".................................12 |\n| 4. Considerations of Access Control for NoSQL Systems.....................................................................15 |\n| 5.\nConclusion ...................................................................................................................................19 |\n| References.......................................................................................................................................20 |\n| Appendix A......................................................................................................................................22 |\n\n| List of Tables |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 1. Comparison of RDBMS and NoSQL features ...........................................................................6 |\n| List of Figures |\n| Fig. 1. Key-value database model .......................................................................................................3 |\n| Fig. 2."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nlar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172A Natl. Inst. Stand. Technol. Spec. Publ. 800-172A, 62 pages (March 2022)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.1.3 Other Considerations\n\nBecause malware comes in many forms, it is imperative to have multiple layers of defense against it while also working to actively improve these defenses."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe enhanced security requirements are organized into 14 families consistent with the families for basic and derived requirements. Each family contains the requirements related to the general security topic of the family. The families are closely aligned with the minimum security requirements for federal information and information systems in [FIPS 200]. The security requirements for contingency planning , system and services acquisition , and planning are not included within the scope of this publication due to the tailoring criteria in [SP 800-171]. Table 1 lists the security requirement families addressed in this publication. 17\n\n- 3.11.4e Document or reference in the system security plan the security solution selected, the rationale for the security solution, and the risk determination."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\normation system, and that the threat and vulnerability identification and initial risk determination are identified and documented in the system security plan, risk assessment, or equivalent document.\nThe results of a security certification are used to reassess the risks, develop the plan of action and milestones (POA&Ms) which are required to track remedial actions, and update the system security plan, thus providing the factual basis for an authorizing official to render a security\n\nBefore the system security plan can be developed, the information system and the information resident within that system must be categorized based on a FIPS 199 impact analysis. Then a determination can be made as to which systems in the inventory can be logically grouped into major applications or general support systems. The FIPS 199 impact levels must be considered when the system boundaries are drawn and when selecting the initial set of security controls (i.e., control baseline). The baseline security controls can then be tailored based on an assessment of risk and local conditions including organization-specific security requirements, specific threat information, costbenefit analyses, the availability of compensating controls, or special circumstances. Common security controls, which is one of the tailoring considerations, must be identified prior to system security plan preparation in order to identity those controls covered at the agency level, which are not system-specific. These common security controls can then be incorporated into the system security plan by reference."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- Unified threat management (or UTMs): UTM devices combine many of the most critical security functions - firewall, IPS, VPN concentrator, gateway antivirus, content filtering, and WAN load balancing - into a single device, usually with a unified management console. - Next-generation firewall (NGFW): The distinguishing feature of NGFW is application data awareness. It can look at data not only at layers 3 and 4 of an Open Systems Interconnection (OSI) stack but also at layer 7 - the application level. Its capabilities extend beyond packet filtering and stateful inspection. There are multiple deployment options available for NGFWs, such as an appliance in the data center, as a software running in a VM in a cloud, or as a cloud service (FWaaS). Some capabilities of NGFW include [9]:\n- a. Deep Packet Inspection (DPI)\n- b. TLS decryption and inspection of packet payload\n- c. Intrusion prevention system (IPS) feature\n- Web application and API protection (WAAP): This is a comprehensive security approach and an enhancement over WAF. WAF is an integral component for API security, BOT (abbreviation for Robot) defense, and DDOS protection. - a. These can be offered as a product suite or as a cloud-based service [10][11]. - b. Secure web gateway (SWGs): SWGs are appliances utilized for policy-based access to and control of cloud-based applications as well as governance of access to the open web for enterprise users in ubiquitous locations (e.g., headquarters, branch offices, home, remote locations). An SWG is fundamentally a web filter that protects outbound user traffic through HTTP or Hypertext Transfer Protocol Secure (HTTPS) inspection [12]. It also protects user endpoints from web-based threats that can occur when users click on links to malicious websites or to websites infected with malware. They centralize control, visibility, and reporting across many locations and types of users. They are not a replacement for WAFs,\n\n- a."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 6)"}, {"role": "assistant", "content": ". Entre ellas se encuentran Greg Holden, director del proyecto ZTA del Consejo Federal de CIO; Alper Kerman, director del proyecto ZTA del NIST/Centro Nacional de Ciberseguridad; y Douglas Montgomery.\nEn la traducción, un especial reconocimiento a las personas que colaboraron de alguna u otra forma con la gestión, redacción, terminología específica y compaginación: Fabien Spychiger, CEO Dreamlab Technologies Chile; Javier Toro Rodríguez, Cybersecurity Service Manager, Dreamlab Tecnologies Chile; Stéphane Bürgi, Senior Technical Writer Dreamlab Technologies Chile y Celeste Gauna, Cyberintelligence Analyst Dreamlab Technologies Chile. ## Audiencia\n\nEste documento pretende describir la confianza cero para los arquitectos de seguridad empresarial. Se intenta ayudar a la comprensión de la confianza cero para los sistemas civiles no clasificados y proporcionar una hoja de ruta para migrar y desplegar conceptos de seguridad de confianza cero a un entorno empresarial. Los responsables de ciberseguridad de las agencias, los administradores de red y los directivos también pueden obtener información sobre la confianza cero y la ZTA a partir de este documento. Esta guía no pretende ser un plan de despliegue único para la ZTA, ya que cada empresa tendrá sus propios casos de uso y activos de datos que requieran protección. Si se parte de un conocimiento sólido del negocio y los datos de la organización, se obtendrá un enfoque sólido de la confianza cero. ## Información sobre marcas registradas\n\nTodas las marcas registradas o comerciales pertenecen a sus respectivas organizaciones. ## Aviso de divulgación de patentes\n\nAVISO: el laboratorio de tecnologías de la información (ITL) ha solicitado 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."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThis publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, 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. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide?"}, {"role": "assistant", "content": " ## NIST Special Publication (SP) 1288GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> FEDERAL CYBERSECURITY ROLE-BASEDGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> TRAINING APPROACHES, SUCCESSES,GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> AND CHALLENGESGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> JulieGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> Haney,GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> JodyGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> Jacobs,GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> andGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> SusanneGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> FurmanGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> ThisGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> publicationGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> isGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> availableGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> freeGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> ofGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> chargeGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> from:GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> https://doi.org/10.6028/NIST.SP.1288GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> ## NIST Special Publication (SP) 1288GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> FEDERAL CYBERSECURITY ROLE-BASEDGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> TRAINING APPROACHES, SUCCESSES,GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> AND CHALLENGESGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> JulieGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> Haney,GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> JodyGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> Jacobs,GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> andGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> SusanneGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> FurmanGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> InformationGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> AccessGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> DivisionGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> InformationGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> TechnologyGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> LaboratoryGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> NationalGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> InstituteGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> ofGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> StandardsGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> andGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> TechnologyGLYPH<c=2,font=/CAAAAA+HKGrotesk-MediumItalic> ThisGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> publicationGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> isGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> availableGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> freeGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> ofGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> chargeGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> from:GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> https://doi.org/10.6028/NIST.SP.1288GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> JANUARYGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> 2023GLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> U.S.GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> DepartmentGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> ofGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> CommerceGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> GinaGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> M.GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> Raimondo,GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> SecretaryGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> NationalGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> InstituteGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> ofGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> StandardsGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> andGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> TechnologyGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> LaurieGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> E.GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> Locascio,GLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> NISTGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> DirectorGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> andGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> UnderGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> SecretaryGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> ofGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> CommerceGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> forGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> StandardsGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> andGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> TechnologyGLYPH<c=2,font=/AAAAAA+HKGrotesk-Medium> ## DISCLAIMERGLYPH<c=2,font=/EAAAAA+HKGrotesk-Bold> Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Machine Learning for Access Control Policy Verification:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\nEnsure the secure disposal of\nequipment that contains device-\nbased authentication keys."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide?"}, {"role": "assistant", "content": "\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guidelines for Media Sanitization provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-88r2\n\n## Guidelines for Media Sanitization\n\nRamaswamy Chandramouli\n\nEric A. Hibbard\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-88r2\n\n\n\n## NIST Special Publication 800 NIST SP 800-88r2\n\n## Guidelines for Media Sanitization\n\nRamaswamy Chandramouli Computer Security Division Information Technology Laboratory\n\nEric A. Hibbard Samsung Semiconductor, Inc. This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-88r2\n\nSeptember 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nNational Institute of Standards and Technology\n\nCraig Burkhardt, Acting Under Secretary of Commerce for Standards and Technology and Acting NIST Director\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.2.1\n\nPhysical Security, Site, Facility DP Instal-\nlation\n\nFacility and installation access control are the\nOnly personnel whose\n\nfirst two levels of protection."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\nUnfortunately, security awareness efforts may face significant challenges. Industry surveys and research studies have discovered that security awareness programs in organizations of all sizes may be underfunded and often rely on part-time security awareness professionals who may lack sufficient background, skills, tools, or resources necessary for managing an effective program [SANS][WOELK][BADA][STEWART]. Furthermore, employees may view training as boring and burdensome [BADA]. While mandates enforce a minimum baseline for security awareness, when viewed simply as a 'check-the-box' exercise, organizations may begin to measure program success simply in terms of compliance metrics, like training completion rates. However, these metrics reveal little about the effectiveness of the training in changing and sustaining workforce attitudes and behaviors [FERTIG]."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.24 (NIST 3.1.24)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.1.24\n-  PI Interface for SNMP ReadOnly version 1."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.1.24", "cmmc_practice_id": "AC.L2-3.1.24", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication contains comprehensive updates to the Risk Management Framework . The updates include an alignment with the constructs in the NIST Cybersecurity Framework; the integration of privacy risk management processes; an alignment with system life cycle security engineering processes; and the incorporation of supply chain risk management processes. Organizations can use the frameworks and processes in a complementary manner within the RMF to effectively manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. Revision 2 includes a set of organization-wide RMF tasks that are designed to prepare information system owners to conduct system-level risk management activities. The intent is to increase the effectiveness, efficiency, and cost-effectiveness of the RMF by establishing a closer connection to the organization's missions and business functions and improving the communications among senior leaders, managers, and operational personnel. assess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n## Recommendation for Pair-Wise Key Establishment Using Integer Factorization Cryptography\n\n## Recommendation for Pair-Wise Key Establishment Using Integer Factorization Cryptography\n\nThis Recommendation specifies key-establishment schemes using integer factorization cryptography (in particular, RSA). Both key-agreement and key transport schemes are specified for pairs of entities, and methods for key confirmation are included to provide assurance that both parties share the same keying material. In addition, the security properties associated with each scheme are provided."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 8)"}, {"role": "assistant", "content": ". The requirements statements are presented as originally written in ISO/IEC 19790 Annex B and ISO/IEC 24759. These often include acronyms and abbreviations spelled out earlier within those documents.\nWhen the first use occurs within this document, the acronym or abbreviation will be spelled out within brackets immediately following the occurrence. These statements also include the British English standard spellings for the words 'zeroize' and 'authorize' as 'zeroise' and 'authorise'. ## Modifications\n\nModifications to ISO/IEC 24759 Section 6.14, Cryptographic module security policy , will follow a similar format as ISO/IEC 24759. For additions to test requirements, new Test Evidence (TE) or Vendor Evidence (VE) will be listed by increasing the 'sequence\\_number.' Modifications can include a combination of additions using underline and deletions using strikethrough. If no changes are required, the paragraph will indicate 'No change.'\n\nISO/IEC 19790 Annex B includes security policy requirements in bulleted form but does not include ways to format the required information. Modifications are addressed by adding formatting guidance (e.g., tables, images), adding underlined text, or using strikethrough for deletion. If no changes are required, the paragraph will indicate 'No change.' Additional guidance may also be included to address requirements presented in NIST Special Publication (SP) 800-140, SP 800-140A, SP 800-140C, SP 800-140D, SP 800-140E, and SP 800-140F. 1\n\n1 More information about the SP 800-140 subseries is available at https://csrc.nist.gov/projects/cmvp/sp800-140-series-info. ## Security Requirements\n\n## Changes to ISO/IEC 24759 Section 6.14 and ISO/IEC 19790 Annex B Requirements\n\nAll requirements from ISO/IEC 24759 Section 6.14 and ISO/IEC 19790 Annex B apply and are required in the security policy as applicable. ISO/IEC 19790 Annex B uses the same section naming convention as ISO/IEC 19790 Section 7 -Security requirements ."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 2)"}, {"role": "assistant", "content": "ion systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems.\nThis guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A-130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## National Institute of Standards and Technology Interagency Report 7916 276 pages (February 2013)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\nWhen the domain parameters ( p, q, g {, SEED, counter }) conform to a FIPS 186-type FFC parameter-size set (see Table 1), private keys are generated in the interval [1, q - 1], and the corresponding public keys are in the interval [2, p - 2]. For the key-pair generation methods in Sections 5.6.1.1.3 and 5.6.1.1.4, the value used for the input parameter N shall be len( q ), i.e., the bit length of the domain parameter q , and the value used for the input parameter s shall be 112, which is the security strength that can be supported by the FIPS 186-type FFC parameter-size set that was used to generate the domain parameters (see Table 1). The generated key pairs shall be used only for key-agreement purposes (see Section 6 for the approved key-agreement schemes), with the possible exception discussed in item 5 of Section 5.6.3.2.\n\nd. See Section 5.6.2.2.3.2.\n\nRecipients not acting in the role of a binding authority shall obtain this assurance - either through a trusted third party (see Section 5.6.2.2.3.1) or directly from the owner (i.e., the other party) (see Section 5.6.2.2.3.2) before using the derived keying material for purposes beyond those required during the key-agreement transaction itself. If the recipient chooses to obtain this assurance directly from the other party (i.e., the claimed owner of that public key), then to comply with this Recommendation, the recipient shall use one of the methods specified in Section 5.6.2.2.3.2."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 7)"}, {"role": "assistant", "content": "800-116 with revision 2 of FIPS 201 (FIPS 201-2). For example, credential validation is now required (see Section 4.4). The CHUID authentication mechanism has been deprecated due to security concerns.\nFor this reason, this publication marks the authentication mechanism as deprecated to signify that it is not a viable authentication mechanism to deploy for physical access control system (PACS). The CHUID data element on the PIV Card, however, remains a mandatory element as the BIO(-A) and SYMCAK authentication mechanisms use the data element as a source for the card's expiration date. It also provides unique identifiers for PACS ACLs. The previous version of this document also included the combined VIS + CHUID authentication mechanism as an option to transitioning from Unrestricted to Controlled areas. VIS + CHUID, however, is not included in this version of the document since it provides 'LITTLE or NO' confidence in the identity of the cardholder. Other changes in this version of the guideline include the removal of the migration strategy as PACS implementation in the Federal Government have moved beyond the described strategy and are more advanced. The future topics (i.e., global identifier and secure biometric match on card) have been addressed in FIPS 201-2 and associated technical specification and thus have become part of this version of guidelines rather than topics for future considerations. Finally, a new Appendix C describes possible improvements to PKI authentication for fast contactless transaction at access points. Appendix I, Revision History, provides a list of changes. This document focuses on the use of PIV Cards to gain access to federal buildings and facilities. It does not address non-PIV credentials that may be issued to populations that do not fall under the scope of HSPD-12 but require access to federal facilities. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 4)"}, {"role": "assistant", "content": "mes. This report de-\nscribes the evaluation criteria and selection process of the First Round of the Additional\nDigital Signatures for the NIST Post-Quantum Cryptography (PQC) Standardization Process.\nBased on public feedback and internal reviews of the first-round candidates, NIST selected\n14 candidate algorithms to move forward to the second round of evaluation: CROSS, FAEST,\nHAWK, LESS, MAYO, Mirath (merger of MIRA/MiRitH), MQOM, PERK, QR-UOV, RYDE, SDitH,\nSNOVA, SQIsign, and UOV. Keywords\n\ncryptography; digital signatures; post-quantum cryptography; quantum-resistant; quan-\ntum safe. Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops tests,\ntest methods, reference data, proof of concept implementations, and technical analyses\nto advance the development and productive use of information technology. ITL’s respon-\nsibilities include the development of management, administrative, technical, and physical\nstandards and guidelines for the cost-effective security and privacy of other than national\nsecurity-related information in federal information systems. i\n\n\fNIST IR 8528\nOctober 2024\n\nAdditional Digital Signatures\nFirst Round Status Report\n\nContents\n\n1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1. Purpose and Organization of This Document\n\n. . . . . . . . . . . . . . . . . . 2. Evaluation Criteria and the Selection Process . . . . . . . . . . . . . . . . . . . . . . 2.1. Acceptance of the First-Round Candidates . . . . . . . . . . . . . . . . . . . . 2.2. 2.3. Evaluation Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nDescription: Ensuring personnel are made aware of the security risks associated with their activities and of the applicable laws, directives, policies, standards, regulations, or procedures related to the security of organizational systems; and ensuring that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.\n\nRegularly provide basic and advanced security literacy training to new and existing staff. Customize the content to make it relevant -based on the systems that personnel have authorized access to, contextualized to the work environments of personnel (e.g., telework, shop floor), and tailored to the specific roles of personnel. The content should include:"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| | security requirements and risks during software design (secure by design) is key for improving software security and also helps improve development efficiency."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| ...................................................................................................\n3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| | Introduction ....................................................................................................1 | | |-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | 1.1 | | Purpose.......................................................................................................................1 | | | 1.2 | | Scope..........................................................................................................................2 | | | 1.3 | | Audience.....................................................................................................................3 | | | 1.4 | Document | Structure....................................................................................................4 | | | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n| | 5.4 Specific Details ........................................................................................................... | 5.4 Specific Details ........................................................................................................... | 5.4 Specific Details ..........................................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n| Incorporating Key Confirmation into a C(0e, 2s) Scheme ..............................\n107 6.3.3.1 C(0e, 2s) Scheme with Unilateral Key Confirmation Provided by Party |\n| | 6.3.3.2 | C(0e, 2s) Scheme with Unilateral Key Confirmation Provided by Party V to Party U...................................................................................... 109 |\n| | 6.3.3.3 | C(0e, 2s) Scheme with Bilateral Key Confirmation ......................... 110 |\n| 7. Rationale for Selecting a Specific Scheme........................................................ 112 | 7. Rationale for Selecting a Specific Scheme........................................................ 112 | 7. Rationale for Selecting a Specific Scheme........................................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 4)"}, {"role": "assistant", "content": "nterfeiting, Trojan insertion, and reverse engineering. In order to counteract these security risks, many types of solutions have been proposed, ranging from design to test phases of the supply chain.\nNumerous government-funded research programs have been established to develop countermeasures, such as the Defense Advanced Research Projects Agency (DARPA) Automated Implementation of Secure Silicon (AISS) program [1], the DARPA Structured Array Hardware for Automatically Realized Applications (SAHARA) program [2], the Naval Surface Warfare Center (NSWC) Crane State-of-the-Art Heterogeneous Integration Prototype (SHIP) program [3], the Air Force Research Laboratory (AFRL) Locked Electronics for Assured Design (LEAD) program [4], and the AFRL Aether Spy program [5], just to name a few, as addressing these security issues is crucial to national security. Dealing with such serious challenges necessitates directing security countermeasure initiatives in stages where the severity of the threat can be best diminished. Supply chain threat analysis is an essential component of security research. The goals of such analysis are to 1) identify the different threats and related vulnerabilities associated with integrated circuits, 2) analyze how severe the threats become at different stages of the supply chain, and 3) quantify the severity of threats due to collusion among adversaries. The first thing to acknowledge before beginning any such analysis is that, while there are many threats and related vulnerabilities, not all of them can be exploited at every stage in the semiconductor supply chain. Threats vary in severity depending on the stage of supply chain. For example, the risk of side-channel analysis is more common in chip use scenarios, whereas the risk of a hardware Trojan is more common in the early stages of design and manufacturing, as shown in Fig. 1. Fig. 1."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nSYSTEMS DEVELOPMENT AND MAINTENANCE PRACTICES\n6.1\n6.2\n6.3\n6.4\n\nManual Checking\nControl Totals\nTest Data\nIntegrated Test Facility\nTagging\nExtended Record Maintenance\nTracing\nMapping\nRecompilation\n\n1 . System Development and Maintenance Practices Audit\n2. Application Review\n3. Installation Security Review\nU. Security Function (Data Base/Communication Environ-\nment) Review\n5. Compromise Attempt."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nConducts research and provides measurements, data, standards, reference materials, quantitative understanding and other technical information fundamental to the processing, structure, properties and performance of materials; addresses the scientific basis for new advanced materials technologies; plans research around cross-cutting scientific themes such as nondestructive evaluation and phase diagram development; oversees Bureau-wide technical programs in nuclear reactor radiation research and nondestructive evaluation; and broadly disseminates generic technical information resulting from its programs."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nCryptographic techniques are potentially very useful to improve the security and privacy properties of IMDs through stronger authentication protocols and (confidentiality and integrity) protected communications over wireless channels. However, since IMDs operate in very constrained environments (such as device size, cost, and power availability,) traditional cryptographic techniques and protocols may be inappropriate. More compatible cryptographic suites and protocols need to be devised for use on IMDs and applied in a very selective manner to optimize the security protection from these power intensive operations. The body of research conducted for cryptography for sensor networks are directly applicable [8] to applying cryptographic techniques to IMDs.\n\n## A. Equipment Control and Recipe Integrity\n\n## B. Process Data Integrity"}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.11 (NIST 3.2.11)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.11. 3.2.11. 3.2.11."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.11", "cmmc_practice_id": "AT.L2-3.2.11", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| Chapter 1."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 10)"}, {"role": "assistant", "content": ".............................................................................11 |\n| 4. | PIV Authentication Mechanisms in PACS Applications ................................................\n12 |\n| 4.1 | PIV Authentication Mechanisms.................................................................................12 |\n| 4.2 | Authentication Factors.................................................................................................12 |\n| 4.3 | Selection of PIV Authentication Factors.....................................................................14 |\n| 4.4 | Credential Validation...................................................................................................19 |\n| 5. | PACS Use Cases.................................................................................................................. 21 |\n| 5.1 | Single-Tenant Facility .................................................................................................22 |\n| 5.2 | Federal Multi-Tenant Facility......................................................................................22 |\n| 5.3 | Mixed-Multi-Tenant Facility.......................................................................................23 |\n| 5.4 | Single-Tenant Campus ................................................................................................24 |\n| | 5.4.1 FSL I or II Campus......................................................................................... 24 |\n| | 5.4.2 FSL III Campus..............................................................................................."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 4)"}, {"role": "assistant", "content": "forma�on they need to implement a similar approach. The documents in this series describe example implementa�ons of cybersecurity prac�ces that businesses and other organiza�ons may voluntarily adopt.\nThese documents do not describe regula�ons or mandatory prac�ces, nor do they carry statutory authority. ## ABSTRACT\n\nThe Transport Layer Security (TLS) protocol is widely deployed to secure network traffic. TLS 1.3 protects the contents of its previous TLS communica�ons even if a TLS -enabled server is compromised. This is known as forward secrecy. The approach used to achieve forward secrecy in TLS 1.3 may interfere with passive decryp�on techniques that enterprises rely on to have visibility into their TLS 1.2 traffic. Enterprises' authorized network security staff rely on that visibility to protect its data and syste ms with cri�cal cybersecurity controls to meet opera�onal needs and legal requirements. Adop�on of the TLS 1.3 protocol can disrupt current approaches to observing and monitoring internal network communica�ons within an enterprise. The NCCoE, in collabora�on with technology providers and enterprise customers, ini�ated a project to demonstrate op�ons for maintaining visibility within the TLS 1.3 protocol using several standards-compliant builds that enterprises can use for real�m e and post-facto systems monitoring and analy�cs capabili�es. This publica�on contains demonstrated proofs of concept along with links to detailed technical informa�on online on NIST pages. This publica�on also includes links to mappings of TLS 1.3 visibility principles to commonly used security standards and guid elines. ## KEYWORDS\n\nbounded lifetime; break and inspect; ephemeral; key management; middlebox; passive decryption; passive inspection; protocol; Transport Layer Security (TLS); visibility. ## ACKNOWLEDGMENTS\n\nWe are grateful to the following individuals for their generous contribu�ons of exper�se and �me."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n□ Communications\n\n24. Which of the following topics have been addressed by your security awareness program via training courses, events, or other communications in the past 1-2 years? Check all that apply.\n\n□ Communications and marketing"}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by\nNIST in accordance with its assigned statutory responsibilities. The information in this publication,\nincluding concepts, practices, and methodologies may be used by federal agencies even before the\ncompletion of such companion publications. Thus, until each publication is completed, current\nrequirements, guidelines, and procedures, where they exist, remain operative. For planning and\ntransition purposes, federal agencies may wish to closely follow the development of these new\npublications by NIST. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . | . . . | 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|\n| 1.1. | Purpose and Organization of This Document . . . . | 3 |\n| 2. Evaluation Criteria and Selection Process . . | . . . . . . . . | 4 |\n| 2.1. | Acceptance of the Fourth-Round Candidates . . . . | 4 |\n| 2.2. | Evaluation Criteria . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.1. Security . . . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.2.Cost and Performance . . . . . . . . . . . . . | 5 |\n| | 2.2.3.Algorithm and Implementation Characteristics | 8 |\n| 2.3. | Selection of the Candidates for Standardization . . . | 8 |\n| 3. Summary of the Fourth-Round Candidates . | . . . . . . . . | 10 |\n| 3.1. | HQC . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nhe State of Maryland and Montgomery County, Maryland. The Technology Partners/Collaborators who participated in this build submitted their capabilities in response to a notice in the Federal Register.\nRespondents with relevant capabilities or product components were invited to sign a Cooperative Research and Development Agreement (CRADA) with NIST, allowing them to participate in a consortium to build this example solution. We worked with:"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\n## 3.1. Recruitment"}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n## Guide to Malware Incident Prevention and Handling for Desktops and Laptops\n\n## Guide to Malware Incident Prevention and Handling for Desktops and Laptops\n\nMalware, also known as malicious code, refers to a program that is covertly inserted into another program with the intent to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Malware is the most common external threat to most hosts, causing widespread damage and disruption and necessitating extensive recovery efforts within most organizations. This publication provides recommendations for improving an organization's malware incident prevention measures. It also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n.......................................................................................... 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ...............................................\n19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ..............................................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nThe National Bureau of Standards, with the support of the U.S. Gen-\neral Accounting Office, sponsored an invitational workshop on \"Audit and\nEvaluation of Computer Security,\" held in Miami Beach, Florida on March\n22-24, 1977.\narea and define appropriate subjects for future research.\nperts in the audit and computer communities were invited to discuss the\nsubject in one of ten sessions, each of which considered a different as-\npect.\nthese reports form the body of these Proceedings.\nThe ten topics re-\nported on are: Internal Audit Standards, Qualifications and Training,\nSecurity Administration, Audit Considerations in Various System Environ-\nments, Administrative and Physical Controls, Program Integrity, Data In-\ntegrity, Communications, Post-Processing Audit Tools and Techniques, and\nInteractive Audit Tools and Techniques.\n\nKEYWORDS:\ntraining, communications security, computer controls, computer\nsecurity, data integrity, interactive audit, internal audit, post-\nprocessing audit, program integrity.\n\n........\n....\nInternal Audit Standards\nQualifications and Training ............\n.....\nSecurity Administration\nAudit Considerations in Various System\n.....\nEnvironments\nAdministrative and Physical Controls .......\n.....\nProgram Integrity\nData Integrity\nCommunications\nPost-Processing Audit Tools and Techniques ....\nInteractive Audit Tools and Techniques"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” support CMMC certification?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nn Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562.\nhttps://doi.org/10.6028/NIST.IR.8562\n\n## Author ORCID iDs\n\nKaterina Megas: 0000-0002-2815-5448 Michael Fagan: 0000-0002-1861-2609 Barbara Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Abstract\n\nThis report summarizes the feedback received by the NIST Cybersecurity for the Internet of Things (IoT) program at the in-person and hybrid workshop on \"Updating Manufacturer Guidance for Securable Connected Product Development\" held in December 2024. The purpose of this workshop was to consider how to update Foundational Cybersecurity Activities for IoT Device Manufacturers (NIST Internal Report (IR) 8259) based on concepts in risk management, operational technology concerns, product end of life concerns and recent trends in IoT cybersecurity and privacy. Over time, the NIST volume of work has built upon the concepts introduced in NIST IR 8259,to add technical (NIST IR 8259A) and nontechnical (NIST IR 8259B) concepts to help manufacturers and customers consider the cybersecurity of IoT devices. The NIST IR 8259 series has been used to inform and develop subsequent publications that elaborate on IoT cybersecurity across sectors and use cases (e.g., federal agency uses cases reflected in NIST SP 800-213 and consumer use cases reflected in NIST IR 8425 and the U.S. Cyber Trust Mark). ## Keywords\n\ncybersecurity baseline; Internet of Things (IoT); IoT products; manufacturing; privacy; risk management; securable products; security requirements; software development; threat modelling. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nAssessment (evaluación). System Inventory (inventario del sistema). User Inventory (inventario de usuarios). Business Process Review Risk Assessment and Policy Development políticas). Deployment (implementación). Operations (operaciones).\n\nSe trata de las brechas que afectan a la implementación y despliegue iniciales de la ZTA y a la continuidad de su funcionamiento y madurez. Estas podrían ralentizar la adopción de la ZTA en las organizaciones o provocar la fragmentación de la industria de componentes de ZTA. Los estándares abiertos (producidos por organizaciones de desarrollo de estándares [SDO, por su desarrollo en inglés Standards Development Organization] o un consorcio industrial) podrían ayudar en estas brechas sistémicas."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\n| [SP162] | Hu VC, Ferraiolo DF, Kuhn DR, Schnitzer A, Sandlin K, Miller R, Scarfone KA (2014) Guide to Attribute Based Access Control (ABAC) Definition and Considerations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-162, Includes updates as of August 02, 2019. https://doi.org/10.6028/NIST.SP.800-162 |\n|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [SP205] | Hu VC, Ferraiolo DF, Kuhn DR (2019) Attribute Considerations for Access Control Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-205. https://doi.org/10.6028/NIST.SP.800-205 |\n| [XACML] | OASIS eXtensible Access Control Markup Language (XACML) TC (2020) Organization for the Advancement of Structured Information Standards . Available at https://www.oasis- open.org/committees/tc_home.php?wg_abbrev=xacml |\n| [ZZH] | Zhai P, Zhang L, He J (2021) A Review of Blockchain-Based Access Control for the Industrial IoT. CONVERTER 2021(3):308-316. https://doi.org/10.17762/converter.62 |"}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nnt provides a high-level overview of the mSCP, its components, and some common use cases. It refers readers to the online project documentation for in-depth technical information and use instructions.\nThis document is intended to be independent of macOS version releases; updates will be released as needed when there are substantial changes to the mSCP. Updates from the previous release of this document mainly involve the new mSCP capability to create a custom benchmark by tailoring a baseline."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Non-Technical Supporting Capability Core Baseline provide? (Part 5)"}, {"role": "assistant", "content": "publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication.\n## Table of Contents\n\n| 1 | Introduction ............................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|\n| 2 | The IoT Non-Technical Supporting Capability Core Baseline............................4 |\n| References...................................................................................................................11 | References...................................................................................................................11 |\n| Appendix A-Acronyms............................................................................................13 | Appendix A-Acronyms............................................................................................13 |\n| Appendix B-Glossary ..............................................................................................14 | Appendix B-Glossary ..............................................................................................14 |\n\n## 1 Introduction\n\nInternet of Things (IoT) devices often lack built-in device cybersecurity capabilities, as well as non-technical support relevant to cybersecurity."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\n| | Introduction ..................................................................................................................... | Introduction ..................................................................................................................... |\n|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology.......................................................................................................... 2 | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology.........................................................................................................."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-06-29 Supersedes NIST SP 800-219 (June 2022) https://doi.org/10.6028/NIST.SP.800-219\n\n## How to Cite this NIST Technical Series Publication:\n\nTrapnell M, Trapnell E, Souppaya MP, Gendler B, Brodjieski D, Golbig A, Scarfone K, Heiserman B (2023) Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-219r1. https://doi.org/10.6028/NIST.SP.800-219r1\n\n## Author ORCID iDs\n\nMark Trapnell: 0000-0002-5266-3610\n\nEric Trapnell: 0000-0001-9315-3732\n\nMurugiah Souppaya: 0000-0002-8055-8527\n\nBob Gendler: 0000-0002-8928-6492\n\nKaren Scarfone: 0000-0001-6334-9486\n\n## Contact Information\n\napplesec@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe macOS Security Compliance Project (mSCP) provides resources that system administrators, security professionals, security policy authors, information security officers, and auditors can leverage to secure and assess macOS desktop and laptop system security in an automated way. This publication introduces the mSCP and gives an overview of the resources available from the project's GitHub site, which is continuously curated and updated to support each new release of macOS."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nCMVP; Cryptographic Module Validation Program; FIPS 140; FIPS 140 testing; ISO/IEC 19790; ISO/IEC 24759; security policy; testing requirement; vendor documentation; vendor evidence.\n\nThis document is intended for vendors, testing labs, and CMVP to address issues in ISO/IEC 19790, Information technology - Security techniques - Security requirements for cryptographic modules , and ISO/IEC 24759, Information technology - Security techniques - Test requirements for cryptographic modules .\n\nThis document specifies the Cryptographic Module Validation Program (CMVP) modifications of the methods to be used by a Cryptographic and Security Testing Laboratory (CSTL) to demonstrate conformance. This document also specifies the modification of documentation for providing evidence to demonstrate conformity. Unless otherwise specified in this document, the test requirements are specified in ISO/IEC 19790 Annex B and ISO/IEC 24759 Section 6.14."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 6)"}, {"role": "assistant", "content": "cybersecurity education and awareness plan..7 |\n| Fig. 4.\nMock-up of how cybersecurity education and awareness information could be delivered via the app. ..........................................................................................................................................8 |\n| Fig. 5. Example of the quick start manual proposed to support the product. ........................................9 |\n| Fig. 6. An example of a cybersecurity-targeted newsletter proposed by the team.............................. 10 |\n| Fig. 7. Planning notes for Team 3's cybersecurity education and awareness strategy. ........................ 11 |\n| Fig. 8. A detailed user narrative was developed to hone cybersecurity education and awareness approaches. ( Note: cropping of text is due to framing of the source image ) ............................ 11 |\n| Fig. 9. The team's mock-up of a guided and gamified approach that could be used to support cybersecurity education and awareness.................................................................................. 12 |\n| Fig. 10."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\ngement, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems.\nThe Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\n--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2.\nBackground......................................................................................................................................2 |\n| 3. Report from the Design-A-Thon .......................................................................................................4 |\n| 4. Designs ............................................................................................................................................6 |\n| 5. Discussion......................................................................................................................................14 |\n| References.........................................................................................................................................16 |\n| Appendix A. Call for Participants........................................................................................................18 |\n| Appendix B. Mock Product Data Cards............................................................................................... 19 |\n| Appendix C."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nInformation systems are vulnerable to a variety of disruptions, ranging from mild (e.g., short-term power outage, disk drive failure) to severe (e.g., equipment destruction, fire). Much vulnerability may be minimized or eliminated through management, operational, or technical controls as part of the organization's resiliency effort; however, it is virtually impossible to completely eliminate all risks. 6 Contingency planning is designed to mitigate the risk of system and service unavailability by providing effective and efficient solutions to enhance system availability.\n\nAn organization must have the ability to withstand all hazards and sustain its mission through environmental changes. These changes can be gradual, such as economic or mission changes, or sudden, as in a disaster event. Rather than just working to identify and mitigate threats, vulnerabilities, and risks, organizations can work toward building a resilient infrastructure, minimizing the impact of any disruption on mission essential functions.\n\nCOOP focuses on restoring an organization's mission essential functions (MEF) at an alternate site and performing those functions for up to 30 days before returning to normal operations. Additional functions, or those at a field office level, may be addressed by a BCP. Minor threats or disruptions that do not require relocation to an alternate site are typically not addressed in a COOP plan."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nThe supply chains of information and communications technologies are increasingly at risk of compromise. Additional risks causing supply chain disruptions include counterfeiting, unauthorized production, tampering, theft, and insertion of unexpected software and hardware. Managing these risks requires ensuring the integrity of the supply chain and its products and services. This project demonstrates how organizations can verify that the internal components and system firmware of the computing devices they acquire are genuine and have not been unexpectedly altered during manufacturing, distribution, or operational use.\n\nThe supply chains of information and communications technologies are increasingly at risk of compromise. Additional risks causing supply chain disruptions include counterfeiting, unauthorized production, tampering, theft, and insertion of unexpected software and hardware. Managing these risks requires ensuring the integrity of the cyber supply chain and its products and services. This prototype implementation demonstrates how organizations can verify that the internal components of the computing devices they acquire are genuine and have not been unexpectedly altered during manufacturing or distribution processes.\n\nSection 4, Architecture, specifies the components of the prototype implementation and details how data and communications flow between validation systems."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nblication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Acquisition or procurement responsibilities (e.g., contracting officers)\n- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts)"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n2.4.1.\nThe verifier SHALL employ appropriately tailored security controls from the moderate\nbaseline security controls defined in [SP800-53] or an equivalent federal (e.g.,\n[FEDRAMP]) or industry standard that the organization has chosen for the information\nsystems, applications, and online services that these guidelines are used to protect.\n\n3.1.3.4. Multi-Factor Out-of-Band Authenticators\nMulti-factor out-of-band authenticators operate similarly to single-factor out-of-band\nauthenticators (see Sec. 3.1.3.1). However, they require the presentation and verification\nof an activation factor (i.e., a password or a biometric characteristic) before allowing the\nclaimant to complete the authentication transaction (i.e., before accessing or entering\nthe authentication secret as appropriate for the authentication flow being used). Each\nuse of the authenticator SHALL require the presentation of the activation factor.\n\n3.2.3.4. Use of Biometric Samples\nBiometric samples collected in the authentication process MAY be used locally within\nthe authenticator or verifier performing the biometric comparison to update the\ntemplates for the purpose of compensating for changes in subscriber characteristics or\n— with explicit subscriber consent — other research purposes. The biometric samples\nand any other biometric data derived from them SHALL be erased immediately after\nany adaptation or research data has been derived. A limit on the allowable time for\nadaptation SHALL be established and enforced by the authenticator or the CSP."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nC\n\nOne important characteristic of the management zone is that it has a separate security posture because non-privileged users do not need to access the management servers or services in a direct way.\nPrivileged users responsible for configuring, maintaining, and operating the HPC system access the management zone servers and switches through extra security controls. For example, from the public-facing login nodes, they may go through a bastion host that is typically located in the management zone, or they may establish a virtual private network (VPN) with separate authentication and authorization or other appropriate security controls to reach the management zone. All systems are configured on networks that are not routed beyond the perimeter of the HPC system so that only nodes like compute nodes and storage nodes can access the services."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nZero trust provides a collection of concepts designed to minimize uncertainty in enforcing accurate, least privilege per-request access decisions in information systems and services in the face of a network viewed as contested. That is, there may be a malicious actor on the network that can intercept or initiate communication. Zero trust is fundamentally comprised of a set of principles upon which information technology architectures are planned, deployed, and operated [1]. Zero trust uses a holistic view that considers potential risks to a given mission or business process and how they are mitigated. As such, there is no single specific zero trust infrastructure implementation or architecture. zero trust solutions depend on the workflow (i.e., part of the enterprise mission) being analyzed and the resources that are used in performing that workflow. zero trust strategic thinking can be used to plan and implement an enterprise IT infrastructure, this plan is called a zero trust architecture (ZTA). - I. All resource authentication and authorization are dynamic and strictly enforced before access is allowed. A typical enterprise has a wide collection of network identities: end users, accounts used by processes and services, etc. Some end users may have multiple network identities, and some identities may only be used by\n\n1 The unit of 'session' can be nebulous and differ depending on tools, architecture, etc. The basic definition in a zero trust context is a connection to one resource utilizing one network identity and one privilege for that identity (e.g. read, write, delete, etc.) or even a single operation (similar to an API call)."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThe common language helps facilitate communications about secure software practices among both internal and external organizational stakeholders, such as: | Practices | Tasks | Notional Implementation Examples | References | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | PO.2.3 : Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development- related roles and responsibilities."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nt information systems that provide public access services, the same controls might not be required for users accessing those systems through public interfaces to obtain publicly available information.\nOn the other hand, identification and authentication must be required for users accessing information systems through public interfaces to access their private/personal information."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.5 (NIST 3.1.5)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.1.5 Challenges: Required Training... 3.1.5 Challenges: Required Training... 3.1.5 Challenges: Required Training\n\nParticipants rated their challenges with required training on a four-point scale ranging from 'very challenging' to 'not at all challenging,' with a 'does not apply' (N/A) option (see Figure 5)."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "nist_control": "3.1.5", "cmmc_practice_id": "AC.L2-3.1.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide?"}, {"role": "assistant", "content": "\n\n## NIST Interagency Report NIST IR 8562\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nKaterina N. Megas Michael Fagan Barbara Cuthill Brad Hoehn Evie Petrella\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8562\n\n\n\n## NIST Interagency Report NIST IR 8562\n\n## Summary Report for ' Workshop on Updating Manufacturer Guidance for Securable Connected Product Development '\n\nKaterina N. Megas Michael Fagan Barbara Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nBrad Hoehn HII\n\nEvie Petrella Electrosoft Services, Inc. This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8562\n\nApril 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nNational Institute of Standards and Technology\n\nCraig S. Burkhardt, Acting NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-03-21\n\n## How to Cite this NIST Technical Series Publication\n\nMegas K, Fagan M, Cuthill B, Hoehn N, and Petrella E (2025) Summary Report for 'Workshop on Updating Manufacturer Guidance for Securable Connected Product Development' (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8562."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n.13.1.2 | SP-ARC-001 |\n| DETECT (DE) | Anomalies and Events (DE.AE) | DE.AE-2: Detected events are analyzed to understand attack tar- gets and methods.\n| AU-6, CA-7, IR-4, SI-4 | A.12.4.1, A.16.1.1, A.16.1.4 | PR-CDA-001 |\n| DETECT (DE) | Anomalies and Events (DE.AE) | DE.AE-3: Event data are collected and correlated from multiple sources and sensors. | AU-6, CA-7, IR-4, IR-5, IR-8, SI-4 | A.12.4.1, A.16.1.7 | CO-OPS-001, PR-CIR-001 |\n| DETECT (DE) | Anomalies and Events (DE.AE) | DE.AE-4: Impact of events is determined. | CP-2, IR-4, RA-3, SI-4 | A.16.1.4 | PR-INF-001 |"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 4)"}, {"role": "assistant", "content": "| INTRODUCTION.................................................................................................................\n1 | INTRODUCTION................................................................................................................. 1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | STUDY METHODOLOGY................................................................................................. 2 | STUDY METHODOLOGY................................................................................................. 2 |\n| 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 | 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 | 2.1 FOCUS GROUP METHODOLOGY............................................................................................ 3 |\n| 2.1.1 | Focus Group Design..................................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.1.2 | Brief Overview of the Scheme | Brief Overview of the Scheme | 47 |\n| 3. 3.1.2 Brief Overview of the Scheme\n\nThe Scheme described in this Chapter enables its user to systematically perform a riskbased evaluation ofthe subjects for ADP audit (or security review) within an organization (i."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.4.1. 3.4.1."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 7)"}, {"role": "assistant", "content": "or even individual supervisors. - RBT content: About two-thirds of surveyed participants said that their organizations create at least some RBT content on their own, which could be resource-intensive.\nThose who purchase training may find the cost to obtain content for many cybersecurity roles to be prohibitive. Indeed, over 40% of survey participants rated finding RBT materials and updating RBT as moderately or very challenging. On the upside, the majority (about 60%) said that their RBT content is tailored to their organizational mission and current security threats. - RBT approaches: Almost all survey participants (95%) said their organizations offered at least some online training, while over half also allow live training options. Almost half utilize industry-recognized certifications to fulfill RBT requirements. - Compliance with mandatory RBT requirements: Most organizations do not experience substantial challenges in tracking employee completion of RBT. Still, over a third are using a manual method (e.g., a spreadsheet) for tracking. Additionally, about 40% of organizations were moderately or very challenged in getting employees to complete training by the appointed deadline. This may be due to training overload, employee time constraints, or a lack of concrete consequences for not completing training. - Organizational support for RBT: More than two-thirds of survey participants believed that organizational employees and leadership were supportive of RBT activities. Over 70% said they have adequate technology to support RBT activities. However, 42% disagreed that they have adequate funding and 52% disagreed that they have adequate staff for conducting RBT activities. - Measuring RBT effectiveness: Just over half of survey participants rated their RBT activities as moderately or very successful."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n- [RFC 4492] Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS), May 2006, see https://tools.ietf.org/html/rfc4492. - [RFC 5903] Elliptic Curve Groups Modulo a Prime (ECP Groups) for IKE and IKEv2, June 2010, see https://tools.ietf.org/html/rfc5903. - [RFC 7919] Negotiated Finite Field Diffie-Hellman Ephemeral Parameters, August 2016, see https://tools.ietf.org/html/rfc7919. - [SECG] Standards for Efficient Cryptography Group, see http://www.secg.org/. - [SEC2] Standards for Efficient Cryptography, SEC 2: Recommended Elliptic Curve Domain Parameters, September 2000, see http://www.secg.org/SEC2-Ver1.0.pdf. - [SP 800-38B] Special Publication 800-38B, Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication , May 2005, with updates dated October 2016. https://doi.org/10.6028/NIST.SP.800-38B\n- [SP 800-38C] Special Publication 800-38C, Recommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentiality , May 2004, with updates dated July 2007. https://doi.org/10.6028/NIST.SP.800-38C\n- [SP 800-38F] Special Publication 800-38F, Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping , December 2012. https://doi.org/10.6028/NIST.SP.800-38F\n- [SP 800-52] Special Publication 800-52 Revision 2 (DRAFT), Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations , November 15, 2017. https://csrc.nist.gov/publications/detail/sp/800-52/rev-2/draft\n- [SP 800-56B] Special Publication 800-56B Revision 1, Recommendation for Pair-Wise Key-Establishment Schemes Using Integer Factorization Cryptography , September 2014. https://doi.org/10.6028/NIST.SP.800-56Br1\n- [SP 800-56C] Special Publication 800-56C Revision 1, Recommendation for Key Derivation Methods in Key Establishment Schemes , April 2018."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/232/final, including related content, potential updates, and document history.\n\nThe substitution layer 𝑝 𝑆 updates the state S with 64 parallel applications of the 5-bit substitution box SBOX as\n\n- 𝑐𝑡𝑥 ← Ascon-XOF128 .Absorb( 𝑐𝑡𝑥 , str ) Absorbs an arbitrary-length input str into the state and updates the context 𝑐𝑡𝑥 . Restriction: May be called multiple times after Init , but cannot be called after any call to Squeeze .\n- ( 𝑐𝑡𝑥 , 𝑜𝑢𝑡 ) ← Ascon-XOF128 .Squeeze( 𝑐𝑡𝑥 , 𝐿 ) and"}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\n- Delineate responsibilities, expected use of system, and behavior of all users.\n- Describe appropriate limits on interconnections.\n- Define service provisions and restoration priorities.\n- Describe consequences of behavior not consistent with rules.\n- Covers the following topics:\n- o Work at home\n- o Dial-in access\n- o Connection to the Internet\n- o Use of copyrighted work\n- o Unofficial use of government equipment\n- o Assignment and limitations of system privileges and individual accountability\n- o Password usage\n- o Searching databases and divulging information.\n\nThe first item listed in the system security plan is the system name and identifier. As required in OMB Circular A-11, each system should be assigned a name and unique identifier. Assignment of a unique identifier supports the agency's ability to easily collect agency information and security metrics specific to the system as well as facilitate complete traceability to all requirements related to system implementation and performance. This identifier should remain the same throughout the life of the system and be retained in audit logs related to system use.\n\nAn authorizing official must be identified in the system security plan for each system. This person is the senior management official who has the authority to authorize operation (accredit) of an information system (major application or general support system) and accept the residual risk associated with the system. The assignment of the authorizing official should be in writing, and the plan must include the same contact information listed in Section 3.3."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n## Conformance Testing\n\nConformance testing for implementations of this Recommendation will be conducted within the framework of the Cryptographic Algorithm Validation Program (CAVP) and the Cryptographic Module Validation Program (CMVP). The requirements of this Recommendation are indicated by the word ' shall .' Some of these requirements may be out-of-scope for CAVP or CMVP validation testing, and thus are the responsibility of entities using, implementing, installing or configuring applications that incorporate this Recommendation.\n\nThe RSA private key may be expressed in several formats. The basic format of the RSA private key consists of the modulus n and a private-key exponent d that depends on n and the public-key exponent e ; this format is used to specify the RSA primitives and operations in Section 7. The other two formats may be used in implementations, but may require appropriate modifications for correct implementation. To facilitate implementation testing, the format for the private key shall be one of the following:"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 5)"}, {"role": "assistant", "content": "|\n| Table 1. Variables for the Expected_Exploited() Equation....................................................................5 | Table 1.\nVariables for the Expected_Exploited() Equation....................................................................5 |\n| Table 2. Variables for the Expected_Exploited() Equation....................................................................6 | Table 2. Variables for the Expected_Exploited() Equation....................................................................6 |\n| Table 3. Variables and Functions for the Composite_Probability() Equation.........................................7 | Table 3. Variables and Functions for the Composite_Probability() Equation.........................................7 |\n| Table 4. Variable and Function for the LEV and LEV2 Equations...........................................................8 | Table 4. Variable and Function for the LEV and LEV2 Equations...........................................................8 |\n| Table 5. Proportion of expected exploited on 2025-01-16 .................................................................18 | Table 5. Proportion of expected exploited on 2025-01-16 .................................................................18 |\n| List of Figures | List of Figures |\n| Fig. 1."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n- Harden software, such as enforcing the principles of least privilege and least functionality (e.g., deactivating or uninstalling software services, features, and other components that are not needed). For additional information on hardening assets, especially those considered critical, see the NIST publication Security Measures for 'EO-Critical Software' Use Under Executive Order (EO) 14028 (July 9, 2021). - Acquire software that is likely to have fewer vulnerabilities over time compared to other software. - Work with software development partners that are likely to introduce fewer vulnerabilities into software over time, taking into consideration factors such as how rigorous their secure software development practices are, how quickly they address issues and release patches, how often problems are associated with their patches, and how transparent they are in their security-related communications. - Use managed services instead of software when feasible. 1. Will you be releasing updates for this software to address vulnerabilities? 2. Approximately how many patches, updates, and upgrades do you expect to release each year for this software? On average, how quickly do you expect to address each vulnerability and release a patch? Do you bundle patches together or is each patch separate? How often do you anticipate releasing emergency updates? 3. For how many years are you committed to correcting vulnerabilities in the software? 4. Will you release updates on a regular schedule, as needed, or both? If a schedule will be followed, what is that schedule (weekly, monthly, quarterly, etc.)? 5. Do you have a vulnerability disclosure and incident response program for your software? How transparent are you in your security-related communications to your customers? 6. When a vulnerability in your software becomes public but a patch, update, or upgrade is not available, how do you recommend that customers protect their computing assets running your software?"}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nDEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..................................................................................\n7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................"}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\ngs and relationships between the security standards and guidelines developed by NIST, the\nInternational Organization for Standardization (ISO), and the International Electrotechnical Commission\n(IEC).\nIdentify determination statements for organization-defined parameters (ODPs) first and separately\nfrom the determination statements for each control item;\nImprove the readability of the assessment procedures;\nProvide a structured schema for automated tools when assessment information is imported into such\ntools;\nProvide greater flexibility in conducting assessments by giving organizations the capability to target\ncertain aspects of controls (highlighting the particular weaknesses and/or deficiencies in controls),\nImprove the efficiency of security and privacy control assessments;\nSupport continuous monitoring and ongoing authorization programs by providing a greater number\nof component parts of security and privacy controls that can be assessed at organization-defined\nfrequencies and degrees of rigor."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nNoSQL systems can handle fast-paced agile development, the storage of large volumes of structured and semi-structured data, the requirements for scale-out architecture, and modern application paradigms (e.g., microservices and real-time streaming) [MO]. However, they also face many challenges with regard to access control, such as a lack of proper authentication, encryption, dynamic model support, and fine-grained authorization (as described in Sec. 3.3). Therefore, careful considerations need to be made when implementing access control on NoSQL databases to address these issues effectively.\n\nDue to NoSQL's distributed nature, security becomes a more significant concern compared to central management-oriented RDBMS. From the perspective of data at rest and data in transit (i.e., communications between databases), NoSQL databases generally provide weaker security features when compared to RDBMS.\n\nThe security of data in transit and communications in horizontally scaled NoSQL databases is a critical issue. Some systems use symmetric key algorithms to encrypt data based on the NoSQL structure (i.e., types). For example, in a key-value system, the value of the key is the encrypted data, including all of the other key values being concatenated and encrypted. When a query is created, the system retrieves data entities and then uses the symmetric key to decrypt the data [ZM]. As a result, the data is protected by encryption even if the key is intercepted while in transit between different NoSQL hosts."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Contingency Planning Guide for Federal Information Systems provide? (Part 2)"}, {"role": "assistant", "content": ", other than the ones noted above, are available at http://csrc.nist.gov/publications. National Institute of Standards and Technology Special Publication 800-34 Natl. Inst. Stand. Technol. Spec. Publ.\n800-34, 150 pages (May 2010) CODEN: NSPUE2\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in federal computer systems. This Special Publication 800-series reports on ITL's research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. ## Authority\n\nThis document has been developed by the National Institute of Standards and Technology (NIST) in furtherance of its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, Public Law 107-347. NIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), 'Securing Agency Information Systems,' as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8532/final, including related content, potential updates, and document history.\n\nSemiconductor-based hardware is the foundation of modern-day electronics - from smartphones, computers, and telecommunications to transportation and critical infrastructure. The semiconductor hardware supply chain is a complex network of companies that collectively provide intellectual property, designs, and raw materials and manufacture, test, package, and distribute products. Coordination among the components of a supply chain is required at different stages, including inception, deployment to end users, maintenance during use, and disposal or end of life. Securing semiconductor-based hardware and their supply chains help protect sensitive information, maintain the integrity of systems, and ensure overall stability across the infrastructure and connected world.\n\nThese activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n7-12\n7-12\n7-13\n7-13\n7-13\n....... 7-13\nDesign Standards o\n7-14\nOrganization Control .\n7-14\nAccess Control .\n7-15\nPhase Review/Project Control\nTesting/System Assurance ........ ^\n7-16\n7-16\nPromotion Process\nDocumentation ............... 7-17\n7-17\nAuditor/Independent Party Involvement\nConfiguration Management .......... 7-17\nEmergency Procedures ........... 7-18\n\ncategories: physical, system and administrative.\nThe physical con-\ntrols include the traditional \"put the system in a vault\" measures,\nincluding perimeter control, hazard protection and backup mechanisms.\nSystem controls include hardware/software access control techniques,\nprogram integrity measures, audit trail techniques and failure re-\nAdministrative control techniques include what\nsponse procedures.\nare commonly referred to as Change Control Procedures.\ncontrol techniques must be evaluated against each of the access con-\ntrol, accuracy, and availability factors and an overall score must be\narrived at for each of those factors.\n\nDevelopment procedures - standards, configuration management,\ncertification, etc."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\nMean for Your Hardware? Available at https://evernex.com/industry-guide/eol-meaning/\n- [9] Vincent J (2018) Chinese spies reportedly inserted microchips into servers used by Apple, Amazon, and others.\nAvailable at https://www.theverge.com/2018/10/4/17935868/-chinese-spies-microchip-hackservers-apple-amazon-supermicro\n- [10] Yu S, Liu W, O'Neill M (2019) An improved automatic hardware Trojan generation platform. IEEE Computer Society Annual Symposium on VLSI (ISVLSI) (IEEE, Miami, Florida), pp 302-307. https://doi.org/10.1109/ISVLSI.2019.00062\n- [11] Cruz J, Huang Y, Mishra P, Bhunia S (2018) An automated configurable Trojan insertion framework for dynamic trust benchmarks. Design, Automation & Test in Europe Conference & Exhibition (IEEE, Dresden, Germany) pp 1598-1603. https://doi.org/10.23919/DATE.2018.8342270\n- [12] Perez TD, Pagliarini S (2023) Hardware Trojan insertion in finalized layouts: From methodology to a silicon demonstration. IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems (IEEE) 42(7): 2094-2107. https://doi.org/10.1109/TCAD.2022.3223846"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 10)"}, {"role": "assistant", "content": "| AWARENESSANDTRAINING...............................................................................................................\n| 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT..................................................................................................... | 11 |\n| 3.5 | IDENTIFICATION ANDAUTHENTICATION.......................................................................................... | 13 |\n| 3.6 | INCIDENT RESPONSE......................................................................................................................... | 15 |\n| 3.7 | MAINTENANCE ................................................................................................................................. | 16 |\n| 3.8 | MEDIAPROTECTION........................................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nthe Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies.\nThe scope of this publication pertains to federal information systems, which are discrete sets of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information, whether such information is in digital or non-digital form. Information resources include information and related resources, such as personnel, equipment, funds, and information technology."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nhin the ADP Facility - Both errors and intentional acts committed by the ADP operations staff may result in improper operational procedures, lapsed controls, and losses in storage media and output. 6.\nProgram Errors - Applications programs should be developed in an environment that requires and supports complete, correct, and consistent program design, good programming practices, adequate testing, review, and documentation, and proper maintenance procedures. Although programs developed in such an environment may still contain undetected errors, programs not developed in this manner will probably be rife with errors. Additionally, programmers can deliberately modify programs to produce undesirable side effects or they can misuse the programs they are in charge of. 7. Operating System Flaws - Design and implementation errors, system generation and maintenance problems, and deliberate penetrations resulting in modifications to the operating system can produce undesirable effects in the application system. Flaws in the operating system are often difficult to prevent and detect. 8. Communications System Failure - Information being routed from one location to another over communication lines is vulnerable to accidental failures and to intentional interception and modification by unauthorized parties."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 5)"}, {"role": "assistant", "content": "other attacks. By leveraging hardware roots of trust capabilities as a computing device traverses the supply chain, we can maintain trust in the computing device throughout its operational lifecycle.\nThis project addresses several processes, including:\n\n-  how to create verifiable descriptions of components and platforms, which may be done by original equipment manufacturers (OEMs), platform integrators, and even information technology (IT) departments;\n-  how to verify devices and components within the single transaction between an OEM and a customer; and\n-  how to verify devices and components at subsequent stages in the system lifecycle in the operational environment. This project also demonstrates how to inspect the verification processes themselves. The following is a list of the project's collaborators. ## Collaborator\n\n\n\n## Security Capability or Component\n\nIntegrated Risk Management Platform, Incident Management, Integrating Data from Asset Discovery and Management and Security Information and Event Management (SIEM) Systems\n\nManufacturer, Platform Integrity Validation System\n\nPlatform Integrity Validation System\n\n\n\n\n\n\n\n\n\n\n\n\n\nManufacturer, Platform Integrity Validation System\n\nManufacturer, Platform Integrity Validation System\n\nSecurity Information and Event Management\n\nManufacturer, Platform Integrity Validation System\n\nCertificate Authority, Platform Integrity Validation System\n\nManufacturer, Platform Integrity Validation System\n\nWhile the NCCoE used a suite of commercial products to address this challenge, this guide does not endorse these particular products, nor does it guarantee compliance with any regulatory initiatives. Your organization's information security experts should identify the products that will best integrate with your existing tools and IT system infrastructure."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n1. Concept: Concept stage is the birthplace of an Integrated Circuit (IC). At this stage, the goals and purpose of an integrated circuit (IC) are formulated, and the scope and target of a hardware component are discussed. Customers, the design, planning, finance teams, and other key stakeholders are involved at this stage. 2. Design: Design stage gives a form to the ideas generated in the concept stage. This is the stage where prototypes of the concept are created with the help of different Computer Aided Design (CAD) tools and analysis of whether the goals identified during the concept stage are met. This stage also includes the use of third-party software and hardware prototyping. 3. Integration: Integration is the stage where different design components from designers and third parties are integrated together. This phase is crucial since many design elements already have tested solutions, so not everything needs to be created from the ground up. It is more feasible to purchase these solutions from third parties and integrate them into the design. 4. Manufacturing: After the IC's design is finished, the manufacturing phase begins. This stage includes several processes, including fabrication and packaging. Due to the high cost of building and maintaining manufacturing facilities, many design houses are fabless and outsource their designs to manufacturers located elsewhere. 5. Testing: Testing is the stage at which manufactured Integrated Circuits (ICs) are tested to ensure that they perform properly. Following the completion of fabrication, each IC undergoes testing. An IC's functionalities are tested here to make sure they adhere to design specifications. 6. Provisioning: Provisioning is the stage where standard and sensitive data are loaded into the manufactured IC. Standard data are generic and mostly available open source, but the sensitive data are anything whose disclosure would compromise IP or security."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nhere those common security controls are applied. Security controls not designated as common controls are considered system-specific controls and are the responsibility of the information system owner.\nSystem security plans should clearly identify which security controls have been designated as common security controls and which controls have been designated as system-specific controls."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "...............................................................79 | |\n| A.2.6.\nFAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7. FAMILY: CONFIGURATION MANAGEMENT................................................................................87 | |\n| A.2.8. FAMILY: CONTINGENCY PLANNING ...........................................................................................98 | |\n| A.2.9. FAMILY: IDENTIFICATION AND AUTHENTICATION...................................................................102 | |\n| A.2.10. FAMILY: INCIDENT RESPONSE................................................................................................105 | |\n| A.2.11. FAMILY: MAINTENANCE.........................................................................................................110 | |\n| A.2.12. FAMILY: MEDIA PROTECTION ................................................................................................115 | |\n| A.2.13."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nas a master template for a generalized contingency plan for all agency information systems with individual information system owners tailoring the plan, where appropriate, for system-specific issues.\n| CLASS | FAMILY | IDENTIFIER |\n|-------------|--------------------------------------------------------|--------------|\n| Management | Risk Assessment | RA |\n| Management | Planning | PL |\n| Management | System and Services Acquisition | SA |\n| Management | Certification, Accreditation, and Security Assessments | CA |\n| Operational | Personnel Security | PS |\n| Operational | Physical and Environmental Protection | PE |\n| Operational | Contingency Planning | CP |\n| Operational | Configuration Management | CM |\n| Operational | Maintenance | MA |\n| Operational | System and Information Integrity | SI |\n| Operational | Media Protection | MP |\n| Operational | Incident Response | IR |\n| Operational | Awareness and Training | AT |\n| Technical | Identification and Authentication | IA |\n| Technical | Access Control | AC |\n| Technical | Audit and Accountability | AU |\n| Technical | System and Communications Protection | SC |"}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.8.\n\n4.3.8. On-Site Attended Requirements — Kiosk-Based . . . . . . . . .\n\na piece of identity evidence through the return of a confirmation code, consistent\nwith the requirements specified in Sec. 3.8."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.3.2. 3.3.2. 3.3.2."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nderal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?\n| The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. |\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.8 (NIST 3.3.8)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.3.8 Program Controls\n\nAccess controls must also be in place to protect\nprograms, JCL and related documentation from unauthorized\nA program may be proprietary for its intrinsic\naccess."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.3.8", "cmmc_practice_id": "AU.L2-3.3.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.3.1. Privacy Risk Assessment . . . . . . . . . . . . . . . . . . . . . .\n\n3.11. Requirements for the Use of Biometrics . . . . . . . . . . . . . . . . . .\n\n6. Threats and Security Considerations . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n| Collaborator | Component |\n|----------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| | Provides secure remote access with authentication and authorization support. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n| | Offers secure data storage on-prem. |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n\n| Collaborator | Component |\n|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Real-time data management software that enables detection of behavior anomalies and modifications to hardware, firmware, and software capabilities. |\n| | Access control platform that secures connections and provides control mechanisms to enterprise systems for authorized users and devices; monitors activity down to the keystroke |\n| | Provides network and asset monitoring to detect behavior anomalies and modifications to hardware, firmware, and software capabilities."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.2.3. 3.2.3."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 4)"}, {"role": "assistant", "content": "ies, and methods for key confirmation are included to provide assurance that both parties share the same keying material. In addition, the security properties associated with each scheme are provided.\n## Keywords\n\nassurances; integer factorization cryptography; key agreement; key confirmation; key derivation; key establishment; key management; key recovery; key transport. ## Acknowledgements\n\nNIST thanks the many contributions by the public and private sectors whose thoughtful and constructive comments improved the quality and usefulness of this publication. The authors also acknowledge the contributions by Dustin Moody, Andrew Regenscheid and Miles Smid made to previous versions of this Recommendation . ## Conformance Testing\n\nConformance testing for implementations of this Recommendation will be conducted within the framework of the Cryptographic Algorithm Validation Program (CAVP) and the Cryptographic Module Validation Program (CMVP). The requirements of this Recommendation are indicated by the word ' shall .' Some of these requirements may be out-of-scope for CAVP or CMVP validation testing, and thus are the responsibility of entities using, implementing, installing or configuring applications that incorporate this Recommendation. ## Table of Contents\n\n| 1. Introduction............................................................................................................................. | 1. Introduction............................................................................................................................. | 1. Introduction............................................................................................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof-of-concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1. | Introduction ...................................................................................................................... | 2 |\n| 2. | Fundamental Theories ....................................................................................................."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nbust and comprehensive information security and privacy risk\nmanagement programs can facilitate compliance with applicable laws, regulations, executive\norders, and governmentwide policies.\nRisk management frameworks and risk management\nprocesses are essential in developing, implementing, and maintaining the protection measures\nnecessary to address stakeholder needs and the current threats to organizational operations\nand assets, individuals, other organizations, and the Nation. Employing effective risk-based\nprocesses, procedures, methods, and technologies ensures that information systems and\norganizations have the necessary trustworthiness and resiliency to support essential mission and\nbusiness functions, the U.S. critical infrastructure, and continuity of government."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.3.3. 3.3.3."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\n## Ordered t-way Combinations for Testing State-based Systems\n\nFault detection often depends on the specific order of inputs that establish states which eventually lead to a failure. However, beyond basic structural coverage metrics, it is often difficult to determine if code has been exercised sufficiently to ensure confidence in its functions. Measures are needed to ensure that relevant combinations of input values have been tested with adequate diversity of ordering to ensure correct operation. Combinatorial testing and combinatorial coverage measures have been applied to many types of applications but have some deficiencies for verifying and testing state-based systems where the response depends on both input values and the current system state. In such systems, internal states change as input values are processed. Examples include network protocols, which may be in listening, partial connection, full connection, disconnected, and many other states depending on the values of packet fields and the order of packets received. Similarly, merchant account balances in credit card systems change continuously as transactions are processed. This publication introduces a notion of ordered t-way combinations, proves a result regarding the construction of adequate blocks of test inputs, and discusses the application of the results to verify and test state-based systems.\n\ncombinatorial coverage; combinatorial methods; combinatorial testing; software testing; structural coverage; test coverage."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 10)"}, {"role": "assistant", "content": "mental Standard for Physical Security and\nGeneral Controls\nCommentary\n2o4.1\nOther Audit Requirements\n\n2.3\n\n2.4\n\n2e5\n\nCommentary\n\n. o\n\n. . o\n\n. »\n\n„\n\n. =\n\n. „\n\no\n\n3. RECOMMENDED COURSE OF ACTION\n\no\n\n4.\nPART IV:\n\nREFERENCES\nQUALIFICATIONS AND TRAINING ........... o\n\nEDITORS' NOTE\n\n. . Qualifications and Training\n\n•\n\n\"\n\n0\n\n0\n\n0\n\n1. 2. 3. 4. 5„\n6. 7. 8. INTRODUCTION\nCONSIDERATIONS ASSOCIATED WITH DEVELOPING A COMMON\nBODY OF KNOWLEDGE ......... THE EIGHT PARTS OF THE COMMON BODY OF KNOWLEDGE ..... COMPUTER SYSTEM, OPERATIONS, AND SOFTWARE\nDATA PROCESSING TECHNIQUES\nMANAGEMENT OF THE DATA PROCESSING FUNCTION „\nSECURITY OF THE DATA PROCESSING FUNCTION\nRISK ANALYSIS AND THREAT ASSESSMENT .......... MANAGEMENT CONCEPTS AND PRACTICES\nAUDITING CONCEPTS AND PRACTICES\nBASIC QUALIFICATIONS NEEDED TO EVALUATE COMUTER\nSECURITY\n\n......... o\n\n. . . „\n\n. . o\n\no\n\no\n\n. . o\n\n. o\n\no\n\no\n\n. . . . o\n\n. . . 0\n0\n\nOUTLINE OF THE COMMON BODY OF KNOWLEDGE . BIBLIOGRAPHY\n\n. . . o\n\n. o\n\no\n\no\n\nPART V:\n\nSECURITY ADMINISTRATION\n\n. . . o\n\nEDITORS' NOTE\n\n....... o\n\n. . le\n\nINTRODUCTION\nGeneral\nlal\nPrivacy Legislation . 1.2\n1.201\n1.202\nle2.3\nOrganization of this Report . 1.3\n\no\n\no\n\nThe Privacy Act of 1974\nLaws in Other Countries\nInternational Privacy Law Compatibility\n\no\n\no\n\n. o\n\no\n\n. . . o\n\no\n\n. . o\n\n. . . . . . . . . . vi ii\n\n3-5\n3-5\n3-5\n3-6\n\n3-7\n3-7\n\n3-8\n3-8\n3-10\n\n3-10\n\n3-11\n\n4-1\n4-2\n\n4-3\n\n4-3\n\n4-3\n4-6\n\n4-6\n4-7\n4-7\n4-7\n4-8\n4-8\n4-9\n\n4-9\n\n4-11\n4-13\n\n5-1\n5-2\n\n5-3\n5-3\n5-4\n5-4\n5-4\n5-5\n5-5\n\n\f2. SECURITY ADMINISTRATION PROGRAM\n2.1\n2.2\n2.3\n2.4\n\nIntroduction\nPlanning by Management\nManagement Control ..... ADP Security\n2.4.1\n2.4.2\n2.4.3\n2.4.4\n2.4.5\n\nAdministrative Security\nPhysical Security Administration\nTechnical Security\nTraining\nA Suggested Security System for an\nOn-Line System— An Example\n\n3. AUDITING THE SECURITY ADMINISTRATION FUNCTION ....."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\ns prevention. So, within any year, I reach out to those stakeholders to ask, 'What's important for the user to understand about cybersecurity awareness? What do you want to talk to the customer about?\nWhat kind of behaviors are you seeing that you want us to help encourage them to do or not to do?.' (D01)\n- 'Build relationships with offices within your organization- Incident Response, Help Desk,…FISMA Compliance.' (Q24)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nty on a small number of low-importance assets. - Schedule patch deployment. Many organizations schedule patch deployments as part of their enterprise change management activities. - Acquire the patch.\nPatches may be downloaded from the internet, built internally by developers or system administrators, or provided through removable media. - Validate the patch. A patch's authenticity and integrity should be confirmed, preferably by automated means, before the patch is tested or installed. The patch could have been acquired from a rogue source or tampered with in transit or after acquisition. - Test the patch. A patch may be tested before deployment. This is intended to reduce operational risk by identifying problems with a patch before placing it into production. Testing may be performed manually or through automated methods."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nNoSQL systems can handle fast-paced agile development, the storage of large volumes of structured and semi-structured data, the requirements for scale-out architecture, and modern application paradigms (e.g., microservices and real-time streaming) [MO]. However, they also face many challenges with regard to access control, such as a lack of proper authentication, encryption, dynamic model support, and fine-grained authorization (as described in Sec. 3.3). Therefore, careful considerations need to be made when implementing access control on NoSQL databases to address these issues effectively."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n..................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5.\nTraceability of CE Operations.....................................................................................................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1. Information Decisions in the System Life Cycle..........................................................................20 |\n| 4.3.2. Determination of Security Categorization..................................................................................21 |\n| 4.3.3. Reuse of Media...........................................................................................................................22 |\n| 4.3.4. Control of Media ........................................................................................................................22 |\n| 4.3.5. Data Protection Level .................................................................................................................23 |\n| 4.3.6. Sanitization and Disposal Decision.............................................................................................23 |"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - The application is made up of a set of loosely coupled components called microservices. Each of the microservices can be hosted on different physical or virtual machines (VMs) and even be geographically distributed (e.g., within several facilities that belong to the enterprise, such as the headquarters, branch offices, and in various cloud service provider environments). - Any transaction involving the application may also involve one or more inter-service (microservice) calls across the network. - A widespread feature (though not necessarily a requirement for cloud-native applications) is the presence of a software platform called the service mesh that provides an integrated set of all application services (e.g., services discovery, networking connections, communication resilience, and security services like authentication and authorization). - Zero trust is the term for an evolving set of cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users and resources. It is a set of security primitives rather than a particular set of technologies."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nEnterprise administrators and system operators need to be involved in the planning and deployment for a ZTA to be successful. ZTA planning requires input and analysis from system and workflow owners as well as professional security architects. Zero trust cannot be simply added onto an existing workflow but needs to be integrated into all aspects of the enterprise. This document introduces NIST Risk Management Framework (RMF) [2] concepts for administrators and operators who are in the process of migrating to a ZTA. The RMF lays out an approach that includes set of steps and tasks that is integrated into enterprise risk analysis, planning, development, and operations. Administrators who normally do not perform the steps and tasks detailed in the RMF may find that they will need to become familiar with them as they migrate to a ZTA.\n\nZero trust lends itself to the use of more dynamic development and operations (DevOps) [17] and DevOps and security (DevSecOps) style operations. The cycles of security updates and reviews could be described as involving a subset of the RMF process. For example, a DevOps cycle for the cybersecurity posture could be expressed as figure 3 below:"}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Access Control?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| Non-Technical Supporting Capability | Common Actions | Rationale | IoT Reference Examples | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Education and Awareness : The ability for the manufacturer and/or supporting entity to create awareness of and educate customers and others in the IoT device ecosystem about cybersecurity- related information, considerations, features, etc."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.1.1 Identify Outage Impacts and Estimated Downtime\n\nThis section identifies and characterizes the types of impact categories that a system disruption is likely to create in addition to those identified by the FIPS 199 impact level, as well as the estimated downtime that the organization can tolerate for a given process."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 2)"}, {"role": "assistant", "content": "systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 3)"}, {"role": "assistant", "content": "d States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-37, Revision 2 Natl. Inst. Stand. Technol. Spec. Publ. 800-37, Rev.\n2, 183 pages (December 2018)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-37r2\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the designated public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.3.4, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\ncontrol (e.g., contractor computers, employees' home computers, business partners' computers, mobile devices). Organizations should ensure that their policies address prevention of malware incidents.\nThese policy statements should be used as the basis for additional malware prevention efforts, such as user and IT staff awareness, vulnerability mitigation, threat mitigation, and defensive architecture (described in Sections 3.2 through 3.5, respectively). If an organization does not state malware prevention considerations clearly in its policies, it is unlikely to perform malware prevention activities consistently and effectively throughout the organization. Malware prevention-related policy should be as general as possible to provide flexibility in policy implementation and to reduce the need for frequent policy updates, but also specific enough to make the intent and scope of the policy clear. Although some organizations have separate malware policies, many malware prevention considerations belong in other policies, such as acceptable use policies, so a separate malware policy might duplicate some of the content of other policies. 5 Malware prevention-related policy should include provisions related to remote workers-both those using hosts controlled by the organization and those using hosts outside of the organization's control (e.g., contractor computers, employees' home computers, business partners' computers, mobile devices)."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nncy official with statutory or operational authority for specified information and responsibility for establishing the controls for its generation, collection, processing, dissemination, and disposal.\nThe information owner has the following responsibilities related to system security plans:\n\n| CLASS | FAMILY | IDENTIFIER |\n|-------------|--------------------------------------------------------|--------------|\n| Management | Risk Assessment | RA |\n| Management | Planning | PL |\n| Management | System and Services Acquisition | SA |\n| Management | Certification, Accreditation, and Security Assessments | CA |\n| Operational | Personnel Security | PS |\n| Operational | Physical and Environmental Protection | PE |\n| Operational | Contingency Planning | CP |\n| Operational | Configuration Management | CM |\n| Operational | Maintenance | MA |\n| Operational | System and Information Integrity | SI |\n| Operational | Media Protection | MP |\n| Operational | Incident Response | IR |\n| Operational | Awareness and Training | AT |\n| Technical | Identification and Authentication | IA |\n| Technical | Access Control | AC |\n| Technical | Audit and Accountability | AU |\n| Technical | System and Communications Protection | SC |\n\n| Configuration Control [CNSS Inst."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.5 (NIST 3.1.5)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.5. 3.1.5."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.5", "cmmc_practice_id": "AC.L2-3.1.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n3.4.1. 3.4.1. 3.4.1."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\ncyber threat information sharing; Cybersecurity Framework; cybersecurity incident; cybersecurity risk management; incident handling; incident management; incident response.\n\n…an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies. [FISMA2014]\n\n- Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state"}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n- NIST research and publications on trustworthy and responsible AI, including the Artificial Intelligence Risk Management Framework (AI RMF 1.0) [2], Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations [3], Towards a Standard for Identifying and Managing Bias in Artificial Intelligence [4], and the Dioptra experimentation testbed for security evaluations of machine learning algorithms [5]. - NIST's Secure Software Development Framework (SSDF) Version 1.1 [6], which is a set of fundamental, sound, and secure software development practices. It provides a common language to help facilitate communications among stakeholders, including software producers and software acquirers. The SSDF has also been used in support of EO 14028, Improving the Nation's Cybersecurity [7], to enhance software supply chain security. - NIST general cybersecurity resources, including The NIST Cybersecurity Framework (CSF) 2.0 [8], Security and Privacy Controls for Information Systems and Organizations [9], and Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations [10]. - AI model developers, AI researchers, AI system developers, and secure software practitioners from industry and government with expertise in the unique security challenges of AI models and the practices for addressing those challenges. This expertise was primarily captured through NIST's January 2024 workshop, where speakers and attendees shared suggestions for adapting secure software development practices and tasks to accommodate the unique aspects of AI model development and the software leveraging them. All practices and tasks are unchanged from SSDF version 1.1 unless they are explicitly tagged as 'Modified from SSDF 1.1' or 'Not part of SSDF 1.1.' An example is the PW.3 practice, ' Confirm the Integrity of Training, Testing, Fine-Tuning, and Aligning Data Before Use' and all of its tasks."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 5)"}, {"role": "assistant", "content": "orkshop and received over 150 position papers, many of which suggested secure software development practices, tasks, examples of implementations, and references for consideration for this SSDF update.\nThe authors appreciate all of those suggestions, as well as the input from those who spoke at or attended the workshop and shared their thoughts during or after the workshop. Additionally, the authors appreciate the public comments submitted by dozens of organizations and individuals and wish to acknowledge the particularly helpful feedback from Amazon Web Services, Apiiro, Blackberry, BSA | The Software Alliance, the Enterprise Cloud Coalition, the General Services Administration (GSA), Google, IBM, Medical Imaging & Technology Alliance (MITA), Microsoft, Oracle, the Software Assurance Forum for Excellence in Code (SAFECode), Synopsis, the U.S. Navy, Xoomworks, and Robert Grupe. Representatives of Siemens Energy and Synopsis contributed mappings to new references. The authors thank all of their NIST colleagues for their support throughout the SSDF update, especially Curt Barker, Paul Black, Jon Boyens, Jim Foti, Barbara Guttman, Mat Heyman, Nicole Keller, Matt Scholl, Adam Sedgewick, Kevin Stine, and Isabel Van Wyk. The authors also wish to thank all of the individuals and organizations who provided comments on drafts of the original version of the SSDF, including the Administrative Offices of the U.S. Courts, The Aerospace Corporation, BSA | The Software Alliance, Capitis Solutions, the Consortium for Information & Software Quality (CISQ), HackerOne, Honeycomb Secure Systems, iNovex, Ishpi Information Technologies, the Information Security and Privacy Advisory Board (ISPAB), Juniper Networks, Microsoft, MITA, Naval Sea Systems Command (NAVSEA), NIST, Northrop Grumman, the Office of the Undersecretary of Defense for Research and Engineering, Red Hat, SAFECode, and the Software Engineering Institute (SEI)."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| 2.1 | BACKGROUND | BACKGROUND | BACKGROUND | 16 | |-------|------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|------| | | 2.1.1 | PCIE - EDP Systems Review and Security Work Group | PCIE - EDP Systems Review and Security Work Group | 16 | | | 2.1.2 | System Development Life Cycle | System Development Life Cycle | 16 | | 2.2 | OPERATING ENVIRONMENT | OPERATING ENVIRONMENT | OPERATING ENVIRONMENT | 17 | | | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 2.2.1 IRM Planning and Implementation of Policy Guidelines | 17 | | | 2.2.1.1 IRM Planning | 2.2.1.1 IRM Planning | 2.2.1.1 IRM Planning | 17 | | | 2.2.1.2 Using Policy/Procedures/Standards | 2.2.1.2 Using Policy/Procedures/Standards | 2.2.1.2 Using Policy/Procedures/Standards | 18 | | | 2.2.1.2.1 | 2.2.1.2.1 | References Used by the Life Cycle Matrix | 19 | | | 2.2.1.2.2 | 2.2.1.2.2 | Major GSA References | 21 | | | 2.2.2 AIS Development Methodologies | 2.2.2 AIS Development Methodologies | 2.2.2 AIS Development Methodologies | 21 | | | 2.2.3 Project Administration and Control | 2.2.3 Project Administration and Control | 2.2.3 Project Administration and Control | 23 |"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . .\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.1. Truncation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.2.2. Nonce Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| 4.3. AEAD Requirements.............................................................. | 19 |\n| 4.4. Security Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.1. Single-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.2. Multi-Key Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 20 |\n| 4.4.3. Nonce-Misuse Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 21 |\n| 5. Hash and eXtendable-Output Functions (XOFs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.1. Specification of Ascon-Hash256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.2. Specification of Ascon-XOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 25 |\n| 5.3. Specification of Ascon-CXOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 28 |\n| 5.4. Streaming API for XOF............................................................ | 30 |\n| 5.5. Security Strengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 2)"}, {"role": "assistant", "content": "approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130.\nNothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-218\n\nNatl. Inst. Stand. Technol. Spec. Publ. 800-218, 36 pages (February 2022) CODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-218\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n- Identity Management, Authentication, and Access Control: Identities and credentials for authorized users, services, and hardware are managed by the organization [PR.AA-01]\n- Awareness and Training: Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind [PR.AT-02]"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 3)"}, {"role": "assistant", "content": "ble at https://csrc.nist.gov/pubs/ir/8558/final, including related content, potential updates, and document history. ## All comments are subject to release under the Freedom of Information Act (FOIA).\n## Abstract\n\nThis report documents the first SOUPS Design-A-Thon, which was held on August 11 th , 2024, and focused on Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness. In total, eight individuals participated in the event, forming three teams. The teams each selected a mock product based on a selection of five Product Data Cards developed by the NIST team. Participants used the information on the Product Data Cards to develop a strategy for cybersecurity education and awareness for the product. Teams were successful in planning strategies that utilize novel techniques and sound best practices. From the participant teams' designs, the NIST team identified highlights and takeaways that are further elaborated in this report. ## Keywords\n\ncybersecurity; Internet of Things; Design-A-Thon; usability; human factors; education and awareness. ## Audience\n\nThis report is primarily intended for students and researchers in the fields of IoT cybersecurity and usable security. The topics and discussion of this report may also be useful and interesting to practitioners in these fields, but since the report contains initial findings from a small group exercise, it is not intended as a specific recommendation or guideline for practice. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM) provide? (Part 6)"}, {"role": "assistant", "content": "the supplier relationship lifecycle. - ☐ Specify in contracts the rights and responsibilities of the organization, its suppliers, and their supply chains with respect to potential cybersecurity risks.\nContractually require suppliers to do the following:\n\n☐ disclose cybersecurity features, functions, and vulnerabilities of their products and services for the life of the product or the term of service\n\n☐ provide and maintain a current component inventory (e.g., software or hardware bill of materials) for critical products\n\n☐ vet their employees and guard against insider threats\n\n☐ provide evidence of performing acceptable security practices through, for example, self-attestation, conformance to known standards, certifications, or inspections\n\n## NIST CSF 2.0: CYBERSECURITY SUPPLY CHAIN RISK MANAGEMENT (C-SCRM)\n\nA QUICK-START GUIDE\n\n## HOW TO USE THE CSF TO DEFINE AND COMMUNICATE SUPPLIER REQUIREMENTS\n\n## Developing Supplier Requirements\n\nAn organization should specify requirements for technology suppliers. Robustness of these requirements should correspond to supplier criticality. Organizations can use two different methods for specifying supplier requirements:\n\n1. Use CSF Categories and Subcategories. Not all Categories and Subcategories will apply to all suppliers. You can pick and choose requirements that fit your mission or business supplier criticality level. Select requirements for suppliers based on their criticality and your mission or business. To do that, review the list of CSF Categories and Subcategories, and determine which ones will be applicable to suppliers within each of the criticality levels, based on the risk appetite for each supplier criticality level. When considering individual supplier agreements, determine if additional supplier requirements are needed based on existing criticality criteria, such as your mission or business, data type being processed, or digital product or service being provided. 2."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nScott Rose Wireless Networks Division Communications Technology Laboratory\n\nFor additional information on NIST's Cybersecurity programs, projects, and publications, visit the Computer Security Resource Center. Information on other efforts at NIST, the Information Technology Laboratory (ITL) and Communications Technology Laboratory (CTL) is also available. Zero trust related information is also found on the zero trust topic page.\n\nNational Institute of Standards and Technology Attn: Wireless Networks Division, Communications Technology Laboratory 100 Bureau Drive (Mail Stop 8920) Gaithersburg, MD 20899-8920"}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n.............................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1.\nBaseline Security ........................................................................................................................11 |\n| 3.2.2. Controls for Interacting With SCM Systems...............................................................................12 |\n| 4. CI/CD Pipelines -Background, Security Goals, and Entities to be Trusted .....................................13 |\n| 5. Integrating SSC Security Into CI/CD Pipelines.................................................................................15 |\n| 5.1.1. Secure Build................................................................................................................................16 |\n| 5.1.2. Secure Pull-Push Operations on Repositories............................................................................17 |\n| 5.1.3. Integrity of Evidence Generation During Software Updates......................................................18 |\n| 5.1.4. Secure Code Commits ................................................................................................................19 |"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n- Environmental and physical threats: Physical or cyber attacks against facilities (e.g., power, cooling, water), unauthorized physical access, and natural disasters (e.g., fire, flood, earthquake, hurricane, etc.) are all potential threats to an HPC system. - Vulnerabilities introduced by prioritizing performance in HPC design and operation: HPC is designed to process large volumes of data and perform complex computations at very high speeds. Achieving the highest performance possible is a priority in HPC design and operation. Such prioritization, however, has its security implications. For instance, designers often make conscious decisions to build a less redundant system to achieve high performance, making the system less robust and potentially more vulnerable to attacks, such as DoS attacks. As another example, using a backup system to improve system robustness and high availability is a proven technology. However, building a spare or backup HPC system is often too costly. HPC systems can often lack storage backup due to the vast size of the data stored. Similarly, most HPC missions do not have a service-level agreement to justify the need for a full backup system at a backup location. All resources are poured into building the single best HPC system possible. - Supply chain threats: The HPC supply chain faces a variety of threats, from the theft of proprietary information to attacks on critical hardware components and software manipulation to gain unauthorized access. Some HPC software (e.g., OS, applications), firmware, and hardware components have limited manufacturers, suppliers, and integrators, which makes diversification difficult. Limited suppliers also lead to shortages in the qualified workforce who can provide required technical support. - Insider threats: Insider threats come from people within the organization who have internal information and may have the privileges needed to access the HPC system."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nation of privacy capabilities in IoT products. Gilbert also discussed specific privacy risks related to IoT, such as interactions with the physical world leading to reputational harm or safety issues.\nData processing might exceed the product's intended scope, and access, management, and monitoring features could result in loss of trust and economic loss. Additionally, privacy capability availability, efficiency, and effectiveness are crucial to prevent issues like discrimination and to maintain trust. IoT products need the capabilities to support configurations such as remote activation, prevention, and data minimization."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "e of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management.\nFigure 1: Risk Management 3-Tiered Approach\n\n\n\nThe 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. The security controls in SP 800-53 Rev. 4 support Step Two of the RMF, and a detailed catalog of these controls is provided in Appendix F. For ease of use in the security control selection and specification process, controls are organized into eighteen families, each containing security controls related to the general security topic of the family. Security controls involve aspects of policy, oversight, supervision, manual processes, individual actions, or automated mechanisms implemented by information systems/devices. The security control structure consists of the\n\nfollowing components: (i) a control section; (ii) a supplemental guidance section; (iii) a control enhancements section; (iv) a references section; and (v) a priority and baseline allocation section."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.4 (NIST 3.7.4)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.7.4 Privileged Program Controls 3. 3.7.4 Privileged Program Controls 3. 3.7.4 Privileged Program Controls ; A means of permitting users to have limited access to a data base to vSiich they do not have authorization for direct access is to produce a set of privileged (or trusted) sanitization programs vAiich are permitted to access the restricted data base components for the user."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.7.4", "cmmc_practice_id": "MA.L2-3.7.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/88/r2/final, including related content, potential updates, and document history.\n\nDuring the requirements phase, other types of ISM that will be used to create, capture, or transfer information used by the system should be identified. This analysis balances business needs and confidentiality risks in compliance with FIPS 200 [3]. While media sanitization and information disposition activities primarily occur during the disposal phase of the system life cycle, many types of ISM containing data will be transferred outside of the positive control of the organization throughout the life of an information system (e.g., for maintenance, system upgrades, or during a configuration update).\n\n- Alignment of the organization's data classification scheme (e.g., low, medium, and high security categorizations) with minimum acceptable sanitization methods (i.e., clear, purge, and destroy)\n- Requirements for the disposal and/or reuse of storage assets\n- Expected outcomes from storage sanitization activities (e.g., identification of specific, acceptable sanitization techniques [13])\n- Documentation or evidence associated with sanitization activities (see Sec. 4.6)\n- The identification of roles and responsibilities (see Sec. 4.7) and personnel competencies, skills, and training\n- The use of sanitization tools, including equipment calibration, testing, and maintenance\n- Type of assurances (e.g., guarantees, assessment results, formal certifications) that the ISM vendor should provide for the sanitization capabilities"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 9)"}, {"role": "assistant", "content": "| ........................................................................................................................\n5 |\n| 4 | Architecture and Builds.......................................................................6 | Architecture and Builds.......................................................................6 |\n| | 4.1 Project | Collaborators ................................................................................................... 6 |\n| | 4.1.1 | AppViewX ...................................................................................................................... 7 |\n| | 4.1.2 | DigiCert ........................................................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.5.1 Implementation of the Scheme | 3. 3.5.1 Implementation of the Scheme | 59 |\n| | 3. 3.5.1 | Introduction | 86 |\n| | 4."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- It enables the enterprise to have tight version control (tracking changes) so that unauthorized networking devices and changes in associated configurations do not open up security vulnerabilities. - It enables the enterprise to have a uniform infrastructure across all environments development, testing, staging, and production. - Monitoring the drift (the unintended changes) between the defined infrastructure (as found in IaC) and the operational infrastructure (as measured by monitoring tools\n\n- The DevSecOps paradigm consisting of CI/CD pipelines invokes the network provisioning tool (IaC code generator) to automate the initial deployment and subsequent reconfiguration of the networking infrastructure. Since the pipelines have a built-in audit process, the changes in network configuration are automatically captured in the audit, which enables the enterprise to demonstrate corporate security policy compliance and regulatory policy compliance for their networks where applicable. - Testing the code (IaC code) generated by IaC tools (and invoked by the CI/CD pipeline code that deploys the infrastructure using IaC in the DevSecOps process) ensures that security policies are consistently and uniformly applied across the entire enterprise networking infrastructure (i.e., multiple cloud services). - The advantage of having plug-ins for defining network provisioning for different public cloud provider environments is that they can be used to customize the observability tools used for network monitoring for each of those cloud services that the enterprise has subscribed to [17]. 2. Information about the device from which access is being requested - Establishing trust in the device through a combination of health and risk profiles of the device. For example, the risk profile of the device can be obtained through an out-of-the-box posture check (risk of the device [28]) with or without integrating with an endpoint protection tool for the device."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 8)"}, {"role": "assistant", "content": "IRM Planning | 2.2.1.1 IRM Planning | 2.2.1.1 IRM Planning | 17 | | | 2.2.1.2 Using Policy/Procedures/Standards | 2.2.1.2 Using Policy/Procedures/Standards | 2.2.1.2 Using Policy/Procedures/Standards | 18 | | | 2.2.1.2.1 | 2.2.1.2.1 | References Used by the Life Cycle Matrix | 19 | | | 2.2.1.2.2 | 2.2.1.2.2 | Major GSA References | 21 | | | 2.2.2 AIS Development Methodologies | 2.2.2 AIS Development Methodologies | 2.2.2 AIS Development Methodologies | 21 | | | 2.2.3 Project Administration and Control | 2.2.3 Project Administration and Control | 2.2.3 Project Administration and Control | 23 | | | 2.2.4 AIS Life Cycle Matrix | 2.2.4 AIS Life Cycle Matrix | 2.2.4 AIS Life Cycle Matrix | 24 | | 2.3 | LIFE CYCLE PHASES | LIFE CYCLE PHASES | LIFE CYCLE PHASES | 26 | | | 2.3.1 Initiation - Phase I | 2.3.1 Initiation - Phase I | 2.3.1 Initiation - Phase I | 27 | | | 2.3.2 Definition - Phase II | 2.3.2 Definition - Phase II | 2.3.2 Definition - Phase II | 27 | | | 2.3.3 System Design - Phase III | 2.3.3 System Design - Phase III | 2.3.3 System Design"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| ...................................................................................................\n3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n- FIPS 199 [2] and SP 800-60r2, Guide for Mapping Types of Information and Systems to Security Categories [7] , provide guidance for establishing the security categorization for a system's confidentiality. This categorization will impact the level of assurance that an organization should require when making sanitization decisions. - FIPS 200, Minimum Security Requirements for Federal Information and Information Systems [3] , establishes baseline security requirements for organizations to have a media sanitization program. - FIPS 140-3, Security Requirements for Cryptographic Modules [1] , establishes a standard for cryptographic modules used by the U.S. Government. - SP 800-53r5 [5] provides minimum recommended security controls, including sanitization, for federal systems based on their overall system security categorization. - SP 800-53Ar5, Guide for Assessing the Security Controls in Federal Information Systems and Organizations: Building Effective Security Assessment Plans [6], provides guidelines for assessing security controls, including sanitization, for federal systems based on their overall system security categorization. - SP 800-111, Guide to Storage Encryption Technologies for End User Devices [10], provides guidelines for selecting and using storage encryption technologies. 8 Conformance testing for FIPS 140-3 is conducted within the framework of the Cryptographic Module Validation Program (CMVP) and the Cryptographic Algorithm Validation Program (CAVP). - Alignment of the organization's data classification scheme (e.g., low, medium, and high security categorizations) with minimum acceptable sanitization methods (i.e., clear, purge, and destroy)\n- Requirements for the disposal and/or reuse of storage assets\n- Expected outcomes from storage sanitization activities (e.g., identification of specific, acceptable sanitization techniques [13])\n- Documentation or evidence associated with sanitization activities (see Sec."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\nNIST is selecting public-key cryptographic algorithms through a public, competition-like process to specify additional digital signature, public-key encryption, and key-establishment algorithms to supplement FIPS 186-5, SP 800-56Ar3, and SP 800-56Br2. These algorithms are intended to protect sensitive information well into the foreseeable future, including after the advent of quantum computers. In the fourth round of the Post-Quantum Cryptography Standardization Process, NIST selected four candidate algorithms for key establishment to be studied: BIKE, Classic McEliece, HQC, and SIKE. This report describes the evaluation and selection process of these fourth-round candidates based on public feedback and internal review. The report summarizes each of the candidate algorithms and identifies those selected for standardization. The only key-establishment algorithm that will be standardized is HQC, and NIST will develop a standard based on HQC to augment its key-establishment portfolio. | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . | . . . | 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|\n| 1.1. | Purpose and Organization of This Document . . . . | 3 |\n| 2. Evaluation Criteria and Selection Process . . | . . . . . . . . | 4 |\n| 2.1. | Acceptance of the Fourth-Round Candidates . . . . | 4 |\n| 2.2. | Evaluation Criteria . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.1. Security . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| | Introduction ....................................................................................................1 | | |-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | 1.1 | | Purpose.......................................................................................................................1 | | | 1.2 | | Scope..........................................................................................................................2 | | | 1.3 | | Audience.....................................................................................................................3 | | | 1.4 | Document | Structure....................................................................................................4 | | | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 8)"}, {"role": "assistant", "content": "|\n| 3.2 Symbols and Abbreviations................................................................................................\n9 | 3.2 Symbols and Abbreviations................................................................................................ 9 | 3.2 Symbols and Abbreviations................................................................................................ 9 |\n| Key-Establishment Schemes Overview............................................................................... 16 | Key-Establishment Schemes Overview............................................................................... 16 | Key-Establishment Schemes Overview..............................................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology.\nITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems. The Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations.\n\n3.2.1. Physical Authenticators\n\nThis guideline applies to the digital authentication of subjects to systems over a network.\nIt also requires that verifiers and RPs participating in authentication protocols be\nauthenticated to claimants to assure the identity of the services with which they are\nauthenticating. It does not address the authentication of a person for physical access\n(e.g., to a building)."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Assessing Security Requirements for Controlled Unclassified Information support CMMC certification?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nother than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n| | 6.3.2 | (Cofactor) Static Unified Model, C(0e, 2s, ECC CDH) Scheme..................... 105 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | 6.3.3 | Incorporating Key Confirmation into a C(0e, 2s) Scheme .............................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## Analyzing Collusion Threats in the Semiconductor Supply Chain\n\nRekhi S, Amberiadis K, Akib AA, Srivastava A (2025) Analyzing Collusion Threats in the Semiconductor Supply Chain. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 46. https://doi.org/10.6028/NIST.CSWP.46\n\nThis work proposes a framework for analyzing threats related to the semiconductor supply chain. The framework introduces a metric that quantifies the severity of different threats subjected to a collusion of adversaries from different stages of the supply chain. Two different case studies are provided to describe the real-life application of the framework. The metrics and analysis aim to guide security efforts and optimize the trade-offs of hardware security and costs."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 10)"}, {"role": "assistant", "content": "://www.nist.gov. ## NIST CYBERSECURITY PRACTICE GUIDES\n\nNIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors.\nThey are practical, user-friendly guides that facilitate the adoption of standards-based approaches to cybersecurity. They show members of the information security community how to implement example solutions that help them align with relevant standards and best practices, and provide users with the materials lists, configuration files, and other information they need to implement a similar approach. The documents in this series describe example implementations of cybersecurity practices that businesses and other organizations may voluntarily adopt. These documents do not describe regulations or mandatory practices, nor do they carry statutory authority. ## ABSTRACT\n\nOrganizations are increasingly at risk of cyber supply chain compromise, whether intentional or unintentional. Cyber supply chain risks include counterfeiting, unauthorized production, tampering, theft, and insertion of unexpected software and hardware. Managing these risks requires ensuring the integrity of the cyber supply chain and its products and services. This project demonstrates how organizations can verify that the internal components of the computing devices they acquire, whether laptops or servers, are genuine and have not been tampered with. This solution relies on device vendors storing information within each device, and organizations using a combination of commercial off-theshelf and open-source tools that work together to validate the stored information. This NIST Cybersecurity Practice Guide describes the work performed to build and test the full solution. ## KEYWORDS\n\ncomputing devices; cyber supply chain; cyber supply chain risk management (C-SCRM); hardware root of trust; integrity; provenance; supply chain; tampering ."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.4.3 | Risk... 3.4.3 Risk\n\nSP 800-161 Revision 1 [3] provides an analysis framework for organizations to assess supply chain risk by creating a threat scenario -a summary of potential consequences of the successful exploitation of a specific vulnerability or vulnerabilities by a threat agent. 3.4.3."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "blication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n## Audience\n\nThis publication serves a diverse group of individuals and organizations in the public and private sectors, including:\n\n- Federal agencies responsible for managing and protecting CUI\n- Nonfederal organizations responsible for protecting CUI\n- Individuals with system development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Individuals with acquisition or procurement responsibilities (e.g., contracting officers)\n- Individuals with system, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Individuals with security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, analysts, independent verifiers and validators)\n\nThe above roles and responsibilities can be viewed from two perspectives:\n\n- Federal perspective : The entity establishing and conveying the security requirements in contractual vehicles or other types of agreements\n- Nonfederal perspective : The entity responding to and complying with the security requirements set forth in contracts or agreements\n\n## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology.\nITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.4.2 | Vulnerabilities... 3.4.2 Vulnerabilities\n\nThis document is guided by NIST SP 800-161 Revision 1 [3], which describes an ICT supply chain vulnerability as the following:\n\n' A vulnerability is a weakness in an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source […] . 3.4.2 PR."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-223\n\n## High-Performance Computing Security\n\nArchitecture, Threat Analysis, and Security Posture\n\nYang Guo Ramaswamy Chandramouli Lowell Wofford Rickey Gregg Gary Key Antwan Clark Catherine Hinton Andrew Prout Albert Reuther Ryan Adamson Aron Warren Purushotham Bangalore Erik Deumens\n\nCsilla Farkas\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-223\n\n\n\n## NIST Special Publication 800 NIST SP 800-223\n\n## High-Performance Computing Security\n\nArchitecture, Threat Analysis, and Security Posture\n\nYang Guo Ramaswamy Chandramouli\n\nComputer Security Division\n\nInformation Technology Laboratory\n\nLowell Wofford Amazon.com, Inc. Rickey Gregg Gary Key\n\nHPCMP\n\nAntwan Clark Laboratory for Physical Sciences\n\nCatherine Hinton\n\nLos Alamos National Laboratory\n\nAndrew Prout Albert Reuther MIT Lincoln Laboratory\n\nRyan Adamson\n\nOak Ridge National Laboratory\n\nAron Warren Sandia National Laboratories\n\nPurushotham Bangalore\n\nUniversity of Alabama\n\nErik Deumens University of Florida\n\nCsilla Farkas University of South Carolina\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-223\n\nFebruary 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/204/d/final, including related content, potential updates, and document history. | Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Software Supply Chain (SSC) -Definition and Model .....................................................................4 |\n| 2.4.1. Software Supply Chain Defects ....................................................................................................6 |\n| 2.4.2. Software Supply Chain Attacks.....................................................................................................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1. Developer Environment ...............................................................................................................8 |\n| 3.1.2. Threat Actors................................................................................................................................8 |\n| 3.1.3. Attack Vectors ..............................................................................................................................9 |\n| 3.1.4. Attack Targets (Assets).................................................................................................................9 |\n| 3.1.5."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nINCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XI\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\nThe rapid development and wide application of distributed network systems have made network security - especially access control and data privacy - ever more important. Blockchain technology offers features such as decentralization, high confidence, and tamper-resistance, which are advantages to solving auditability, resource consumption, scalability, central authority, and trust issues - all of which are challenges for network access control by traditional mechanisms. This document presents general information for blockchain access control systems from the views of blockchain system properties, components, functions, and supports for access control policy models. Considerations for implementing blockchain access control systems are also included.\n\nBlockchain properties improve the security, flexibility, scalability, integrity, and confidentiality of AC data/logs and processes (compared to traditional AC systems) by allowing organizations to verify and audit AC data transactions and processes to track the states of their AC systems hosted on distributed sites [SP162].\n\nBlockchain systems provide an alternative (or complimentary) system for reliability, security, accountability, and scalability for AC systems. Blockchain characteristics - such as transparency, distributed computing/storage, and a tamper-evident/tamper-resistant design - help to prevent AC data from being accessed or modified by malicious users. Access logs are also recorded in blocks that allow for the detection of malicious activities. Blockchain system components and their advantages for AC systems are:"}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 7)"}, {"role": "assistant", "content": "...........................22 | |\n| 5.1.2.\n| Threats and Attacks ................................................................................................23 | |\n| 5.2. | Performance..............................................................................................................24 | |\n| 5.2.1. | Computational Complexity.......................................................................................24 | |\n| 5.2.2. | Keys and Ciphertext Size | ........................................................................................24 |\n| 5.2.3. | Physical Limitations.................................................................................................25 | |\n| 5.3. | Access Control Policies and Model Supports.............................................................25 | |\n| 6."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide? (Part 6)"}, {"role": "assistant", "content": "e successful approach used in the first workshop, leading experts in the audit and computer communities were again invited to share their views -this time on a more focused arrangement of the subject.\nThree manageria] and five technical sessions on vulnerabilities and countering controls were the result. These Proceedings contain the findings of these eight sessions. The Co-Chairpersons of this workshop were Robert G. McKenzle, an Audit Manager with the GAO [now Eastern Region Director of Audit for the National Aeronautics and Space Administration] , and Zella G. Ruthberg, a Computer Scientist with fIBS. The GAO again gave their generous support to this important undertaking by allowing Mr. McKenzle to devote time to the planning and execution of the workshop, by sending several vital attendees, and by providing us with Mr. Donald L. Scantlebury, Director of the Financial and General Management Studies Division, as Keynote speaker and Chairperson of the session in \"Managerial and Organizational Vulnerabilities and Controls -Staff Level.\"\n\nThe Proceedings represent the thinking of the Invited participants. The views expressed do not necessarily reflect those of the National Bureau of Standards, the U. S. General Accounting Office, or any of the organizations that sponsored an individual at the workshop. However, we at the National Bureau of Standards think these Proceedings warrant careful consideration by all those seriously concerned with security of computer systems and data. \n\n1^1^ ctA^H\\_\\_\\_\\_.\\^\n\nCenr^rfor Programming Science and Technology\n\nThe National Bureau of Standards, with the support of the U.S. General Accounting Office, sponsored a second invitational workshop on computer security audit, entitled \"Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls,\" In Miami Beach, Florida, on November 28-30, 1978."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 9)"}, {"role": "assistant", "content": "led Unclassified Information (CUI) in Nonfederal Systems and Organizations [3]. Organizations can use the assessment procedures to generate evidence that the security requirements have been satisfied.\nThe scope of the security assessments conducted using the procedures described in this publication is guided and informed by the system security plans for systems that process, store, or transmit CUI. The assessment procedures offer the flexibility to customize assessments based on organizational policies and requirements, known threat and vulnerability information, system and platform dependencies, operational considerations, and tolerance for risk. 1\n\n## 1.2. Organization of This Publication\n\nThe remainder of this special publication is organized as follows:\n\n- Section 2 describes the fundamental concepts associated with assessments of security requirements, including assessment procedures, methods, objects, and assurance cases that can be created using the evidence produced during assessments. - Section 3 provides assessment procedures for the security requirements in SP 800-171, including assessment objectives and potential assessment methods and objects for each procedure. 1 The term risk refers to risks to organizational operations (i.e., mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation. See SP 800-39 [4] for additional information on organizational risk management and risk tolerance. The following sections provide additional information to support the protection of CUI:\n\n- References\n- Appendix A: Acronyms\n- Appendix B: Glossary\n- Appendix C: Security Requirement Assessments\n- Appendix D: Organization-Defined Parameters\n- Appendix E: Change Log\n\nThe contents of this publication can be used for many different assessment-related purposes to determine organizational compliance with the security requirements."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n................................................................................57 | |\n| Appendix A.\nC-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nThis guide addresses auditing the system development hfe cycle (SDLC) process for an automated information system (AIS), to ensure that controls and security are designed and built into the system. The guide also presents a process for deciding which system to audit among an organization's universe of systems. It is directed toward mid-level ADP auditors having a minimum of two years experience in ADP auditing, but can also be used by security reviewers, quaHty assurance personnel, and as a training tool for less experienced ADP auditors. ADP managers and system developers will also find it useful guidance on security and control issues. The guide is designed to provide audit/review programs for each major phase of the SDLC process and assumes a large sensitive system. The reader is expected to make appropriate modifications for small less sensitive systems. The guide represents the results of the past four years of activities by the Electronic Data Processing (EDP) Systems Review and Security Work Group of the Computer Security Project within the President's Council on Integrity and Efficiency (PCIE). (See Appendix A for more information on the Work Group.)\n\nThis guide covers auditing the system development life cycle (SDLC)^process for a system, to ensure that controls and security are designed into the system. The guide also presents a process for deciding which system to audit among an organization's universe of systems. It is directed toward mid-level ADP'^ auditors having a minimum of two years experience in ADP auditing, but can also be used by security reviewers, quality assurance personnel, and as a training tool for auditors with less experience in ADP auditing. ADP managers and system developers will also find it useful guidance on security and control issues. The guide is designed to provide audit/review programs for each major phase of the SDLC and assumes a large sensitive system."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n- Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state\n\nProcesses and procedures should be based on the incident response policy and plan. Documented procedures should explain how technical processes and other operating procedures should be performed. Procedures can be tested or exercised periodically to verify their accuracy and can be used to help train new personnel. While it is impossible to have detailed procedures for every possible situation, organizations should consider documenting procedures for responding to the most common types of incidents and threats. Organizations should also develop and maintain procedures for particularly important processes that may be urgently needed during emergency situations, such as redeploying the organization's primary authentication platform."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| | 1.1.5 | Relevant Laws and Regulations | Relevant Laws and Regulations | 4 | | | 1.1.5.1 | Requirements for Audit Involvement | Requirements for Audit Involvement | 4 | | | | 1.1.5.2 | Requirements for Internal Control | 5 | | 1.2 | RISKS GENERATED BY COMPUTER TECHNOLOGY | RISKS GENERATED BY COMPUTER TECHNOLOGY | RISKS GENERATED BY COMPUTER TECHNOLOGY | 6 | | | 1.2.1 Overview of Risks | 1.2.1 Overview of Risks | 1.2.1 Overview of Risks | 6 | | | 1.2.1.1 | | Definitions | 7 | | | | 1.2.1.2 | Vulnerability/Risk Related Requirements | 7 | | | 1.2.2 | Risks in a Computerized Environment | Risks in a Computerized Environment | 8 | | | | 1.2.2.1 | Additional Risks Present in a Computerized Environment | 8 | | | | 1.2.2.2 | Assessing Vulnerabilities Through the Audit Process | 9 | | 1.3 | CONTROL OBJECTIVES AND STANDARDS IN A COMPUTER ENVIRONMENT | CONTROL OBJECTIVES AND STANDARDS IN A COMPUTER ENVIRONMENT | CONTROL OBJECTIVES AND STANDARDS IN A COMPUTER ENVIRONMENT | 10 | | | 1.3.1 | Impact of the Computer on Controls | Impact of the Computer"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Data Structure for Integrity Protection with Erasure Capability provide? (Part 6)"}, {"role": "assistant", "content": "The total number of data blocks in the matrix is N 2 -N since the diagonal is null. Thus, the last\n- numbered block in a filled matrix of N rows and columns is number N 2 -N .\n- Lower half: Numbered from 0, with no data blocks on the diagonal, the total of blocks for i rows in the lower half (below diagonal) is ( i + 1) 2 -( i +1) = i 2 + i , with the last data block in the lower half numbered as i 2 + i , and because the diagonal is empty, j = i -1 . The first data block in row i is i 2 -i +2 , with j = 0 . - Upper half: the last upper half data block in column j is j 2 + j -1 , with i = j -1 . For a block B in the lower half ( B is even), i, j indices can be computed as:\n\n\n\nand for block B in the upper half ( B is odd), i, j indices can be computed as: :\n\n\n\nNote: [ ϵ ] is the Iverson bracket where [ ϵ ] = 1 if expression ϵ evaluates to true , and 0 otherwise. Blocks can now be deleted by overwriting with zeroes, with one row and one column hash recalculated. Specifically, after deleting block i, j , row i and column j hash values are recalculated. The block matrix data structure may have utility for incorporation into applications requiring integrity protection that currently use permissioned blockchains. This capability could for example be useful in meeting privacy requirements such as the European Union General Data Protection Regulation (GDPR), which requires that organizations make it possible to delete all information related to a particular individual, at that person's request. This requirement may be incompatible with current blockchain data structures, including permissioned blockchains [2] [3] [4], because blockchains are designed to ensure that block contents are immutable. Any change in a blockchain will invalidate subsequent hashes in following blocks, losing integrity protection."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide? (Part 8)"}, {"role": "assistant", "content": "--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| Table 2.\nTerms and definitions........................................................... | 3 |\n| Table 3. Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 5 |\n| Table 4. Basic operations and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 6 |\n| Table 5. The constants const 𝑖 to derive round constants of the Ascon permutations. | 9 |\n| Table 6. Lookup table representation of SBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| Table 7. Security strength of Ascon-AEAD128 with 𝜆 -bit tag in the 𝑢 -key setting, where ( 𝑁 , 𝐴 ) pairs are distinct for encryption per key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 21 |\n| Table 8. Integrity security strength of Ascon-AEAD128 with 𝑢 keys in the nonce- misuse setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 22 |\n| Table 9. Security strengths of Ascon-Hash256 , Ascon-XOF128 , and Ascon-CXOF128 algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 31 |\n| Table 10. Address for each byte of Ascon state word 𝑆 𝑖 in memory on little-endian and big-endian machines, where the word 𝑆 𝑖 begins at memory address 𝑎 . . . . . . . . . . | 36 |\n| Table 11. Examples of padding an unsigned integer 𝑥 to a 64-bit block, where 𝑥 encodes a sequence of bytes that each have value 0xFF in little-endian byte order . | 38 |\n| Table 12."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "e of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management.\nFigure 1: Risk Management 3-Tiered Approach\n\n\n\nThe 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. The security controls in SP 800-53 Rev. 4 support Step Two of the RMF, and a detailed catalog of these controls is provided in Appendix F. For ease of use in the security control selection and specification process, controls are organized into eighteen families, each containing security controls related to the general security topic of the family. Security controls involve aspects of policy, oversight, supervision, manual processes, individual actions, or automated mechanisms implemented by information systems/devices. The security control structure consists of the\n\nfollowing components: (i) a control section; (ii) a supplemental guidance section; (iii) a control enhancements section; (iv) a references section; and (v) a priority and baseline allocation section."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.4. 3.2.4\n\nBiometric comparison can be performed locally on a device being used by the claimant\nor at a central verifier. 3.2.4."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.4.2. 3.4.2. 3.4.2 covers state agency MFA."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 4)"}, {"role": "assistant", "content": "guidance focused on the developers and providers of technology. NIICS' mission is to help organizations build, evaluate, and assess the cybersecurity of\n\nproducts and services in their supply chains.\nThis project aligns with that mission by demonstrating how organizations can verify that the internal components of the computing devices they acquire are genuine and have not been tampered with. This prototype relies on device vendors storing information within each device and organizations using a combination of commercial off-the-shelf and open-source tools that work together to validate the stored information. By doing this, organizations can reduce the risk of compromise to products within their supply chains. In this approach, device vendors create an artifact within each device that securely binds the device's attributes to the device's identity. The customer who acquires the device can validate the artifact's source and authenticity, then check the attributes stored in the artifact against the device's actual attributes to ensure they match. A similar process can be used to periodically verify the integrity of computing devices while they are in use. The authoritative source of information regarding the provenance and integrity of the components provides a strong basis for trust in a computing device. Hardware roots of trust are the foundation upon which the computing system's trust model is built, forming the basis in hardware for providing one or more security-specific functions for the system. Incorporating hardware roots of trust into acquisition and lifecycle management processes enables organizations to achieve better visibility into supply chain attacks and to detect advanced persistent threats and other attacks. By leveraging hardware roots of trust capabilities as a computing device traverses the supply chain, we can maintain trust in the computing device throughout its operational lifecycle."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\ne field of digital forensics. This guide attempts to bridge the gap by providing an indepth look into mobile devices and explaining technologies involved and their relationship to forensic procedures.\nThis document covers mobile devices with features beyond simple voice communication and text messaging capabilities. This guide also discusses procedures for the validation, preservation, acquisition, examination, analysis, and reporting of digital information."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| ^ | 3.2.2 | Size of Review Task | Size of Review Task | 49 | |-----------|------------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------|-----------| | 3.3 | BACKGROUND ON THE METHODOLOGY | BACKGROUND ON THE METHODOLOGY | BACKGROUND ON THE METHODOLOGY | 49 | | | 3.3.1 | The Invitational Workshop | The Invitational Workshop | 49 | | | 3.3.2 | Workshop Points of Agreement | Workshop Points of Agreement | 49 | | 3.4 | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | AWORK PRIORITY SCHEME FOR THE ADP AUDITOR | 50 | | | 3.4.1 | Assumptions and Caveats | Assumptions and Caveats | 50 | | | 3.4.2 | Audit Planning/Prioritization Process | Audit Planning/Prioritization Process | 51 | | | 3.4.3 | Non-Discretionary Audits | Non-Discretionary Audits | 51 | | | 3.4.4 | Risk Evaluation Levels and Dimensions | Risk Evaluation Levels and Dimensions | 53 | | | 3.4.5 | Two Level Work Priority Dimensions/Characteristics | Two Level Work Priority Dimensions/Characteristics | 54 | | | 3.4.5.1 Level I: | 3.4.5.1 Level I: | 3.4.5.1 Level I: | .....55 | | | 3.4.5.1.1 Mission Impact/Strategic Value/Organization | 3.4.5.1.1 Mission Impact/Strategic Value/Organization"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.4.1 | Requisitos de la red para admitir una ZTA... 3.4.1 Requisitos de la red para admitir una ZTA\n\n1. 3.4.1, todo el tráfico se inspecciona, se registra en la red y se analiza con el fin de identificar y reaccionar ante posibles ataques contra la empresa."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body ...................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 4)"}, {"role": "assistant", "content": "OIA). NIST SP 800-63A-4\nJuly 2025\n\nAbstract\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nThis guideline focuses on identity proofing and enrollment for use in digital\nauthentication.\nDuring the process of identity proofing, an applicant provides evidence\nto a credential service provider (CSP) reliably identifying themselves, thereby allowing\nthe CSP to assert that identification at a useful identity assurance level. This document\ndefines technical requirements for each of three identity assurance levels. The guidelines\nare not intended to constrain the development or use of standards outside of this\npurpose. This publication supersedes NIST Special Publication (SP) 800-63A. Keywords\n\nauthentication; credential service provider; digital authentication; identity proofing;\nfederation. Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems. The Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Awareness and Training?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\ness. Education and Awareness provides the educational content required to support customers and others in the secure use and safeguarding of IoT devices and associated systems, software, and hardware.\nBy making customers and others in the ecosystem more knowledgeable about how to secure the IoT devices, and how to most effectively use the device's cybersecurity capabilities, manufacturers can help reduce the number of occurrences and related severity of IoT device compromises, thwart attacks against the devices, and reduce the number of vulnerabilities that are exploited and lead to compromised devices."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 2)"}, {"role": "assistant", "content": "divisions:\n\nApplied Mathematics — Electricity — Mechanics — Heat — Optical Physics — Center for Radiation Research — Lab-\noratory Astrophysics- — Cryogenics^ — Electromagnetics — Time and Frequency'.\nTHE INSTITUTE FOR MATERIALS RESEARCH conducts materials research leading to improved methods of measure-\nment, standards, and data on the properties of well-characterized materials needed by industry, commerce, educational insti-\ntutions, and Government: provides advisory and research services to other Government agencies; and develops, produces, and\ndistributes standard reference materials. The Institute consists of the Office of Standard Reference Materials, the Office of Air\nand Water Measurement, and the following divisions:\n\nAnalytical Chemistry — Polymers — Metallurgy — Inorganic Materials — Reactor Radiation — Physical Chemistry. THE INSTITUTE FOR APPLIED TECHNOLOGY provides technical services developing and promoting the use of avail-\nable technology; cooperates with public and private organizations in developing technological standards, codes, and test meth-\nods; and provides technical advice services, and information to Government agencies and the public. The Institute consists of\nthe following divisions and centers:\n\nStandards Application and Analysis —• Electronic Technology — Center for Consumer Product Technology: Product\nSystems Analysis; Product Engineering — Center for Building Technology; Structures, Materials, and Safety; Building\nEnvironment; Technical Evaluation and Application — Center for Fire Research: Fire Science; Fire Safety Engineering."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\n- Broaden the discussions from a focus on the IoT system device component to considerations of entire IoT products (and connected products) to better reflect the wide variety of applications and use cases that exist. - Develop the relationship between risk assessment and threat modeling activities. - Address the different cybersecurity considerations among Information Technology (IT), Internet of Things (IoT), Operational Technology (OT), and Industrial Internet of Things (IIoT)\n- Identify insights, considerations, approaches, etc. for IoT based on the NIST Privacy Framework, NIST Cyber Physical Systems/IoT Framework, NIST Cybersecurity Framework 2.0, and the NIST Secure Software Development Framework. Stacey Higginbotham of Consumer Reports noted that connected devices establish an ongoing relationship between the buyer, seller, and manufacturer. The lifetime of a connected product is often separate from its physical state. While physical products fail in visible ways, software degrades more quickly, often without consumer awareness. The industry also lacks adequate support for maintenance. Stacey's discussion highli ghted three key areas: zombie hordes of end of life devices, supported devices with unsupportive owners, and herd immunity against malicious actors. ' Zombie devices ' are those that no longer receive software support and security updates. Higginbotham noted that unsupportive owners can neglect cybersecurity issues, leading to vulnerabilities. Herd immunity in cybersecurity requires collective action from manufacturers and consumers. Most consumers are unaware or indifferent to the end of life status of their products, resulting in ' zombie hordes ' . Communicating end of life status and dates is crucial, including proactive notification to consumers, retailers, and third parties. Companies should track devices to address critical vulnerabilities and create structured options for off-ramping zombie devices."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 5)"}, {"role": "assistant", "content": "edge and skills for security awareness professionals within the federal government. The following is a high-level overview of these results, with statistics from the survey unless otherwise indicated.\n## Security Awareness Duties and Work Roles\n\n- 90% of survey participants performed security awareness duties on a part-time basis, with just over 55% spending 25% or less of their time. Focus group participants had similar allocations: 93% part-time and 39% spending 25% of less time. - 50% of survey participants either did not know or were not sure of their National Initiative for Cybersecurity Education (NICE) Workforce Framework for Cybersecurity (NICE Framework) Work Role. This was despite the Federal Cybersecurity Workforce Assessment Act which requires federal agencies to assign the NICE Framework coding structure to its cybersecurity and information technology (IT) positions. Those participants who knew their Work Role identified 11 unique Work Roles. ## Professional Backgrounds\n\n- Participants were diverse in their educational backgrounds, with 83% from focus group and 51% from the survey indicating that they have at least one non-STEM degree. - 92% of survey participants had worked in cybersecurity positions and 76% had worked in IT jobs that did not have a cybersecurity focus. Less than 25% had worked in a variety of\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\nother fields, including non-IT fields such as instructional design and education, communications, and human resources. We found that 40% of participants had only ever worked in a technical field (cybersecurity, IT, or software development). ## Knowledge and Skills\n\n- Survey participants rated the importance of having specific knowledge and skills represented on their teams."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guidelines on Mobile Device Forensics provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-101 Revision 1\n\n## Guidelines on Mobile Device Forensics\n\nRick Ayers Sam Brothers Wayne Jansen http://dx.doi.org/10.6028/NIST.SP.800-101r1\n\n\n\n## NIST Special Publication 800-101 Revision 1\n\n## Guidelines on Mobile Device Forensics\n\nRick Ayers Software and Systems Division Information Technology Laboratory\n\nSam Brothers U.S. Customs and Border Protection Department of Homeland Security Springfield, VA\n\nWayne Jansen Booz Allen Hamilton McLean, VA\n\nhttp://dx.doi.org/10.6028/NIST.SP. 800-101r1\n\nMay 2014\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology\n\nPatrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Management Act of 2002 (FISMA), 44 U.S.C. § 3541 et seq., Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 5)"}, {"role": "assistant", "content": "While the NCCoE used a suite of commercial products to address this challenge, this guide does not endorse these particular products, nor does it guarantee compliance with any regulatory initiatives.\nYour organization ʼ s information security experts should identify the products that will best integrate with your existing tools and IT system infrastructure. Your organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring and implementing parts of a solution. ## BENEFITS\n\nThe NCCoE's practice guide to Data Integrity: Detecting and Responding to Ransomware and Other Destructive Events can help your organization:\n\n-  develop a strategy for detecting and responding to a data integrity cybersecurity event\n-  facilitate effective detection and response to adverse events, maintain operations, and ensure the integrity and availability of data critical to supporting business operations and revenuegenerating activities\n-  manage enterprise risk (consistent with foundations of the NIST Framework for Improving Critical Infrastructure Cybersecurity )\n\n## SHARE YOUR FEEDBACK\n\nYou can view or download the guide at https://www.nccoe.nist.gov/projects/building-blocks/dataintegrity/detect-respond. If you adopt this solution for your own organization, please share your experience and advice with us. We recognize that technical solutions alone will not fully enable the benefits of our solution, so we encourage organizations to share lessons learned and best practices for transforming the processes associated with implementing this guide. To provide comments or to learn more by arranging a demonstration of this example implementation, contact the NCCoE at ds-nccoe@nist.gov."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| | Introduction ....................................................................................................1 | | |-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | 1.1 | | Purpose.......................................................................................................................1 | | | 1.2 | | Scope..........................................................................................................................2 | | | 1.3 | | Audience.....................................................................................................................3 | | | 1.4 | Document | Structure....................................................................................................4 | | | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 6)"}, {"role": "assistant", "content": "as shown in Table ES-1. Some agencies may have different names for their security areas, however each agency should establish their criteria to implement authentication consistent with this document.\nTable ES-1 - Authentication Factors for Security Areas\n\n| Security Areas | Minimum Number of Authentication Factors Required |\n|------------------|-----------------------------------------------------|\n| Controlled | 1 |\n| Limited | 2 |\n| Exclusion | 3 |\n\n[FIPS201] identifies a number of authentication mechanisms supported by mandatory features of PIV Cards. These mechanisms include Authentication using Authentication with the Card Authentication Certificate Credential (PKI-CAK), Authentication Using Off-Card Biometric Comparison (BIO), Attended Authentication Using Off-Card Biometric Comparison (BIO-A), Authentication with the PIV Authentication Certificate Credential (PKI-AUTH). In addition, PIV Cards may optionally support a number of other authentication mechanisms; these include Authentication with the Symmetric Card Authentication Key (SYM-CAK) and Authentication Using On-Card Biometric Comparison (OCC-AUTH). Access points should not rely solely on an\n\n1 The OMB Circular A-130 can be located at https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/circulars/A130/a130revised.pdf . authentication mechanism that requires optional card features as it is not guaranteed that the optional features to be used for authentication are present on all cards. Many changes in this document were made to align SP 800-116 with revision 2 of FIPS 201 (FIPS 201-2). For example, credential validation is now required (see Section 4.4). The CHUID authentication mechanism has been deprecated due to security concerns."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nwhere speakers and attendees shared suggestions for adapting secure software development practices and tasks to accommodate the unique aspects of AI model development and the software leveraging them.\n- AI Risk Management Framework (AI RMF) [2] and the NIST AI RMF Playbook [11]\n- Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations [3]\n- Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile [12]\n- Towards a Standard for Identifying and Managing Bias in Artificial Intelligence [4]\n- Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations [10]\n- NIST Privacy Framework: A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0 [13]\n- Integrating Cybersecurity and Enterprise Risk Management (ERM) [14]"}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.1 (NIST 3.7.1)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.7.1 | Potential Difficulties in Utilization | Potential Difficulties in Utilization | 63 |\n| | 3. 3.7.1 Potential DifTiculties in Utilization\n\n- Time and resources are needed for sufficient data collection."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.7.1", "cmmc_practice_id": "MA.L2-3.7.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nA UICC can contain up to three applications: SIM, USIM and CSIM. UICCs used in GSM and UMTS mobile devices use the SIM and UMTS SIM (USIM) applications, while CDMA devices use the CSIM application.\nA UICC with all three applications provides users with additional portability through the removal of the UICC from one mobile device and insertion into another. Because the SIM application was originally synonymous with the physical card itself, the term SIM is often used to refer to the physical card in lieu of UICC. Similarly the terms USIM and CSIM can refer to both the physical card as well as the respective applications supported on the UICC."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 9)"}, {"role": "assistant", "content": "| 3 PROFESSIONAL DEMOGRAPHICS...............................................................................\n3 | 3 PROFESSIONAL DEMOGRAPHICS............................................................................... 3 |\n| 3.1 SECURITY AWARENESS DUTIES ........................................................................................... 3 | 3.1 SECURITY AWARENESS DUTIES ........................................................................................... 3 | 3.1 SECURITY AWARENESS DUTIES ........................................................................................... 3 |\n| 3.1.1 Security Awareness Roles and Percentage of Time.................................................... 3 3.1.2 Years of Security Awareness Experience.................................................................... 4 | 3.1.1 Security Awareness Roles and Percentage of Time.................................................... 3 3.1.2 Years of Security Awareness Experience.................................................................... 4 | 3.1.1 Security Awareness Roles and Percentage of Time...................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 8)"}, {"role": "assistant", "content": "Network Monitoring and Observability Tools | 3.4.1. Network Monitoring and Observability Tools | ............................................................12 |\n| 3.4.2. Automated Network Provisioning Tools....................................................................12 | 3.4.2."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n| 1 INTRODUCTION.................................................................................................................\n1 | 1 INTRODUCTION................................................................................................................. 1 |\n| 2 REPORTING CONVENTIONS.......................................................................................... 2 | 2 REPORTING CONVENTIONS.......................................................................................... 2 | 2 REPORTING CONVENTIONS.......................................................................................... 2 |\n| 3 PROFESSIONAL DEMOGRAPHICS............................................................................... 3 | 3 PROFESSIONAL DEMOGRAPHICS............................................................................... 3 | 3 PROFESSIONAL DEMOGRAPHICS..............................................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| 4.3 | Supporting Platform Integrity Validation Systems......................................................24 | Supporting Platform Integrity Validation Systems......................................................24 | |\n|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|----|\n| | 4.3.1 | Host Integrity at Runtime and Start-up Attestation Certificate Authority (HIRS ACA)24 | |\n| | 4.3.2 | Network Boot Services ............................................................................................... | 26 |\n| | 4.3.3 | Platform Manifest Correlation System......................................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n...........13 |\n| 3.2.1. MFA Users ..................................................................................................................................13 |\n| 3.2.2.\nIT Support Staff...........................................................................................................................14 |\n| 3.2.3. Other Agencies ...........................................................................................................................14 |\n| 3.2.4. Procurement Teams...................................................................................................................14 |\n| 3.2.5. Compliance Teams .....................................................................................................................15 |\n| 3.2.6. Legal Teams................................................................................................................................15 |\n| 3.2.7. Technology Vendors...................................................................................................................15 |\n| 3.4.1. Local Agency MFA Architectures................................................................................................17 |\n| 3.4.2. State MFA Deployments.............................................................................................................21 |\n| 3.4.3. Implementing MFA with VPNs ...................................................................................................25 |\n| 4. Key Takeaways.............................................................................................................................29 |\n| References.......................................................................................................................................31 |\n| Appendix A."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n## The Federal Cybersecurity Awareness Workforce\n\n## The Federal Cybersecurity Awareness Workforce\n\nOrganizational cybersecurity awareness (hereafter shortened to 'security awareness') programs may experience a number of challenges, including lack of funding and staff with the appropriate knowledge and skills to manage an effective program. While prior surveys and research have examined programs in the private sector, there is little understanding of whether these findings also apply within the U.S. government. To address this gap and better understand the needs, challenges, practices, and necessary competencies of federal security awareness teams and programs, NIST conducted a research study that leveraged both qualitative and quantitative methodologies. This companion document to NISTIR 8420 'Federal Cybersecurity Awareness Programs: A Mixed Methods Research Study' reports on a subset of study results focused on identifying the current job classifications, roles, and desired knowledge and skills for security awareness professionals within the federal government. Insights gained from these results are informing guidance and other initiatives to aid federal organizations in building security awareness teams with the appropriate competencies. While focused on the U.S. government, findings may also have implications for organizational security awareness professionals in other sectors."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 3)"}, {"role": "assistant", "content": "efore the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 5)"}, {"role": "assistant", "content": ".................................4 |\n| 2.2.1. Speaker Viewpoints......................................................................................................................5 |\n| 2.2.2.\nKey Highlights ...............................................................................................................................6 |\n| 2.3.1. Speaker Viewpoints......................................................................................................................6 |\n| 2.3.2. Key Highlights ...............................................................................................................................8 |\n| 2.4.1. Speaker Viewpoints......................................................................................................................9 |\n| 2.4.2. Key Highlights .............................................................................................................................11 |\n| 2.5.1. Speaker Viewpoints....................................................................................................................11 |\n| 2.5.2. Key Highlights .............................................................................................................................13 |\n| 3. Summary and Road Ahead ...........................................................................................................15 |\n| Appendix A. Workshop Agenda........................................................................................................16 |\n| List of Figures |\n| Fig. 1. Components for securing microelectronics................................................................................1 |\n| Fig. 2."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 10)"}, {"role": "assistant", "content": "| DigiCert .........................................................................................................................\n7 |\n| | 4.1.3 | F5 ................................................................................................................................... 8 |\n| | 4.1.4 | JPMorgan Chase &Co................................................................................................... 8 |\n| | 4.1.5 | Mira Security ................................................................................................................. 8 |\n| | 4.1.6 | NETSCOUT ....................................................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 6)"}, {"role": "assistant", "content": "Examples and Informative References to add to this document. All feedback should be sent to ssdf@nist.gov. ## Trademark Information\n\nAll registered trademarks belong to their respective organizations.\n## Acknowledgments\n\nThe authors thank all of the organizations and individuals who provided numerous public comments and other thoughtful input for this publication. In response to Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and Use of Artificial Intelligence , NIST held a January 2024 workshop, where speakers and attendees shared suggestions for adapting secure software development practices and tasks to accommodate the unique aspects of AI model development and the software that leverages them. The authors also thank all of their NIST colleagues and external experts who provided suggestions and feedback that helped shape this publication. 1 The terms 'producer' and 'acquirer' were selected for consistency with the Audience statement in NIST SP 800-218. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document provide? (Part 2)"}, {"role": "assistant", "content": "Jake Wills US Bank Corporation\n\nJane Gilbert D'Nan Godfrey Thales TCT\n\nDean Cocklin Avesta Hojjati DigiCert\n\n*Contributed while a NIST Employee\n\nDavid Wells\n\nFinal September 2025\n\n\n\nU.S.\nDepartment of Commerce Howard Lutnick, Secretary\n\nNational Institute of Standards and Technology\n\nCraig Burkhardt, Acting Under Secretary of Commerce for Standards and Technology and Acting NIST Director\n\n## DISCLAIMER\n\nCertain commercial en��es, equipment, products, or materials may be iden�fied by name or company logo or other insignia in order to acknowledge their par�cipa�on in this collabora�on or to describe an experimental procedure or concept adequately. Such iden�fica�on is not intended to imply special status or rela�onship with NIST or recommenda�on or endorsement by NIST or NCCoE; neither is it intended to imply that the en��es, equipment, products, or materials are necessarily the best available fo r the purpose. While NIST and the NCCoE address goals of improving management of cybersecurity and privacy risk through outreach and applica�on of standards and best prac�ces, it is the stakeholder's responsibility to fully perform a risk assessment to include the current threat, vulnerabili�es, likelihood of a compromise , and the impact should the threat be realized before adop�ng cybersecurity measures such as this recommenda�on. Na�onal Ins�tute of Standards and Technology Special Publica�on 1800 -37 , Natl. Inst. Stand. Technol. Spec. Publ. 1800 -37 , 63 pages, ( September 2025 ), CODEN: NSPUE2\n\n## NATIONAL CYBERSECURITY CENTER OF EXCELLENCE\n\nThe Na�onal Cybersecurity Center of Excellence (NCCoE), a part of the Na�onal Ins�tute of Standards and Technology (NIST), is a collabora�ve hub where industry organiza�ons, government agencies, and academic ins�tu�ons work together to address businesses' most pressing cybersecurity issues."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Awareness and Training?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nTo complement the core baseline from NISTIR 8259A, the IoT non-technical supporting capability core baseline is a set of actions performed by manufacturers and/or designated supporting third parties (called supporting parties ). These actions will help others (e.g., customers, end-users) use the cybersecurity capabilities of IoT devices, and support the on-going cybersecurity of the IoT device and the system and networks the device connects to (the digital ecosystem). Providing such non-technical cybersecurity support through educational materials or other types of non-technical tools and actions can benefit the entire IoT device ecosystem and allow manufacturers to better support the cybersecurity of devices throughout the entire device lifecycle. Both device cybersecurity capabilities and non-technical supporting capabilities are vital to customers' abilities to achieve their needs and goals. Similar to the IoT device cybersecurity capability core baseline in NISTIR 8259A, this IoT non-technical supporting capability core baseline is intended to give organizations a starting point for establishing nontechnical actions to support IoT device cybersecurity risk management. Specifically, this publication describes four recommended non-technical supporting capabilities related to the full lifecycle of cybersecurity management that manufacturers should implement to support the IoT devices they make for the full length of life: 1) Documentation; 2) Information and Query Reception; 3) Information Dissemination; and 4) Education and Awareness. Education and Awareness provides the educational content required to support customers and others in the secure use and safeguarding of IoT devices and associated systems, software, and hardware."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nParticipant quotes from the focus groups and open-ended questions in the survey provide insights into the range of responses. Participants' comments reflect motivators for regularly updating annual training, such as addressing emerging threats and organizational feedback:\n\n'For me, usually my first go-to is what is CISA [Cybersecurity and Infrastructure Security Agency] about, right, because they kind of got the scope on the entire .gov space. At the same time, they work with industry as well. So, anything that they are bringing to light, I try to emulate that and try to kind of go, 'Hey, this is something that CISA's saying is important as a threat. You, as an individual, need to know that this is a threat. This way you are aware of what's going on the other way'.' (N10)\n\n'We annually meet with [an external organization's] computer security incident response center, and I get them to produce a list of user-induced or incidents that could have been prevented by users, kind of by category. And I take a compilation of those, the most recent Verizon data breach report, and the IBM threat report and kind of take a mix of the top threats from those three sources and kind of whittle them down into about eight or so topics for the cybersecurity awareness training.' (D06)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 3)"}, {"role": "assistant", "content": "re authorized and expected. Provenance is the comprehensive history of a device throughout the entire life cycle from creation to ownership, including changes made within the device or its components.\nAssuming without verification that all acquired computing devices are genuine and unmodified increases the risk that a compromise will affect products in an organization's supply chain and go unnoticed at the time, which in turn increases risks to customers and end users. Organizations currently lack the ability to cost effectively distinguish trustworthy products from others, meaning they are genuine and have not been inappropriately altered. Having this ability is a critical foundation of cyber supply chain risk management (C-SCRM). C-SCRM is the process of identifying, assessing, and mitigating risks associated with the distributed and interconnected nature of supply chains. C-SCRM presents challenges to many industries and sectors, requiring a coordinated set of technical and procedural controls to mitigate risks throughout the design, manufacturing, acquisition, provisioning, operations, and decommissioning stages of a product's life. ## This practice guide can help your organization:\n\n-  Avoid using untrustworthy technology components in your products\n-  Enable your customers to readily verify that your products are genuine\n-  Prevent compromises of your own information and systems caused by acquiring and using compromised technology products\n\n## SOLUTION\n\nTo address these challenges, the NCCoE collaborated with technology vendors to develop a prototype implementation in harmony with the National Initiative for Improving Cybersecurity in Supply Chains (NIICS), which emphasizes tools, technologies, and guidance focused on the developers and providers of technology. NIICS' mission is to help organizations build, evaluate, and assess the cybersecurity of\n\nproducts and services in their supply chains."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology.\nITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems. The Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations.\n\n3.10. Requirements for Notifications of Identity Proofing . . . . . . . . . . . .\n\n3.13. Requirements for the Validation of Physical Evidence . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 7)"}, {"role": "assistant", "content": "............................................24 |\n| Appendix B. List of Symbols, Abbreviations, and Acronyms...........................................25 | Appendix B.\nList of Symbols, Abbreviations, and Acronyms...........................................25 |\n\n## Introduction\n\n## Scope\n\nThis document specifies the Cryptographic Module Validation Program (CMVP) modifications of the methods to be used by a Cryptographic and Security Testing Laboratory (CSTL) to demonstrate conformance. This document also specifies the modification of documentation for providing evidence to demonstrate conformity. Unless otherwise specified in this document, the test requirements are specified in ISO/IEC 19790 Annex B and ISO/IEC 24759 Section 6.14. ## Normative References\n\nThis section identifies the normative references cited as ISO/IEC 19790 and ISO/IEC 24759. The specific editions to be used are ISO/IEC 19790:2012 and ISO/IEC 24759:2017. The version 19790:2012 referenced here includes the corrections made in 2015. National Institute of Standards and Technology (2019) Security Requirements for Cryptographic Modules. (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 140-3. https://doi.org/10.6028/NIST.FIPS.140-3\n\n## Document Organization\n\n## General\n\nSection 3.1 of this document specifies any modifications to ISO/IEC 19790 Annex B and ISO/IEC 24759 Section 6.14. Section 3.2 identifies any additional requirements for the security policy that are documented in other publications. Section 3.3 describes the security policy structure and how the requirements in Sections 3.1 and 3.2 map into that structure. The requirements statements are presented as originally written in ISO/IEC 19790 Annex B and ISO/IEC 24759. These often include acronyms and abbreviations spelled out earlier within those documents."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}}