{"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 19)"}, {"role": "assistant", "content": "| |\n| D.4.1.10.\nRevision and Maintenance...............................................................................................228 | |\n| Appendix E. FASCSA......................................................................................................................... | 230 |\n| E.1.1. Purpose, Audience, and Background........................................................................................230 | |\n| E.1.2. Scope ........................................................................................................................................230 | |\n| E.1.3. Relationship to NIST SP 800-161, Rev. 1, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations ...........................................................................................231 | |\n| E.2.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 18}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 18)"}, {"role": "assistant", "content": "adversarial group that possesses the expertise and resources that allow it to create opportunities to achieve its objectives by using multiple attack vectors, including cyber, physical, and deception.\nThe APT objectives include establishing a foothold within the infrastructure of targeted organizations for purposes of exfiltrating information; undermining or impeding critical aspects of a mission, function, program, or organization; or positioning itself to carry out these objectives in the future. The APT pursues its objectives repeatedly over an extended period, adapts to defenders' efforts to resist it, and is determined to maintain the level of interaction needed to execute its objectives. While the category of CUI itself does not require greater protection, CUI associated with critical programs or high value assets is at greater risk because the APT is more likely to target such information and therefore requires additional protection. ## CUI ENHANCED SECURITY REQUIREMENTS\n\nControlled Unclassified Information has the same value , whether such information is resident in a federal system that belongs to a federal agency or a nonfederal system that belongs to a nonfederal organization. Accordingly, the enhanced security requirements in this publication are consistent with and complementary to the guidelines used by federal agencies to protect CUI. The 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 APT is extremely dangerous to the national and economic security interests of the United States since organizations are very dependent on systems of all types, including traditional Information Technology (IT) systems, Operational Technology (OT) systems, Internet of Things\n\n6 [32 CFR 2002] was issued on September 14, 2016, and went into effect on November 14, 2016."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 17}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 Identification and Authentication?"}, {"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": "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 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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 11)"}, {"role": "assistant", "content": "..................................................... 11 | CHAPTER THREE THE REQUIREMENTS.........................................................................................\n11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ................................................................................................... 13 |\n| 3.3 AUDIT ANDACCOUNTABILITY | ................................................................................................. 14 |\n| 3.4 CONFIGURATIONMANAGEMENT | ........................................................................................... 14 |\n| 3.5 IDENTIFICATIONANDAUTHENTICATION | ................................................................................. 16 |\n| 3.6 INCIDENT RESPONSE | .............................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 20)"}, {"role": "assistant", "content": "and communications. Therefore, CUI that is processed, stored, or transmitted by any of the above systems related to a critical program or high value asset requires additional protection from the APT.\n## 1.1 PURPOSE AND APPLICABILITY\n\nThe purpose of this publication is to provide federal agencies with a set of enhanced security requirements 9 for protecting the confidentiality , integrity , and availability of CUI: (1) when the CUI is resident in a nonfederal system and organization, (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, 10 and (3) where there are no specific safeguarding requirements for protecting the CUI prescribed by the authorizing law, regulation, or government-wide policy for the CUI category listed in the CUI Registry. 11 The enhanced security requirements address the protection of CUI by promoting: (1) penetration-resistant architecture, (2) damage-limiting operations, and (3) designs to achieve cyber resiliency and survivability. 12 The enhanced security requirements are intended to supplement the basic and derived security requirements in [SP 800-171] and are for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations. The enhanced security requirements apply to components 13 of nonfederal systems that process, store, or transmit CUI associated with a critical program or a high value asset or that provide security protection for such components. If nonfederal organizations designate specific system components for the processing, storage, or transmission of CUI associated with a critical program or a high value asset, those organizations may limit the scope of the enhanced security requirements by isolating the designated system components in a separate CUI security domain."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 19}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 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 additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 13)"}, {"role": "assistant", "content": "n the risk tolerance of the organizations or communities of interest developing the overlays. General guidance on overlays is provided in section 3.3 and an overlay template is provided in Appendix I.\nThe template is included as an example only-organizations may choose to use other formats or modify the format in this appendix based on organizational needs and the type of overlay being developed. The level of detail included in the overlay is at the discretion of the organization initiating the overlay but should be of sufficient breadth and depth to provide an appropriate rationale and justification for the resulting tailored baseline developed, including any risk-based decisions made during the overlay development process. The sample overlay template consists of eight sections:\n\n- Identification;\n- Overlay Characteristics;\n- Applicability;\n- Overlay Summary;\n- Detailed Overlay Control Specifications;\n- Tailoring Considerations;\n- Definitions; and\n- Additional Information or Instructions. ## 9 Privacy\n\nFederal agencies are required to ensure that privacy protections are incorporated into information security planning. To that end, SP 800-53 Rev. 4 features eight new families of privacy controls that are based on the internationally accepted Fair Information Practice Principles (FIPPs). The proliferation of social media, Smart Grid, mobile, and cloud computing, as well as the transition from structured to unstructured data and metadata environments, have added significant complexities and challenges for federal organizations in safeguarding privacy. These challenges extend well beyond the traditional information technology security view of protecting privacy, which focused primarily on ensuring confidentiality. The families of controls are described in a similar manner to those of Appendix F (Security Controls) and Appendix G (Information Security Programs Organization-Wide Information Security Program Management Controls). SP 800-53 Rev."}], "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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 12}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 15)"}, {"role": "assistant", "content": "nks 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.\nFurther, NIST does not endorse any commercial products that may be advertised or available on these sites. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Family: Access Control\n\nDescription: Limiting information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems) and to the types of transactions and functions that authorized users are permitted to exercise.*\n\n## Getting Started with Access Control\n\n\n\nImplement policies and procedures that limit access to CUI on systems and devices to only those individuals that require such access to do their jobs . Complete a review of publicly available information , such as information on the company website. - Review the content for CUI and remove such information if discovered. CUI should not be available to the public. ## Protect CUI with device locks and session termination . - Train staff on these behaviors and establish policies that prevent unauthorized individuals from seeing CUI or other sensitive information on a device while the device is unattended by an individual. When the individual returns to their device, they will have to re-establish access by using a password or biometric authenticator\n\nFoundational Concept -Least Privilege: This involves limiting access rights to only those users who need it to accomplish assigned tasks. - Identify who has access to CUI and the system. Only those who require access to CUI should have it. For example, if a network or system administrator does not need access to CUI, their access should be restricted. - Reassign or remove privileges as necessary, such as when an individual no longer requires access to CUI and the system."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 14}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 12)"}, {"role": "assistant", "content": "d, 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_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 11}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 11)"}, {"role": "assistant", "content": "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.\nThey complement the security controls in Appendix F and focus on the programmatic, organization-wide information security requirements that are independent of any particular information system and are essential for managing information security programs. Tailoring guidance can be applied to the program management controls in a manner similar to how the guidance is applied to security controls in Appendix F. ## 7 International Information Security Standards\n\nMany 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_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 12)"}, {"role": "assistant", "content": "ramework provides a basis for the reciprocal acceptance of\nsecurity and privacy control assessment evidence and authorization decisions and facilitates\ninformation sharing and collaboration.\nNIST 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. vii\n\n\fNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nDEVELOPMENT OF INFORMATION SYSTEMS, COMPONENTS, AND SERVICES\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. 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\nr\n5\n\nI\n\n."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 11}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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......................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": "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 Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 19)"}, {"role": "assistant", "content": "rols that can be inherited by designated organizational systems, accepting the security and privacy risks to the organization's operations and assets, individuals, other organizations, and the Nation.\nAuthorizing officials also consider the risk of inheriting common controls as part of their system authorizations. The different types of authorizations are described in Appendix F. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## THE RMF IS TECHNOLOGY NEUTRAL\n\nThe RMF is purposefully designed to be technology neutral so that the methodology can be applied to any type of information system* without modification. While the specific controls selected, control implementation details, and control assessment methods and objects may vary with different types of IT resources, there is no need to adjust the RMF process to accommodate specific technologies. 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."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 18}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 18)"}, {"role": "assistant", "content": "ctor of National Intelligence, the Department of Defense, and the Committee on National Security Systems, and has established a unified risk management framework for the federal government.\nThis common foundation provides the Civil, Defense, and Intelligence Communities of the federal government and their contractors, cost-effective, flexible, and consistent methods and techniques to manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. The unified framework also provides a strong basis for reciprocal acceptance of assessment results 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 its security and privacy standards and guidelines and those developed by external organizations. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## ACCEPTANCE OF SECURITY AND PRIVACY RISK\n\nThe Risk Management Framework addresses security and privacy risk from two perspectivesan information system perspective and a common controls perspective. For an information system, authorizing officials issue an authorization to operate or authorization to use for the system, accepting the security and privacy risks to the organization's operations and assets, individuals, other organizations, and the Nation. For common controls, authorizing officials issue a common control authorization for a specific set of controls that can be inherited by designated organizational systems, accepting the security and privacy risks to the organization's operations and assets, individuals, other organizations, and the Nation."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 17}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 17)"}, {"role": "assistant", "content": "vant -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.\nThe content should include:\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?). - Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.). - How to respond to confirmed or suspected incidents. - How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI). - How to recognize and report insider threats, social engineering, and social mining. Examples of security awareness techniques include displaying posters, offering supplies inscribed with security reminders, generating email advisories or notices from leadership, and conducting awareness events -such as a lunch-and-learn or workshop. There are many resources that are free and open to the public that can be incorporated into awareness and training, such as videos, online courses, and awareness posters. The resources will likely need to be customized to meet your own unique business needs, but they offer a starting point. Resources can be found in the resources box below."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 16}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 11)"}, {"role": "assistant", "content": "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.\nThey complement the security controls in Appendix F and focus on the programmatic, organization-wide information security requirements that are independent of any particular information system and are essential for managing information security programs. Tailoring guidance can be applied to the program management controls in a manner similar to how the guidance is applied to security controls in Appendix F. ## 7 International Information Security Standards\n\nMany 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_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 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\n## 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 14)"}, {"role": "assistant", "content": "ed security services provider (MSSP), talk to others in your industry to get their perspective on vendors they have worked with and always thoroughly review any contract or agreement prior to signing.\nA helpful resource, assembled by member company participants of the National Defense Information Sharing& Analysis Center (ND-ISAC), is the Defense Industrial Base Managed Service Provider Shopping Guide for Small & Medium-Sized Businesses. You may also explore the CyberAB Marketplace to find a consulting firm to assist in NIST 800-171 implementation.* |\n| Review NIST SP 800-171A to help you understandhow the security requirements in SP 800-171 can be self-assessed or are assessed by independent, third-party entities or by the | Review NIST SP 800-171A to help you understandhow the security requirements in SP 800-171 can be self-assessed or are assessed by independent, third-party entities or by the |\n\n* 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."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 13}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n| Background - Zero Trust Principles and Zero Trust Architecture................................\n| 2 |\n| | Relationship to Other NIST Guidance Documents...................................................... | 3 |\n| | Scope......................................................................................................................... | 3 |\n| | Target Audience | ........................................................................................................."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "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 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 20)"}, {"role": "assistant", "content": "tems (including hardware, software, firmware, and documentation); and establishing and enforcing security configuration settings for information technology products employed in organizational systems.\n## Getting Started with Configuration Management\n\n\n\nChanges to a system can have potentially significant effects on the security of the system. Configuration management helps establish processes for initializing, changing and monitoring configurations to the hardware, software, or firmware components of the system or the operational procedures related to the system storing CUI. ## Limit who can make changes to the system containing CUI. - 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). ## Authorized software -allow by exception. - 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 . ## Locate CUI. - Identify the location of CUI and the system components on which the information is processed and stored. Identify who within the business has access to CUI. Again, remember to restrict this access to only those who need it. Foundational Concept -Least Functionality: Systems (databases, email systems, network drives, etc.) provide a variety of functions and services."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 19}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\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. Organizations 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."}], "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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 16)"}, {"role": "assistant", "content": "nformation, including inconsistent markings, inadequate safeguarding, and needless restrictions, both by standardizing procedures and by providing common definitions through a CUI Registry [NARA CUI].\nThe CUI Registry is the online repository of information, guidance, policy, and requirements on handling CUI, including issuances by the National Archives and Records Administration (NARA) CUI Executive Agent. The CUI Registry identifies approved CUI categories, provides general\n\n1 An information system is a discrete set of information resources organized expressly for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. Information systems also include specialized systems, such as industrial and process control systems, cyber-physical systems, IoT systems, embedded systems, and devices. The term system is used throughout this publication to represent all types of computing platforms that can process, store, or transmit CUI. 2 A federal information system is a system that is used or operated by an executive agency, a contractor of an executive agency, or another organization on behalf of an executive agency. A system that does not meet such criteria is a nonfederal system . 3 Controlled Unclassified Information is any information that law, regulation, or government-wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under [EO 13526] or any predecessor or successor order, or [ATOM54], as amended. 4 Established by Executive Order 13556, the CUI Program standardizes the way that the Executive branch handles unclassified information that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and government-wide policies. 5 [EO 13556] designated the National Archives and Records Administration (NARA) as the Executive Agent to implement the CUI Program."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 15}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 17)"}, {"role": "assistant", "content": "nd consistent with law, regulations, and government-wide policies. 5 [EO 13556] designated the National Archives and Records Administration (NARA) as the Executive Agent to implement the CUI Program.\nCHAPTER ONE PAGE 1\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\ndescriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI, including but not limited to marking, safeguarding, transporting, disseminating, reusing, and disposing of the information. [EO 13556] also required that the CUI Program emphasize openness, transparency, and uniformity of government-wide practices, and that the implementation of the program take place in a manner consistent with applicable policies established by the Office of Management and Budget (OMB) and federal standards and guidelines issued by the National Institute of Standards and Technology (NIST). The federal CUI regulation , 6 developed by the CUI Executive Agent, provides guidance to federal agencies on the designation, safeguarding, dissemination, marking, decontrolling, and disposition of CUI; establishes self-inspection and oversight requirements; and delineates other facets of the program. In certain situations, CUI may be associated with a critical program 7 or a high value asset. 8 These critical programs and high value assets are potential targets for the advanced persistent threat (APT). An APT is an adversary or adversarial group that possesses the expertise and resources that allow it to create opportunities to achieve its objectives by using multiple attack vectors, including cyber, physical, and deception."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 16}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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 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 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 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 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 additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 20)"}, {"role": "assistant", "content": "....................................................231 | |\n| E.2.1.\nGeneral Information.................................................................................................................232 | |\n| E.2.2. Baseline Risk Factors (Common, Minimal)...............................................................................234 | |\n| E.2.3. Risk Severity Schema................................................................................................................242 | |\n| E.2.4. Risk Response Guidance...........................................................................................................243 | |\n| E.3.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 19}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 14)"}, {"role": "assistant", "content": "ed security services provider (MSSP), talk to others in your industry to get their perspective on vendors they have worked with and always thoroughly review any contract or agreement prior to signing.\nA helpful resource, assembled by member company participants of the National Defense Information Sharing& Analysis Center (ND-ISAC), is the Defense Industrial Base Managed Service Provider Shopping Guide for Small & Medium-Sized Businesses. You may also explore the CyberAB Marketplace to find a consulting firm to assist in NIST 800-171 implementation.* |\n| Review NIST SP 800-171A to help you understandhow the security requirements in SP 800-171 can be self-assessed or are assessed by independent, third-party entities or by the | Review NIST SP 800-171A to help you understandhow the security requirements in SP 800-171 can be self-assessed or are assessed by independent, third-party entities or by the |\n\n* 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."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 13}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 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": "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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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 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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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 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 Level 3 require for Identification and Authentication?"}, {"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": "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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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 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 Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 19)"}, {"role": "assistant", "content": "_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\ndesigns) associated with a system. Mechanisms are the specific hardware, software, or firmware safeguards employed within a system.\nActivities are the protection-related actions supporting a system that involve people (e.g., conducting system backup operations, exercising a contingency plan, and monitoring network traffic). Individuals are people who apply the specifications, mechanisms, or activities described above. Assessment methods define the nature and extent of the assessor's actions. The methods include examine , interview , and test . The examine method is the process of reviewing, inspecting, observing, studying, or analyzing assessment objects (i.e., mechanisms, activities, specifications). The interview method is the process of holding discussions with individuals or groups of individuals to facilitate understanding, achieve clarification, or obtain evidence. The test method is the process of exercising assessment objects (i.e., activities, mechanisms) under specified conditions to compare actual with expected behavior. The purpose of the assessment methods is to facilitate understanding, achieve clarification, and obtain evidence. The results obtained from applying the methods are used for making the specific determinations called for in the determination statements and thereby achieving the objectives for the assessment procedure. The 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]."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 18}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 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 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 11)"}, {"role": "assistant", "content": "f 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.\nThe 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. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\nBelow is a sample CUI data flow diagram for a fictional company. Create your own diagram to understand how CUI flows into, within, and out of the business. \n\n## General Tips for Getting Started with NIST SP 800-171\n\n\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_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 Control Baselines for Information Systems and Organizations provide? (Part 17)"}, {"role": "assistant", "content": "| CONFIGURATIONMANAGEMENTFAMILY ................................................................................\n| 24 |\n| 3.6 | CONTINGENCYPLANNINGFAMILY .......................................................................................... | 26 |\n| 3.7 | IDENTIFICATIONANDAUTHENTICATIONFAMILY ...................................................................... | 28 |\n| 3.8 | INCIDENT RESPONSE FAMILY .................................................................................................. | 30 |\n| 3.9 | MAINTENANCEFAMILY .........................................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 16}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 Identification and Authentication?"}, {"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": "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 Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "0-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.\nAbstract\n\nThis publication provides a methodology and set of procedures for conducting assessments of\nsecurity and privacy controls employed within systems and organizations within an effective risk\nmanagement framework. 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. The 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. Keywords\n\nAssessment; assessment plan; assurance; control assessment; FISMA; Privacy Act; privacy\ncontrols; Open Security Controls Assessment Language; OSCAL; privacy requirements; Risk\nManagement Framework; security controls; security requirements. 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\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\nAcknowledgments\n\nThis publication was developed by the Joint Task Force Interagency Working Group. The group\nincludes representatives from the civil, defense, and intelligence communities."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.3.1 | Variaciones del algoritmo de confianza... 3.3.1). 3.3.1)."}], "metadata": {"source": "Zero Trust Architecture", "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 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": "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 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 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 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 15)"}, {"role": "assistant", "content": "nks 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.\nFurther, NIST does not endorse any commercial products that may be advertised or available on these sites. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Family: Access Control\n\nDescription: Limiting information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems) and to the types of transactions and functions that authorized users are permitted to exercise.*\n\n## Getting Started with Access Control\n\n\n\nImplement policies and procedures that limit access to CUI on systems and devices to only those individuals that require such access to do their jobs . Complete a review of publicly available information , such as information on the company website. - Review the content for CUI and remove such information if discovered. CUI should not be available to the public. ## Protect CUI with device locks and session termination . - Train staff on these behaviors and establish policies that prevent unauthorized individuals from seeing CUI or other sensitive information on a device while the device is unattended by an individual. When the individual returns to their device, they will have to re-establish access by using a password or biometric authenticator\n\nFoundational Concept -Least Privilege: This involves limiting access rights to only those users who need it to accomplish assigned tasks. - Identify who has access to CUI and the system. Only those who require access to CUI should have it. For example, if a network or system administrator does not need access to CUI, their access should be restricted. - Reassign or remove privileges as necessary, such as when an individual no longer requires access to CUI and the system."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 14}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 does CMMC Level 2 require for Media Protection?"}, {"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: maintenance policy and procedures; procedures for system maintenance tools; system maintenance tools; maintenance tool inspection records; equipment sanitization records; media sanitization records; system security plan; other relevant documents or records]\n\n[SELECT FROM: personnel with system maintenance responsibilities; personnel responsible for media sanitization; personnel with information security responsibilities]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "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 additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 14)"}, {"role": "assistant", "content": "scribed in a similar manner to those of Appendix F (Security Controls) and Appendix G (Information Security Programs Organization-Wide Information Security Program Management Controls). SP 800-53 Rev.\n4 reminds readers to view the privacy controls in Appendix J from the same perspective as the Program Management controls in Appendix G-that is, the controls are implemented for each organizational information system irrespective of the FIPS 199 categorization for that system. Appendix J defines controls, control enhancements, guidance, and references for the following new families:\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). The use of these standardized privacy controls will provide a more disciplined and structured approach for satisfying federal privacy requirements and demonstrating compliance with those requirements. Organizations should decide when to apply control enhancements to support their particular missions and business functions. Specific overlays for privacy can also be considered to facilitate the tailoring of the security control baselines in Appendix D with the requisite privacy controls to ensure that both security and privacy requirements can be satisfied by organizations."}], "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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 13}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 20)"}, {"role": "assistant", "content": "tems (including hardware, software, firmware, and documentation); and establishing and enforcing security configuration settings for information technology products employed in organizational systems.\n## Getting Started with Configuration Management\n\n\n\nChanges to a system can have potentially significant effects on the security of the system. Configuration management helps establish processes for initializing, changing and monitoring configurations to the hardware, software, or firmware components of the system or the operational procedures related to the system storing CUI. ## Limit who can make changes to the system containing CUI. - 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). ## Authorized software -allow by exception. - 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 . ## Locate CUI. - Identify the location of CUI and the system components on which the information is processed and stored. Identify who within the business has access to CUI. Again, remember to restrict this access to only those who need it. Foundational Concept -Least Functionality: Systems (databases, email systems, network drives, etc.) provide a variety of functions and services."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 19}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 12)"}, {"role": "assistant", "content": "d, 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_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 11}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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| 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 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.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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide?"}, {"role": "assistant", "content": "## Risk Management Framework for Information Systems and Organizations\n\nA 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. ## JOINT TASK FORCE\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-37r2\n\n\n\n## NIST Special Publication 800-37\n\nRevision 2\n\n## Risk Management Framework for Information Systems and Organizations\n\n## A System Life Cycle Approach for Security 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."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 are the CMMC Level 2 requirements?"}, {"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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 12)"}, {"role": "assistant", "content": "d, 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_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 11}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 11)"}, {"role": "assistant", "content": "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.\nLessons learned from incident response activities and root cause analysis help improve cybersecurity risk management and\n\ngovernance efforts and ensure that the organization is better prepared to identify its current technology assets and cybersecurity risks, protect its assets, and detect, respond to, and recover from future incidents. ## 1.1. Purpose and Scope\n\nThis publication seeks to help organizations incorporate cybersecurity incident response recommendations and considerations throughout their cybersecurity risk management activities. It also provides a common language that all organizations can use to communicate internally and externally regarding their incident response plans and activities. The scope of this publication differs significantly from previous versions. Because the details of how to perform incident response activities change so often and vary so much across technologies, environments, and organizations, it is no longer feasible to capture and maintain that information in a single static publication. Instead, this version focuses on improving cybersecurity risk management for all of the NIST Cybersecurity Framework (CSF) 2.0 Functions [CSF2.0] to better support an organization's incident response capabilities. Readers are encouraged to utilize other NIST resources in conjunction with this document, including the CSF 2.0 publication and supplemental resources, the Incident Response project page, and mappings to additional sources of information on implementing incident response considerations available through the NIST Cybersecurity and Privacy Reference Tool (CPRT). An example of a CPRT mapping is associating CSF 2.0 outcomes with NIST Special Publication (SP) 800-53 controls that can be implemented to help achieve the outcomes."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 20)"}, {"role": "assistant", "content": "rmine 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.\nTherefore, 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. The RMF is applied iteratively, as applicable, during the system development life cycle for any type of system development approach (including Agile and DevOps approaches). The security and privacy requirements and controls are implemented, verified, and validated as development progresses throughout the life cycle. This flexibility allows the RMF to support rapid technology cycles, innovation, and the use of current best practices in system and system component development. * 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. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## USE OF AUTOMATION IN THE EXECUTION OF THE RMF\n\nOrganizations should maximize the use of automation , wherever possible, to increase the speed, effectiveness, and efficiency of executing the steps in the Risk Management Framework (RMF)."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 19}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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": "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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 is CMMC practice AC.L2-3.1.9 (NIST 3.1.9)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.9. 3.1.9."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.9", "cmmc_practice_id": "AC.L2-3.1.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 additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 14)"}, {"role": "assistant", "content": "1. Enterprise infrastructure layer for uniform policy deployment.......................................... | Fig. 1. Enterprise infrastructure layer for uniform policy deployment.......................................... | 7 |\n| Fig. 2. Flexibility provided by multi-tier policies .........................................................................10 | Fig. 2. Flexibility provided by multi-tier policies .........................................................................10 | |\n| Fig. 3. Multi-tier Policies for a Hybrid Application Environment .................................................13 | Fig. 3. Multi-tier Policies for a Hybrid Application Environment .................................................13 | |\n| Fig. 4. An Istio Authorization Policy that allows Service 1 to Service 2 on port 443 but only allows it to execute the GET HTTP verb on the '/public' path........................................15 Fig. 5."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 13}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 17)"}, {"role": "assistant", "content": "nd consistent with law, regulations, and government-wide policies. 5 [EO 13556] designated the National Archives and Records Administration (NARA) as the Executive Agent to implement the CUI Program.\nCHAPTER ONE PAGE 1\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\ndescriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI, including but not limited to marking, safeguarding, transporting, disseminating, reusing, and disposing of the information. [EO 13556] also required that the CUI Program emphasize openness, transparency, and uniformity of government-wide practices, and that the implementation of the program take place in a manner consistent with applicable policies established by the Office of Management and Budget (OMB) and federal standards and guidelines issued by the National Institute of Standards and Technology (NIST). The federal CUI regulation , 6 developed by the CUI Executive Agent, provides guidance to federal agencies on the designation, safeguarding, dissemination, marking, decontrolling, and disposition of CUI; establishes self-inspection and oversight requirements; and delineates other facets of the program. In certain situations, CUI may be associated with a critical program 7 or a high value asset. 8 These critical programs and high value assets are potential targets for the advanced persistent threat (APT). An APT is an adversary or adversarial group that possesses the expertise and resources that allow it to create opportunities to achieve its objectives by using multiple attack vectors, including cyber, physical, and deception."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 16}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 16)"}, {"role": "assistant", "content": "administrator does not need access to CUI, their access should be restricted. - Reassign or remove privileges as necessary, such as when an individual no longer requires access to CUI and the system.\n- Identify who within the business has administrative (i.e., system administrator or domain administrator) privileges on systems and devices. Limit administrative privileges to only those who need them to perform specified tasks. Implement policies that restrict use of these accounts for routine, day-to-day tasks that do not require administrative privileges. ## Related Resources:\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n*Family definitions, except for 'Supply Chain Risk Management,' are adapted from FIPS 200 , Minimum Security Requirements for Federal Information and Information Systems. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Getting Started with Access Control\n\n\n\n## Getting Started with Awareness and Training\n\n## Family: Awareness and Training\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. ## Getting Started with Awareness and Training\n\n\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."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 15}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 19)"}, {"role": "assistant", "content": "traditional Information Technology (IT) systems, Operational Technology (OT) systems, Internet of Things\n\n6 [32 CFR 2002] was issued on September 14, 2016, and went into effect on November 14, 2016.\n7 The definition of a critical program may vary from organization to organization. For example, the Department of Defense defines a critical program as a program which significantly increases capabilities and mission effectiveness or extends the expected effective life of an essential system/capability [DOD ACQ]. 8 See [OMB M-19-03] and [OCIO HVA]. CHAPTER ONE PAGE 2\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n(IoT) systems, and Industrial IoT (IIoT) systems. The convergence of these types of systems has brought forth a new class of systems known as cyber-physical systems , many of which are in sectors of U.S. critical infrastructure, including energy, transportation, defense, manufacturing, healthcare, finance, and information and communications. Therefore, CUI that is processed, stored, or transmitted by any of the above systems related to a critical program or high value asset requires additional protection from 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 18}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 12)"}, {"role": "assistant", "content": "8 (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. ## 8 Overlays\n\nTo help ensure that selected and implemented controls are sufficient to adequately mitigate risks to organizational operations and assets, SP 800-53 Rev. 4 introduces the concept of overlays. An overlay provides a set of security controls, control enhancements, and supplemental guidance for community-wide use or to address specialized requirements, technologies, or unique missions and environments of operation. For example, the federal government may decide to establish a government-wide set of security controls and implementation guidance for public key infrastructure (PKI) systems that could be uniformly applied to information systems. Multiple overlays can be applied to a single security control baseline. The tailored baselines that result from the overlay development process may be more or less stringent than the original security control baselines. Risk assessments provide information necessary to determine if the risk from implementing the tailored baselines falls within the risk tolerance of the organizations or communities of interest developing the overlays. General guidance on overlays is provided in section 3.3 and an overlay template is provided in Appendix I."}], "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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 11}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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 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 additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 17)"}, {"role": "assistant", "content": "ppendices provide additional assessment-related information, including general References , a Glossary , a list of Acronyms , and a description of the Assessment Methods used in assessment procedures.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## CHAPTER TWO\n\n## THE FUNDAMENTALS\n\nBASIC CONCEPTS FOR ASSESSMENTS OF CUI ENHANCED SECURITY REQUIREMENTS\n\nhe CUI enhanced security requirements in [SP 800-172] are organized into 10 families, as illustrated in Table 1. 5 The process to assess the CUI enhanced security requirements includes preparing for assessment, developing assessment plans, conducting assessments, and analyzing results. 6 The assessment procedures in Chapter Three are grouped by family designations to help ensure the completeness and consistency of assessments. T\n\n## TABLE 1: CUI ENHANCED SECURITY REQUIREMENT FAMILIES\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## 2.1 ASSESSMENT PROCEDURES\n\nAn assessment procedure consists of an assessment objective and a set of potential assessment methods and objects that can be used to conduct the assessment."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 16}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 15)"}, {"role": "assistant", "content": "Revision 5. The addition of the Prepare step is one of the key changes to the RMF-incorporated to achieve more effective, efficient, and cost-effective security and privacy risk management processes.\nThe primary objectives for institutionalizing organization-level and system-level preparation are:\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n- To facilitate effective communication between senior leaders and executives at the organization and mission/business process levels and system owners at the operational level;\n- To facilitate organization-wide identification of common controls and the development of organizationally-tailored control baselines, reducing the workload on individual system owners and the cost of system development and asset protection;\n- To reduce the complexity of the information technology (IT) and operations technology (OT) infrastructure using Enterprise Architecture concepts and models to consolidate, optimize, and standardize organizational systems, applications, and services;\n- To reduce the complexity of systems by eliminating unnecessary functions and security and privacy capabilities that do not address security and privacy risk; and\n- To identify, prioritize, and focus resources on the organization's high value assets (HVA) that require increased levels of protection-taking measures commensurate with the risk to such assets. By achieving the above objectives, organizations can simplify RMF execution, employ innovative approaches for managing risk, and increase the level of automation when carrying out specific tasks."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 14}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 11)"}, {"role": "assistant", "content": "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.\nSecurity Requirement Families\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\nAn assessment procedure consists of an assessment objective and a set of potential assessment methods and objects that can be used to conduct the assessment. Each potential assessment objective includes a determination statement related to the security requirement. If there is an organization-defined parameter (ODP) in the security requirement, then the assessment objective begins with a determination statement related to the definition of the ODP. The determination statements are linked to the content of the security requirements to help ensure traceability of the assessment results to the requirements. Assessment objects identify the specific items being assessed and can include specifications, mechanisms, activities, and individuals. Specifications are the documented artifacts 3 (e.g., plans, policies, procedures, requirements, functional and assurance specifications, design documentation, and architectures) associated with a system. Mechanisms are the hardware, software, and firmware safeguards implemented within a system."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n| 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": "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.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 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 additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 20)"}, {"role": "assistant", "content": "eguards or\ncountermeasures prescribed for a system or an organization to protect the confidentiality,\nintegrity, and availability of its system and information and to manage information security risk.\nPrivacy controls are the administrative, technical, and physical safeguards employed within a\nsystem or an organization to manage privacy risks and ensure compliance with applicable\nprivacy requirements.3\n\nOnce employed within a system, security and privacy controls are assessed to determine their\noverall effectiveness (i.e., the extent to which the controls are implemented correctly, operating\nas intended, and producing the desired outcome with respect to meeting the security and\nprivacy requirements for the system and the organization). Understanding the overall\neffectiveness of implemented security and privacy controls is essential in determining the risk to\nthe organization’s operations and assets, individuals, other organizations, and the Nation\nresulting from the use of the system. 1.1 PURPOSE AND APPLICABILITY\n\nThe purpose of this publication is to provide guidelines for building effective security and\nprivacy assessment plans, as well as a comprehensive set of procedures for assessing the\neffectiveness of security and privacy controls employed in systems and organizations. The\nguidelines apply to the security and privacy controls defined in [SP 800-53] (as amended),\nSecurity and Privacy Controls for Information Systems and Organizations."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 19}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 13)"}, {"role": "assistant", "content": "| TARGET AUDIENCE ..................................................................................................................\n| 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ......................................................................................... | 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 12}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 11)"}, {"role": "assistant", "content": "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.\nI\n\nNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nCOMMON SECURITY AND PRIVACY FOUNDATIONS\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."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\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.\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.\n\nFederal agencies are required to ensure that privacy protections are incorporated into information security planning. To that end, SP 800-53 Rev. 4 features eight new families of privacy controls that are based on the internationally accepted Fair Information Practice Principles (FIPPs). The proliferation of social media, Smart Grid, mobile, and cloud computing, as well as the transition from structured to unstructured data and metadata environments, have added significant complexities and challenges for federal organizations in safeguarding privacy. These challenges extend well beyond the traditional information technology security view of protecting privacy, which focused primarily on ensuring confidentiality."}], "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": "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 13)"}, {"role": "assistant", "content": "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.\nA system security plan documents how an organization meets or plans to meet the security requirements for a system. In particular, the system security plan describes the system boundary, the environment in which the system operates, how the security requirements are satisfied, and the relationships with, or connections to, other systems. View sample templates for system security plans on the Defense Industrial Base Sector Coordinating Council website. |\n| Create a plan of action and milestones (POAM). | Once you have completed your audit or security assessment, describe how unsatisfied security requirements will be met and how planned mitigations will be implemented. Organizations can create system security plans and POAMs as separate or combined documents in any format. Federal agencies may consider system security plans and POAMs as inputs to risk-based decisions on whether to process, store, or transmit CUI on a system hosted by a nonfederal organization. View an editable template. |\n| Find help when you need it. | Consider reaching out to a local Manufacturing Extension Partnership or APEX Accelerator to help you get started. Regularly communicate with your prime contractor or contract officer to understand contract requirements. Decide if you need to increase the skills of your existing staff, hire new people, or engage an external partner to help you. If hiring an external partner, such as a managed security services provider (MSSP), talk to others in your industry to get their perspective on vendors they have worked with and always thoroughly review any contract or agreement prior to signing."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 12}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 17)"}, {"role": "assistant", "content": "lity principle; and\n- -Make the transition to ongoing authorization a priority and use continuous monitoring approaches to reduce the cost and increase the efficiency of security and privacy programs.\nRecognizing that the preparation for RMF execution may vary from organization to organization, achieving the above objectives can reduce the overall IT/OT footprint and attack surface of\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\norganizations, promote IT modernization objectives, conserve resources, prioritize security activities to focus protection strategies on the most critical assets and systems, and promote privacy protections for individuals. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## COMMON SECURITY AND PRIVACY RISK FOUNDATIONS\n\nIn developing standards and guidelines, NIST consults with federal agencies, state, local, and tribal governments, and private sector organizations; avoids unnecessary and costly duplication of effort; and ensures that its publications are complementary with the standards and guidelines used for the protection of national security systems. In addition to implementing a transparent public review process for its publications, NIST collaborates with the Office of Management and Budget, the Office of the Director of National Intelligence, the Department of Defense, and the Committee on National Security Systems, and has established a unified risk management framework for the federal government."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 16}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 19)"}, {"role": "assistant", "content": "tect audit record content. - Ask internal information security staff, or your security vendor, what audit log information, if any, the system currently captures and how it is protected and maintained.\n## Questions to Ask:\n\n- Do audit records contain information that establishes type of event, when the event occurred, where the event occurred, the source of the event, outcome, and the identity of the individual associated with the event? - Who within the business should be alerted when there are, for instance, software and hardware errors, failures in audit log capturing mechanisms, or reaching or exceeding audit log storage capacity? - Are we retaining audit records for a period consistent with the business records retention policy? Note that some industries and types of data (e.g., financial, employee, and medical records) have regulatory specifications. - How are audit information and audit logging tools being protected from unauthorized access, modification, and deletion? - Is access to management of audit logging functionality authorized to only a subset of privileged users or roles? - How frequently are these records reviewed? ## Related Resources:\n\n- View all SP 800-171 Audit and Accountability Requirements and Assessment Procedures\n- NIST Log Management resources\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n- Logging Made Easy, Cybersecurity and Infrastructure Security Agency (CISA)\n\n## Getting Started with Configuration Management\n\n## Family: Configuration Management\n\nDescription: Establishing and maintaining baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation); and establishing and enforcing security configuration settings for information technology products employed in organizational systems."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 18}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 does CMMC require for Security Assessment?"}, {"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": "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 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 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 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 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 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 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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 13)"}, {"role": "assistant", "content": "| ........................................................................................................\n22 |\n| 3.13 SYSTEMANDCOMMUNICATIONSPROTECTION ..................................................................... | 23 |\n| 3.14 SYSTEMANDINFORMATIONINTEGRITY ................................................................................ | 27 |\n| REFERENCES .................................................................................................................................. 32 | REFERENCES .................................................................................................................................. 32 |\n| APPENDIXA GLOSSARY................................................................................................................ 38 | APPENDIXA GLOSSARY................................................................................................................ 38 |\n| APPENDIX B ACRONYMS.............................................................................................................. 48 | APPENDIX B ACRONYMS.............................................................................................................. 48 |\n| APPENDIX C MAPPINGTABLES .................................................................................................... 50 | APPENDIX C MAPPINGTABLES ...................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 12}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 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": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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 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 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 additional guidance does Zero Trust Architecture provide? (Part 11)"}, {"role": "assistant", "content": "| | | 5.2 | DENEGACIÓN DE SERVICIOO ALTERACIÓN DE LA RED ..............................................................................................41 | | | 5.3 | ROBO DE CREDENCIALES Y AMENAZA DE INFILTRACIÓN ...........................................................................................42 | | | 5.4 | VISIBILIDAD EN LA RED .....................................................................................................................................43 | | | 5.5 | ALMACENAMIENTO DE LA INFORMACIÓN DEL SISTEMA Y DE LA RED ...........................................................................43 | | | 5.6 | CONFIANZA EN LOS FORMATOS O EN LAS SOLUCIONES DE DATOS PATENTADOS ............................................................43 | | | 5.7 | USO DE ENTIDADES NO PERSONALES (NPE, POR SU NOMBRE EN INGLÉS NON- PERSON ENTITIES ) EN LA ADMINISTRACIÓN DE | LA | | 6 ARQUITECTURA DE CONFIANZA CERO Y POSIBLES INTERACCIONES CONLAS NORMASFEDERALES | 6 ARQUITECTURA DE CONFIANZA CERO Y POSIBLES INTERACCIONES CONLAS NORMASFEDERALES | | | EXISTENTES...................................................................................................................................................................45 | EXISTENTES...................................................................................................................................................................45 | | | | | NIST..............................................................................................45 | | 6.1 6.2 | ZTA Y EL MARCO DE GESTIÓN DE RIESGOSDE CONFIANZA CERO Y MARCODE PRIVACIDAD DE NIST............................................................................................45 | | | 6.3 | ZTA Y LA ARQUITECTURA F EDERAL DE LA GESTIÓN DE I DENTIDADES , CREDENCIALES Y ACCESOS .....................................46 | | | 6.4 | ZTA Y LA CONEXIÓN A I NTERNET DE CONFIANZA 3.0..............................................................................................46 | | | 6.5 | ZTA Y E INSTEIN (S ISTEMA DE PROTECCIÓN"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 11)"}, {"role": "assistant", "content": "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.\nThey complement the security controls in Appendix F and focus on the programmatic, organization-wide information security requirements that are independent of any particular information system and are essential for managing information security programs. Tailoring guidance can be applied to the program management controls in a manner similar to how the guidance is applied to security controls in Appendix F. ## 7 International Information Security Standards\n\nMany 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_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 11)"}, {"role": "assistant", "content": "..................................................... 11 | CHAPTER THREE THE REQUIREMENTS.........................................................................................\n11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ................................................................................................... 13 |\n| 3.3 AUDIT ANDACCOUNTABILITY | ................................................................................................. 14 |\n| 3.4 CONFIGURATIONMANAGEMENT | ........................................................................................... 14 |\n| 3.5 IDENTIFICATIONANDAUTHENTICATION | ................................................................................. 16 |\n| 3.6 INCIDENT RESPONSE | .............................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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 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 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 Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 14)"}, {"role": "assistant", "content": "by the Defense Science Board, the Executive Order, and the OMB policy memorandum to develop the nextgeneration Risk Management Framework (RMF) for information systems, organizations, and individuals.\nThere are seven major objectives for this update:\n\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. The addition of the Prepare step is one of the key changes to the RMF-incorporated to achieve more effective, efficient, and cost-effective security and privacy risk management processes."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 13}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 11)"}, {"role": "assistant", "content": "ment 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.\nA 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). 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\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\nASSESSMENT PROCEDURE FORMATTING\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."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 10}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 19)"}, {"role": "assistant", "content": "an abstract definition of zero trust architecture and gives general deployment models and use cases with which zero trust could improve an enterprise's overall information technology security posture.\n## Relationship to Other NIST Guidance Documents\n\nSince the current document provides guidance for the realization of ZTA for cloud-native applications hosted in multiple locations (on-premises and multiple clouds) and the enforcement of ZT principles requires policies that are associated with various security services, it will be useful to refer to the following documents. These documents provide background information for the architecture of a microservices-based application with service mesh as well as guidance for configuring specific security services. The current document expands the reference environment to one in which the Information Technology (IT) application infrastructure of an enterprise spans multiple premises and multiple cloud provider locations as well as addresses the range of policies that is required for comprehensive security assurance. - SP 800-204A, Building Secure Microservices-Based Applications Using Service Mesh Architecture [2], provides deployment guidance for various security services (e.g., establishment of secure sessions, security monitoring) for a microservices-based application using a dedicated infrastructure (i.e., a service mesh) based on service proxies that operate independently of the application code. - SP 800-204B, Attribute-Based Access Control for Microservices-Based Applications Using a Service Mesh [3], provides deployment guidance for building an authentication and authorization framework within the service mesh that meets the security requirements."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 18}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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.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 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 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 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\niving 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.\nCommon controls may differ based upon a variety of factors, such as hosting location, system architecture, and the structure of the organization. The organization-wide list of common controls takes these factors into account. Common controls can also be identified at different levels of the organization (e.g., corporate, department, or agency level; bureau or subcomponent level; or individual program level). Organizations may establish one or more lists of common controls that can be inherited by information systems. A requirement may not be fully met by a common control. In such cases, the control is considered a hybrid control and is noted as such by the organization, including specifying which parts of the control requirement are provided for inheritance by the common control and which parts are to be provided at the system level."}], "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 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 are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n## 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 14)"}, {"role": "assistant", "content": "scribed in a similar manner to those of Appendix F (Security Controls) and Appendix G (Information Security Programs Organization-Wide Information Security Program Management Controls). SP 800-53 Rev.\n4 reminds readers to view the privacy controls in Appendix J from the same perspective as the Program Management controls in Appendix G-that is, the controls are implemented for each organizational information system irrespective of the FIPS 199 categorization for that system. Appendix J defines controls, control enhancements, guidance, and references for the following new families:\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). The use of these standardized privacy controls will provide a more disciplined and structured approach for satisfying federal privacy requirements and demonstrating compliance with those requirements. Organizations should decide when to apply control enhancements to support their particular missions and business functions. Specific overlays for privacy can also be considered to facilitate the tailoring of the security control baselines in Appendix D with the requisite privacy controls to ensure that both security and privacy requirements can be satisfied by organizations."}], "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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 13}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 13)"}, {"role": "assistant", "content": "lar A-130, Managing Information as a Strategic Resource [OMB A-130], addresses responsibilities for protecting federal information resources and for managing personally identifiable information (PII).\nCircular A-130 requires agencies to implement the RMF that is described in this guideline and requires agencies to integrate privacy into the RMF process. In establishing requirements for information security programs and privacy programs, the OMB circular emphasizes the need for both programs to collaborate on shared objectives:\n\n'While security and privacy are independent and separate disciplines, they are closely related, and it is essential for agencies to take a coordinated approach to identifying and managing security and privacy risks and complying with applicable requirements….'\n\nThis update to NIST Special Publication 800-37 (Revision 2) responds to the call by the Defense Science Board, the Executive Order, and the OMB policy memorandum to develop the nextgeneration Risk Management Framework (RMF) for information systems, organizations, and individuals."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 12}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 18)"}, {"role": "assistant", "content": "adversarial group that possesses the expertise and resources that allow it to create opportunities to achieve its objectives by using multiple attack vectors, including cyber, physical, and deception.\nThe APT objectives include establishing a foothold within the infrastructure of targeted organizations for purposes of exfiltrating information; undermining or impeding critical aspects of a mission, function, program, or organization; or positioning itself to carry out these objectives in the future. The APT pursues its objectives repeatedly over an extended period, adapts to defenders' efforts to resist it, and is determined to maintain the level of interaction needed to execute its objectives. While the category of CUI itself does not require greater protection, CUI associated with critical programs or high value assets is at greater risk because the APT is more likely to target such information and therefore requires additional protection. ## CUI ENHANCED SECURITY REQUIREMENTS\n\nControlled Unclassified Information has the same value , whether such information is resident in a federal system that belongs to a federal agency or a nonfederal system that belongs to a nonfederal organization. Accordingly, the enhanced security requirements in this publication are consistent with and complementary to the guidelines used by federal agencies to protect CUI. The 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 APT is extremely dangerous to the national and economic security interests of the United States since organizations are very dependent on systems of all types, including traditional Information Technology (IT) systems, Operational Technology (OT) systems, Internet of Things\n\n6 [32 CFR 2002] was issued on September 14, 2016, and went into effect on November 14, 2016."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 17}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 18)"}, {"role": "assistant", "content": ".............................................................. 372\n4.14 PERSONNEL SECURITY ...........................................................................................................\n401\n4.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ................... 412\n4.16 RISK ASSESSMENT ................................................................................................................. 426\n4.17 SYSTEM AND SERVICES ACQUISITION ....................................................................................... 441\n4.18 SYSTEM AND COMMUNICATIONS PROTECTION ...................................................................... 522\n4.19 SYSTEM AND INFORMATION INTEGRITY ................................................................................... 599\n4.20 SUPPLY CHAIN RISK MANAGEMENT .......................................................................................... 665\nREFERENCES ........................................................................................................................................ 684\nAPPENDIX A GLOSSARY ....................................................................................................................... 689\nAPPENDIX B ACRONYMS ..................................................................................................................... 705\nAPPENDIX C ASSESSMENT METHOD DESCRIPTIONS........................................................................... 707\nAPPENDIX D PENETRATION TESTING .................................................................................................. 715\nAPPENDIX E ASSESSMENT REPORTS ................................................................................................... 718\nAPPENDIX F ONGOING ASSESSMENT AND AUTOMATION ................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 17}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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": "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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "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 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 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 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 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": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "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 does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nEach segment is protected by gateway devices, such as intelligent switches and routers or nextgeneration firewalls, that should have the capacity to react and adapt in response to the threats and changes in the application workflows. Segmentation gateways monitor traffic, stop threats, and enforce granular access across east-west traffic (rarely for north-south traffic) within onpremises data centers or cloud regions. The main difficulty with this approach is in mapping the applications' security requirements-based segments to corresponding network segments. Another difficulty is change management. The mapping between applications and network identities that are being statically maintained has to be kept in sync with the operational scenario in which the application's network locations are continuously changing due to performance and security."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "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| 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 additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 13)"}, {"role": "assistant", "content": "s document that are not yet published in an errata update or revision-including additional issues and potential corrections-will be posted as they are identified (see SP 800-172A publication details).\n| DATE | TYPE | CHANGE | PAGE |\n|--------|--------|----------|--------|\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## CHAPTER ONE\n\n## INTRODUCTION\n\nTHE NEED TO ASSESS ENHANCED SECURITY REQUIREMENTS FOR CUI\n\nn 2010, Executive Order 13556 established a government-wide Controlled Unclassified Information (CUI) Program to standardize the way that the executive branch handles unclassified information that requires protection. The regulation that implements the CUI Program is 32 CFR part 2002. Only federal information that requires safeguarding or dissemination controls pursuant to federal law, regulation, or government-wide policy may be designated as CUI. 1 NIST Special Publication (SP) 800-172, a supplement to NIST SP 800-171, specifies enhanced security requirements to ensure the confidentiality, integrity, and availability of CUI when it is associated with a high value asset or a critical program. 2 I\n\n## 1.1 PURPOSE AND APPLICABILITY\n\nThe 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. The assessment procedures are typically used as part of an assessment process."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 12}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense 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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 15)"}, {"role": "assistant", "content": "oday, more than at any time in history, the Federal Government relies on external service providers to help carry out a wide range of federal missions and business functions using information systems.\n1 Many federal contractors, for example, routinely process, store, and transmit sensitive federal information in their systems to support the delivery of essential products and services to federal agencies (e.g., financial services, providing web and electronic mail services, processing security clearances or healthcare data, providing cloud services, and developing communications, satellite, and weapons systems). Federal information is frequently provided to or shared with entities such as state and local governments, colleges and universities, and independent research organizations. The protection of sensitive federal information while residing in nonfederal systems 2 and organizations is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to carry out its designated missions and business operations. T\n\nThe protection of unclassified federal information in nonfederal systems and organizations is dependent on the Federal Government providing a process for identifying the different types of information that are used by federal agencies. [EO 13556] established a government-wide Controlled Unclassified Information (CUI) 3 Program 4 to standardize the way that the executive branch handles unclassified information that requires protection. 5 Only information that requires safeguarding or dissemination controls pursuant to federal law, regulation, or government-wide policy may be designated as CUI. The CUI Program is designed to address several deficiencies in managing and protecting unclassified information, including inconsistent markings, inadequate safeguarding, and needless restrictions, both by standardizing procedures and by providing common definitions through a CUI Registry [NARA CUI]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Risk Assessment", "Maintenance", "Access Control", "System and Communications Protection", "System and Information Integrity", "Incident Response", "Physical Protection", "Identification and Authentication", "Planning", "System and Services Acquisition", "Media Protection", "Awareness and Training", "Audit and Accountability", "Supply Chain Risk Management", "Configuration Management", "Personnel Security", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 14}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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"}}