{"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 require for Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 17)"}, {"role": "assistant", "content": "team oversees incident response, allocates funding, and may have decision-making authority on high-impact response actions, such as shutting down or rebuilding critical services. - Incident handlers.\nIncident handlers verify that an incident has occurred, collect and analyze data and evidence, prioritize incident response activities, and act appropriately to limit damage, find root causes, and restore operations. Incident handlers also often provide input to others on mitigating cybersecurity issues and improving resiliency. An organization's incident handlers might be:\n- o On staff (e.g., an incident response team),\n- o On contract (e.g., outsourcing a security operations center [SOC] to a managed security services provider [MSSP] or leveraging a cloud service provider's incident response team when an incident occurs within that provider's cloud), and/or\n- o Available when needed (e.g., from a parent organization, a cybersecurity services provider, a business partner, or a law enforcement agency). Many organizations may use more than one of these approaches, such as internally performing basic incident response and engaging third-party resources for assistance with certain incidents. Larger organizations may have multiple incident response teams, with each team responsible for a particular logical or physical segment of the organization. When this model is employed, the teams should be part of a single coordinated entity (e.g., a federation) to ensure that incident response processes, procedures, and training are consistent across the organization and that information is shared among teams. - Technology professionals. Cybersecurity, privacy, system, network, cloud, and other technology architects, engineers, and administrators, as well as software developers, may be involved in incident response and recovery efforts. - Legal."}], "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": 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 does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Access Control\n\n## Getting Started with Access Control"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 7)"}, {"role": "assistant", "content": "itado que los titulares de registros de patentes cuyo uso pueda ser necesario para el cumplimiento de las orientaciones o requisitos de esta publicación comuniquen dichos registros de patentes al ITL.\nSin embargo, los titulares de patentes no están obligados a responder a las solicitudes de patentes del ITL y el ITL no ha realizado una búsqueda de patentes para identificar cuáles, si las hubiera, pueden aplicarse a esta publicación. Tras la convocatoria del ITL para la identificación de reclamaciones de patentes cuyo uso pueda ser necesario para el cumplimiento de las orientaciones o requisitos de esta publicación, se ha recibido notificaciones de una o más de dichas reclamaciones. Mediante la publicación, el ITL no adopta posición alguna con respecto a la validez o el alcance de cualquier reivindicación de patente o de cualquier derecho relacionado con ella. No obstante, el o los titulares conocidos de patentes han facilitado a NIST una carta de garantía en la que declaran o bien (1) una renuncia general en el sentido de que no poseen y no tienen actualmente la intención de poseer ninguna reivindicación esencial de patente, o bien (2) que negociarán licencias libres de cánones o que devenguen cánones con otras partes sobre una base no discriminatoria demostrable con términos y condiciones razonables. Para más detalles se puede consultar en zerotrust-arch@nist.gov . No se declara ni se da a entender que esta sea la única licencia necesaria para evitar la infracción de patentes en el uso de esta publicación."}], "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": 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 Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.\nParameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Assessing Security Requirements for Controlled Unclassified Information provide? (Part 7)"}, {"role": "assistant", "content": "...103 |\n| Appendix D. Organization-Defined Parameters...............................................................................107 |\n| Appendix E.\nChange Log .................................................................................................................112 |\n\n## List of Tables\n\n| Table 1. Security Requirement Families ..............................................................................................3 |\n|------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Summary of Assessment Preparation Phase.......................................................................104 |\n| Table 3. Summary of Assessment Plan Development Phase.............................................................105 |\n| Table 4. Summary of Assessment Execution Phase..........................................................................106 |\n| Table 5. Summary of Assessment Analysis, Documentation, and Reporting Phase ...........................106 |\n| Table 6. Organization-Defined Parameters......................................................................................107 |\n\nTable 7. Change Log ....................................................................................................................... 113\n\n## Acknowledgments\n\nThe authors gratefully acknowledge and appreciate the significant contributions from individuals and organizations in the public and private sectors whose constructive comments improved the overall quality, thoroughness, and usefulness of this publication."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 14)"}, {"role": "assistant", "content": "..................................................... 50 | APPENDIX C MAPPINGTABLES ....................................................................................................\n50 |\n| APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 | APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 |\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Errata\n\nThis table contains changes that have been incorporated into Special Publication 800-172. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. Any potential updates for this 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 the SP 800-172 publication details. | DATE | TYPE | CHANGE | PAGE |\n|--------|--------|----------|--------|\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## CHAPTER ONE\n\n## INTRODUCTION\n\nTHE NEED TO PROTECT CONTROLLED UNCLASSIFIED INFORMATION\n\noday, 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."}], "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": 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 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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 3)"}, {"role": "assistant", "content": "| help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n## Audience\n\n\n\n\n\nPages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality\n\n\n\nConfidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 \"Controlled Unclassified Information.\"\n\n## A Suite of Guidance\n\nNIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . \n\n\n\n\n\nNIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nIn working with the Office of Management and Budget to develop standards and guidelines\nrequired by FISMA, NIST consults with federal agencies, state, local, and tribal governments, and\nprivate sector organizations to improve information security and privacy, avoid unnecessary and\ncostly duplication of effort, and help ensure that its publications are complementary with the\nstandards and guidelines used for the protection of national security systems. In addition to a\ncomprehensive and transparent public review and comment process, NIST is engaged in a\ncollaborative partnership with the Office of Management and Budget, Office of the Director of\nNational Intelligence, Department of Defense, Committee on National Security Systems, Federal\nCIO Council, and Federal Privacy Council to establish a Risk Management Framework (RMF) for\ninformation security and privacy for the Federal Government. This common foundation provides\nthe Federal Government and their contractors with cost-effective, flexible, and consistent ways\nto manage security and privacy risks to organizational operations and assets, individuals, other\norganizations, and the Nation. The framework provides a basis for the reciprocal acceptance of\nsecurity and privacy control assessment evidence and authorization decisions and facilitates\ninformation sharing and collaboration. NIST continues to work with public and private sector\nentities to establish mappings and relationships between the standards and guidelines\ndeveloped by NIST and those developed by other organizations. NIST anticipates using these\nmappings and the gaps they identify to improve the control catalog. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ..................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\ns of computing platforms, including\ngeneral purpose computing systems, cyber-physical systems, cloud systems, mobile systems,\nindustrial control systems, and Internet of Things (IoT) devices.\nSafeguarding measures include\nboth security and privacy controls to protect the critical and essential operations and assets of\norganizations and the privacy of individuals. The objective is to make the systems we depend on\nmore penetration resistant to attacks, limit the damage from those attacks when they occur,\nand make the systems resilient, survivable, and protective of individuals’ privacy."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nne or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control.\n- Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nIn addition to the responsibility to protect organizational assets from the threats that exist in today's environment, organizations have a responsibility to consider and manage the risks to individuals when information systems process personally identifiable information (PII). 6 7 The information security and privacy programs implemented by organizations have complementary objectives with respect to managing the confidentiality, integrity, and availability of PII. While many privacy risks arise from unauthorized activities that lead to the loss of confidentiality, integrity, or availability of PII, other privacy risks result from authorized activities involving the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, or disposal of PII that enables an organization to meet its mission or business objectives. For example, organizations could fail to provide appropriate notice of PII processing depriving an individual of knowledge of such processing or an individual could be embarrassed or stigmatized\n\nExecuting the RMF requires close collaboration between information security programs and privacy programs. While information security programs and privacy programs have different objectives, those objectives are overlapping and complementary. Information security programs are responsible for protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction (i.e., unauthorized system activity or behavior) in order to provide confidentiality, integrity, and availability. Privacy programs are responsible for ensuring compliance with applicable privacy requirements and for managing the risks to individuals associated with the creation, collection, use, processing, dissemination, storage, maintenance, disclosure, or disposal (collectively referred to as 'processing') of PII."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 20)"}, {"role": "assistant", "content": "TS\n\nSP 800-171A [84] provides a set of procedures to assess the security requirements described in this publication. The assessment procedures are based on the procedures described in SP 800-53A [57].\n15 With few exceptions, the security controls in SP 800-53 are policy-, technology-, and sector-neutral, meaning that the controls focus on the fundamental measures necessary to protect information across the information life cycle. ## 3. The Security Requirements\n\nThis section describes 17 families of security requirements for protecting the confidentiality of CUI in nonfederal systems and organizations. When used in the context of the requirements in Sec. 3, the term system is defined to be nonfederal systems or system components that process, store, or transmit CUI or that provide protection for such systems or components. Not all security requirements mention CUI explicitly. However, the requirements are included because they directly affect the protection of CUI during processing, while in storage, and when in transmission between different locations. Some systems, including specialized systems (e.g., industrial/process control systems, medical devices, computer numerical control machines), may have limitations on the application of certain security requirements. To accommodate such issues, the system security plan - as reflected in requirement 03.15.02 - is used to describe any enduring exceptions to the security requirements. Individual, isolated, or temporary deficiencies are managed though plans of action and milestones, as reflected in requirement 03.12.02. ## SCOPE AND APPLICABILITY OF SECURITY REQUIREMENTS\n\nThe security requirements in this section are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. ## 3.1. Access Control\n\n## 03.01.01 Account Management\n\n- a. Define the types of system accounts allowed and prohibited. - b."}], "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": 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 System and Information Integrity?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n....................................................................................... | 63 |\n| A.1.1.\nC-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 additional guidance does Zero Trust Architecture provide? (Part 10)"}, {"role": "assistant", "content": "| Implementación basada en enclaves....................................................................................................26 | | | 3.2.3 | Despliegue basado en un portal de recursos........................................................................................27 | | | 3.2.4 | Entorno de pruebas (sandbox) para aplicaciones en dispositivos........................................................28 | | | 3.3 | ALGORITMOS DE CONFIANZA .............................................................................................................................29 | | | 3.3.1 | Variaciones del algoritmo de confianza................................................................................................31 | | | 3.4 | COMPONENTES DE LA RED Y EL ENTORNO ............................................................................................................33 | | | 3.4.1 | Requisitos de la red para admitir una ZTA............................................................................................33 | | | ESCENARIOS DE IMPLEMENTACIÓN Y CASOS DE USO......................................................................................35 | ESCENARIOS DE IMPLEMENTACIÓN Y CASOS DE USO......................................................................................35 | | | 4.1 | E MPRESA CON INSTALACIONES SATÉLITES .............................................................................................................35 | | | 4.2 | E MPRESA MULTINUBE O NUBE A NUBE ................................................................................................................36 | | | 4.3 | E MPRESA CON SERVICIOS CONTRATADOS O ACCESO DE PERSONAL EXTERNO ................................................................37 | | | 4.4 | COLABORACIÓN MÁS ALLÁ DE LOS LÍMITES DE LA EMPRESA ......................................................................................39 | | | 4.5 | E MPRESA CON SERVICIOS ORIENTADOS AL PÚBLICO O AL CLIENTE ..............................................................................40 | | | 5 AMENAZAS ASOCIADAS A LA ARQUITECTURA DE CONFIANZA CERO..............................................................41 | 5 AMENAZAS ASOCIADAS A LA ARQUITECTURA DE CONFIANZA CERO..............................................................41 | | | 5.1 | S UBVERSIÓN DEL PROCESO DE DECISIONES DE LA ZTA............................................................................................41"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["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 does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The NIST Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, implementations, proofs of concept, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. The purpose of this publication is to describe procedures for assessing the enhanced security requirements in [SP 800-172]. 3 Compliance with the security requirements is addressed in CUI guidance and the CUI Federal Acquisition Regulation (FAR) or as supplemented by federal agencies (e.g., Department of Defense Federal Acquisition Regulation). Organizations can use the assessment procedures to generate evidence to support the assertion that the enhanced security requirements have been satisfied."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 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 Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 6)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## CAUTIONARY NOTE\n\nThe generalized assessment procedures described in this publication provide a framework and starting point for developing specific procedures to assess the enhanced security requirements in NIST Special Publication 800-172. The assessment procedures can be used to help generate and evaluate the relevant evidence needed to determine if the security safeguards employed by organizations are implemented correctly, operating as intended, and satisfy the enhanced security requirements. Organizations have the flexibility to tailor the assessment procedures by selecting the assessment methods and objects needed to achieve the assessment objectives. There is no expectation that every assessment method and object in an assessment procedure will be used for every assessment. In addition, there is significant flexibility in the scope of the assessment and the degree of rigor applied during the assessment process. The assessment procedures can support self-assessments, third-party assessments, or assessments conducted by sponsoring organizations (e.g., government agencies). Such approaches may be specified in contracts or in agreements by participating parties."}], "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": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.2.4 | Entorno de pruebas (sandbox) para aplicaciones en dispositivos... 3.2.4 Entorno de pruebas ( sandbox ) para aplicaciones en dispositivos\n\nOtra variación del modelo de despliegue de agente y puerta de enlace es hacer que las aplicaciones o procesos examinados se ejecuten en compartimentos independientes dentro de los activos."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 16)"}, {"role": "assistant", "content": "ets. 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.\nOrganizations implementing the RMF will be able to:\n\n- -Use the tasks and outputs of the Organization-Level and System-Level Prepare step to promote a consistent starting point within organizations to execute the RMF;\n- -Maximize the use of common controls at the organization level to promote standardized, consistent, and cost-effective security and privacy capability inheritance;\n- -Maximize the use of shared or cloud-based systems, services, and applications to reduce the number of authorizations needed across the organization;\n- -Employ organizationally-tailored control baselines to increase the speed of security and privacy plan development and the consistency of security and privacy plan content;\n- -Employ organization-defined controls based on security and privacy requirements generated from a systems security engineering process;\n- -Maximize the use of automated tools to manage security categorization; control selection, assessment, and monitoring; and the authorization process;\n- -Decrease the level of effort and resource expenditures for low-impact systems if those systems cannot adversely affect higher-impact systems through system connections;\n- -Maximize the reuse of RMF artifacts (e.g., security and privacy assessment results) for standardized hardware/software deployments, including configuration settings;\n- -Reduce the complexity of the IT/OT infrastructure by eliminating unnecessary systems, system components, and services - employing the least functionality 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."}], "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": 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 is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.1.1 | ZTA basada en una gobernanza de la identidad mejorada... 3.1.1 ZTA basada en una gobernanza de la identidad mejorada\n\nPara desarrollar una ZTA, el enfoque de la gobernanza de la identidad mejorada utiliza la identidad de los actores como el componente clave de la creación de las políticas."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 3)"}, {"role": "assistant", "content": "| help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n## Audience\n\n\n\n\n\nPages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality\n\n\n\nConfidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 \"Controlled Unclassified Information.\"\n\n## A Suite of Guidance\n\nNIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . \n\n\n\n\n\nNIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 Assessing Security Requirements for Controlled Unclassified Information provide? (Part 6)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1. Introduction...................................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. The Fundamentals..........................................................................................................................3 |\n| 3. The Procedures ..............................................................................................................................7 |\n| B. Glossary .....................................................................................................................101 |\n| Appendix A. Acronyms...................................................................................................................100 |\n| Appendix |\n| Appendix C. Security Requirement Assessment...............................................................................103 |\n| Appendix D. Organization-Defined Parameters...............................................................................107 |\n| Appendix E."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "..........30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5.\nC-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |\n\n| 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls..............................................................................................."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 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 additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 4)"}, {"role": "assistant", "content": "ed as independent, third-party assessments or as government-sponsored assessments. The assessments can be applied with various degrees of rigor based on customer-defined depth and coverage attributes.\n## Keywords\n\nassessment; assessment method; assessment object; assessment procedure; assurance; Controlled Unclassified Information; coverage; FISMA; NIST Special Publication 800-171; NIST Special Publication 800-53A; nonfederal organization; nonfederal system; security assessment; security requirement. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 Access Control?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\nThe assessment methods described above have associated attributes of depth and coverage , which affect the level of effort for the assessment. These attributes provide a means to define the rigor and scope of the assessment to obtain the assurance needed for enhanced security requirements. A description of assessment methods and objects is provided in Appendix C. Figure 1 illustrates an example of an assessment procedure for the CUI enhanced security requirement 3.1.3e from [SP 800-172].\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.\nParameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n........................................................ 1 | CHAPTERONE INTRODUCTION......................................................................................................\n1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 5)"}, {"role": "assistant", "content": "blication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n## Audience\n\nThis publication serves a diverse group of individuals and organizations in the public and private sectors, including individuals with:\n\n- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Acquisition or procurement responsibilities (e.g., contracting officers)\n- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts)\n\nThe above roles and responsibilities can be viewed from two perspectives:\n\n- Federal perspective : The entity establishing and conveying security assessment requirements in contractual vehicles or other types of agreements\n- Nonfederal perspective : The entity responding to and complying with the security assessment requirements set forth in contracts or agreements\n\n## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "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": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Control Baselines for Information Systems and Organizations provide?"}, {"role": "assistant", "content": "## Control Baselines for Information Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-53B\n\n\n\n## NIST Special Publication 800-53B\n\n## Control Baselines for Information Systems and Organizations\n\n## JOINT TASK FORCE\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B\n\n## October 2020\n\nINCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XI\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems. Such information security standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 10)"}, {"role": "assistant", "content": "parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.\nParameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Security and Privacy Controls for Information Systems and Organizations provide? (Part 19)"}, {"role": "assistant", "content": ".......................................................................... 424\nAPPENDIX C CONTROL SUMMARIES ..........................................................................................\n428\n\nxiii\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\nExecutive Summary\n\nAs we push computers to “the edge,” building an increasingly complex world of connected\ninformation systems and devices, security and privacy will continue to dominate the national\ndialogue. In its 2017 report, Task Force on Cyber Deterrence [DSB 2017], the Defense Science\nBoard (DSB) provides a sobering assessment of the current vulnerabilities in the U.S. critical\ninfrastructure and the information systems that support mission-essential operations and assets\nin the public and private sectors. “…The Task Force notes that the cyber threat to U.S. critical infrastructure is outpacing\nefforts to reduce pervasive vulnerabilities, so that for the next decade at least the United States\nmust lean significantly on deterrence to address the cyber threat posed by the most capable\nU.S. adversaries. It is clear that a more proactive and systematic approach to U.S. cyber\ndeterrence is urgently needed…”\n\nThere is an urgent need to further strengthen the underlying information systems, component\nproducts, and services that the Nation depends on in every sector of the critical infrastructure—\nensuring that those systems, components, and services are sufficiently trustworthy and provide\nthe necessary resilience to support the economic and national security interests of the United\nStates."}], "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": 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 Awareness and Training?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Access Control?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| | | 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 Personnel Security?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nThe target audience for this publication includes cybersecurity program leadership, cybersecurity personnel, and others who are responsible for preparing for, detecting, responding to, or recovering from cybersecurity incidents. This publication is intended for use by most organizations, regardless of sector, size, or other factors.\n\nAt that time, incidents were relatively rare, the scope of most incidents was narrow and welldefined, and incident response and recovery was usually completed within a day or two. Under those conditions, it was realistic to treat incident response as a separate set of activities performed by a separate team of personnel and to depict all incident response activities as part of a circular life cycle. Formal post-incident activities would identify needed improvements and feed them into the preparation stage, thus starting the cycle again. Incident response activities were typically intermittent rather than continuous.\n\n(e.g., detecting the presence of a new threat and characterizing its behavior) and communicate those lessons to the appropriate personnel so that the organization's incident response and other cybersecurity risk management policies, processes, and practices can be adjusted as needed."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n## Family: Incident Response"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and 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 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nt of Defense Federal Acquisition Regulation). Organizations can use the assessment procedures to generate evidence to support the assertion that the enhanced security requirements have been satisfied.\nThe assessment procedures are typically used as part of an assessment process. An assessment process is an information-gathering and evidenceproducing activity to determine the effectiveness of the safeguards implemented to meet the set of security requirements specified in [SP 800-172]. The information gathered and evidence produced can be used by an organization to:"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 14)"}, {"role": "assistant", "content": "..................................................... 50 | APPENDIX C MAPPINGTABLES ....................................................................................................\n50 |\n| APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 | APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 |\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Errata\n\nThis table contains changes that have been incorporated into Special Publication 800-172. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. Any potential updates for this 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 the SP 800-172 publication details. | DATE | TYPE | CHANGE | PAGE |\n|--------|--------|----------|--------|\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## CHAPTER ONE\n\n## INTRODUCTION\n\nTHE NEED TO PROTECT CONTROLLED UNCLASSIFIED INFORMATION\n\noday, 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."}], "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": 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 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 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 Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 16)"}, {"role": "assistant", "content": ".................................................................................. 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ...............................................................\n4\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 ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................"}], "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": 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 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 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 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nInformation technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .\nISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 20)"}, {"role": "assistant", "content": "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].\nFIGURE 1: ASSESSMENT PROCEDURE FOR CUI ENHANCED SECURITY REQUIREMENT\n\n\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\nOrganizations are not expected to use all of the assessment methods and objects contained within the assessment procedures identified in this publication. Rather, organizations have the flexibility to establish the level of effort needed and the assurance required for an assessment (e.g., which assessment methods and objects are deemed to be the most useful in obtaining the desired results). The decision on level of effort is made based on how the organization can accomplish the assessment objectives in the most cost-effective and efficient manner and with sufficient confidence to support the determination that the CUI enhanced security requirements have been satisfied. ## ORGANIZATION-DEFINED PARAMETERS\n\nSelected enhanced security requirements contain selection and assignment operations to give organizations flexibility in defining variable parts of those requirements. Selection operations require organizations to select from a list of predefined items. Assignment operations require organizations to define specific parameter values. Determination statements for organizationdefined parameters (ODP) are listed first in the assessment objective section followed by the list of determination statements for the assessment objective. Determination statements for ODPs are noted in bold italics . The ODP values are used in the appropriate determination statements in the assessment procedure, also noted in bold italics ."}], "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": 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": "How does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 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 Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nThe purpose of this publication is to provide procedures for assessing the security requirements in NIST Special Publication (SP) 800-171, Protecting Controlled Unclassified Information (CUI) in Nonfederal Systems and Organizations [3]. Organizations can use the assessment procedures to generate evidence that the security requirements have been satisfied. The scope of the security assessments conducted using the procedures described in this publication is guided and informed by the system security plans for systems that process, store, or transmit CUI. The assessment procedures offer the flexibility to customize assessments based on organizational policies and requirements, known threat and vulnerability information, system and platform dependencies, operational considerations, and tolerance for risk. 1\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.02.01.a.03[01]: security literacy training is provided to system users on recognizing indicators of insider threat."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nance. The decision to select a particular set of enhanced security requirements will be based on the mission and business needs of federal agencies and guided and informed by ongoing risk assessments.\nThe enhanced security requirements for nonfederal systems processing, storing, or transmitting CUI associated with critical programs or high value assets will be conveyed to nonfederal organizations by federal agencies in a contract, grant, or other agreement. The application of the enhanced security requirements to subcontractors will also be addressed by federal agencies in consultation with nonfederal organizations."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171Ar3\n\n\n\n## NIST Special Publication\n\n## NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-171Ar3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nforma estricta antes de permitir el acceso . Se trata de un ciclo constante de acceso, escaneo y evaluación de amenazas, adaptación y reevaluación continua de la confianza en permanente comunicación.\nAsí, se espera que la empresa que implemente una ZTA cuente con una gestión de la identidad, credenciales y acceso (ICAM, por su nombre en inglés Identity, Credential, and Access Management) y sistemas establecidos de gestión de activos. Entre ellos, se incluye el uso de la autenticación multifactor (MFA, por su denominación en inglés multifactor authentication ) para el acceso a algunos o todos los recursos de la empresa. La supervisión continua con posibles reautenticación y reautorización se produce a lo largo de las transacciones de los usuarios, según lo definido y aplicado por la política (por ejemplo, basada en el tiempo, modificación o nuevo recurso solicitado, actividad anómala de sujeto detectada), la cual procura establecer un equilibrio entre la seguridad, la disponibilidad, la usabilidad y la rentabilidad. 7. La empresa recopila toda la información posible sobre el estado actual de los activos, la infraestructura de la red y las comunicaciones, y la utiliza para mejorar la postura de seguridad. Una empresa debe reunir y procesar los datos sobre la postura de seguridad de sus bienes, el tráfico de red y las solicitudes de acceso. Además, tomará cualquier información obtenida para mejorar la creación y la aplicación de las políticas. Estos datos también servirán como contexto para las solicitudes de acceso de los sujetos (consultar la sección 3.3.1)."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n| Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Introduction ...................................................................................................................... | Introduction ...................................................................................................................... | 2 |\n| | Background - Zero Trust Principles and Zero Trust Architecture................................"}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "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 Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 7)"}, {"role": "assistant", "content": "Romine Thomas Michelli Director, Information Technology Laboratory Chair-Defense Community Donna Dodson Susan Dorr-Intelligence Community Co-Chair Cybersecurity Advisor, Information Technology Laboratory Matt Scholl Vicki Michetti Tri-Chair-Defense Community Chief, Computer Security Division Kevin Stine Chris Johnson Chief, Applied Cybersecurity Division Tri-Chair-Intelligence Community Ron Ross Paul Cunningham FISMA Implementation Project Leader Tri-Chair-Civil Agencies ## Joint Task Force Working Group | Ron Ross | Kevin Dulany | Peter Duspiva | Kelley Dempsey | |--------------------|----------------------------------|------------------------------------|----------------------| | NIST, JTF Leader | DoD | Intelligence Community | NIST | | Taylor Roberts OMB | Ellen Nadeau NIST | Victoria Pillitteri NIST | Naomi Lefkovitz NIST | | Jordan Burris OMB | Charles Cutshall OMB | Kevin Herms OMB | Carol Bales OMB | | Jeff Marron NIST | Kaitlin Boeckl NIST | Kirsten Moncada OMB | Jon Boyens NIST | | Dorian Pappas CNSS | Dominic Cussatt Veterans Affairs | Esten Porter The MITRE Corporation | Celia Paulsen NIST | | | Christina Sames | Julie Snyder | Martin Stanley | | Daniel Faigin | | | | | The Aerospace | The MITRE Corporation | The MITRE | Homeland Security | | Corporation | | Corporation | | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ The authors also wish to recognize Matt"}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["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 Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"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": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nblication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Acquisition or procurement responsibilities (e.g., contracting officers)\n- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts)"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n- Sidecar - Beside each application instance to intercept all traffic into and out of the application and handles east-west internal communication between services in the infrastructure. This is the primary use case of the service mesh.\n- Ingress gateway - Controls how applications in the cluster are exposed outside (e.g., managing what names, certificates, ports, protocols, and application endpoints are served to the world outside of the cluster). Think of this as the service mesh control plane that manages a traditional reverse proxy similar to Spring Cloud Gateway, NGINX, or HAProxy.\n- Egress gateway - Controls how applications in the cluster communicate with the outside world. This can be used for traditional egress filtering and logging, like a Squid proxy, but can also implement an identity-based policy for what is allowed to call out and perform credential exchange , or present a set of credentials (e.g., an mTLS certificate for a partner API), on behalf of the application so that the application does not need to handle them (e.g., communicating via mTLS with the partner API). Think of this as a nextgeneration identity-aware Squid proxy.\n- Edge gateway - Accepts external traffic before the ingress gateway and performs finegrained load balancing across clusters or sites. It is used to terminate external traffic, enable infrastructure-level failover, deploy blue-green clusters, and facilitate ingressgateway-per-team deployments without requiring each of those teams to have publicly routable ingress gateways. Think of this as a modern software-based local traffic manager, like F5, that can apply policy per-request rather than per-connection."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nCDM System (sistema CDM). Industry Compliance (cumplimiento de la industria). Threat Intelligence (inteligencia sobre amenazas). Activity Logs (registros de actividades). Control Plane (plano de control). Policy Engine (motor de políticas). Policy Administrator (administrador de políticas). Policy Decision Point (punto de decisión de políticas). Data plane (plano de datos). Subject (sujeto). System (sistema). Untrusted (no confiable). Policy Enforcement Point (punto de aplicación de políticas). Trusted (confiable). Enterprise Resource (recurso de la empresa). Date Access Policy (política de acceso a los datos). PKI, public key infrastructure (infraestructura de clave pública). ID Management (gestión de identidades). SIEM System (sistemas de seguridad de la información y gestión de eventos).\n\nAccess Request (solicitud de acceso). Subject Database and History (datos e historial del sujeto). Asset Database (datos del activo). Resource Policy Requirements (requerimientos de la política de recursos). Threat Intelligence and Logs (inteligencia de amenazas y registros). Trust Algorithm (algoritmo de confianza)."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.01.10.b: the device lock is retained until the user reestablishes access using established identification and authentication procedures.\n\n[SELECT FROM: access control policy and procedures; procedures for session lock and identification and authentication; system design documentation; system configuration settings; display screen with session lock activated; system security plan; other relevant documents or records]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "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 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 is CMMC practice AC.L2-3.1.6 (NIST 3.1.6)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.6. 3.1.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.6", "cmmc_practice_id": "AC.L2-3.1.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 18)"}, {"role": "assistant", "content": "rses, 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.\n## Related Resources:\n\n- View all SP 800-171 Awareness and Training Requirements and Assessment Procedures\n- NIST Free and Low-Cost Online Cybersecurity Learning Content\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n- NARA CUI training\n- Center for Development of Security Excellence Security Awareness Hub\n\n81&/$66,),('GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1)250$7,21GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1\n\n\n\n## Getting Started with Audit and Accountability\n\n## Family: Audit and Accountability\n\nDescription: Creating, protecting, and retaining system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity; and ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. ## Getting Started with Audit and Accountability\n\n\n\nUnderstand and track who is performing actions within business system(s), what those actions are, and when those actions are taken. Having the ability to review system activity and analyze records, generate reports, resolve audit log process failures, and protect audit data gives the business insight into potential unauthorized activity and improves the ability to respond quickly and appropriately. Consider automated tools for conducting audit and logging activities. Products range from free, open-source tools to commercially available ones. ## Define, maintain, and protect 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."}], "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": 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 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 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 guidance does Zero Trust Architecture provide?"}, {"role": "assistant", "content": "## NIST Publicación especial 800-207\n\n## Arquitectura de confianza cero\n\nScott Rose Oliver Borchert Stu Mitchell Sean Connelly\n\nEsta publicación se encuentra disponible en inglés de forma gratuita en https://doi.org/10.6028/NIST.SP.800-207\n\n## S E G U R I D A D I N F O R M Á T I C A\n\n## NIST\n\nNational Institute of Standards and Technologies U. S. Department of Commerce\n\n## NIST Publicación especial 800-207\n\n## Arquitectura de confianza cero\n\nScott Rose Oliver Borchert\n\nDivisión de Tecnologías Avanzadas de Red Laboratorio de Tecnologías de la Información\n\nStu Mitchell Stu2Labs Stafford, VA\n\nSean Connelly\n\nAgencia de Ciberseguridad y Seguridad de las Infraestructuras Departamento de Seguridad Nacional\n\nEsta publicación se encuentra disponible en inglés de forma gratuita en: https://doi.org/10.6028/NIST.SP.800-207\n\nTraducción al español Dreamlab Technologies Chile Yanina Ángela Bettati (2023)\n\nTraducido con permiso por cortesía del Instituto Nacional de Estándares y Tecnología (NIST). No es una traducción oficial del Gobierno de los Estados Unidos. Todos los derechos reservados. Secretaría de Comercio de EE. UU. Departamento de Comercio de EE. UU. Wilbur L. Ross, Jr., Secretario\n\nInstituto Nacional de Normas y Tecnología Walter Copan, Director del NIST y Subsecretario de Comercio para Normas y Tecnología\n\n## Autoridad\n\nEsta publicación ha sido desarrollada por NIST de conformidad con sus responsabilidades estatutarias en virtud de la Ley Federal de Modernización de la Seguridad de la Información (FISMA) de 2014, 44 U.S.C. § 3551 y siguientes, Ley Pública (P.L.) 113-283. NIST es responsable de desarrollar normas y directrices de seguridad de la información, incluidos los requisitos mínimos para los sistemas de información federales, pero dichas normas y directrices no se aplicarán a los sistemas de seguridad nacional sin la aprobación expresa de los funcionarios federales apropiados que ejercen la autoridad política sobre dichos sistemas."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["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 is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.2. 3.1.2. 3.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 5)"}, {"role": "assistant", "content": "blication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| Executive Summary................................................................................................................. 1 | 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_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 is CMMC practice AC.L2-3.1.8 (NIST 3.1.8)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.8. 3.1.8."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.8", "cmmc_practice_id": "AC.L2-3.1.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "tise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D.\nThe controls described assist organizations in defining the controls needed to satisfy minimum assurance requirements. Where additional assurance is desired to achieve risk management objectives, Table E-4 provides additional security controls and control enhancements to achieve enhanced assurance. Implementers should note that designation of assurance-related controls is not intended to imply a greater level of importance for such controls. Achieving adequate security for organizational information systems requires the correct combination of both functionality- and assurance-related security controls. ## 6 Security Controls\n\nAppendix F, the Security Control Catalog, provides a comprehensive range of countermeasures for organizations and information systems. The security controls are designed to be technologyneutral such that the focus is on the fundamental countermeasures needed to protect organizational information during processing, storage, or transmission. SP 800-53 Rev. 4, therefore, does not provide guidance on the application of security controls to specific technologies, environments of operation, or missions/business functions. These specific areas may be addressed using overlays (see below). Control enhancements are included with many security controls and are selected in order to increase the strength of the base control. Control enhancements are intended to be implemented only in conjunction with implementation of the base control. Some security controls and control enhancements include one or more assignment and selection statements. These are variable parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 10)"}, {"role": "assistant", "content": "and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance.\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement. Tailoring: The process by which control baselines are modified to achieve certain organizational goals and objectives. Definitions provided are intended as plain language. Review the NIST Glossary for official NIST definitions. Determine if your business has CUI. ## General Tips for Getting Started with NIST SP 800-171\n\nEveryone will have different approaches to getting started, but here are a few tips to get you started down the right path:\n\nUnderstand current (or future) legal, regulatory, or contractual requirements for protecting CUI. The federal agency is responsible for communicating what CUI the business is responsible for protecting as part of the contractual arrangement. If there are questions, reach out to the contracting officer. The business may also have additional compliance requirements beyond SP 800-171. If so, an initial task might be to understand where the requirements overlap and where they differ. With that information, the business can begin addressing requirements that meet multiple compliance requirements. Understand how CUI flows into, within, and out of the business. \n\nInventorying what systems or components the business has, and how the data flows into, within, and out of those systems or components, helps practitioners understand the scope of applicability of SP 800-171 security requirements to business systems. \n\nScope and Applicability of SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 15)"}, {"role": "assistant", "content": "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.\nPolicy | Deployment for a Three-tier | Application...............................................................16 |\n\n## Acknowledgments\n\nThe authors would like to express their thanks to Isabel Van Wyk of NIST for her detailed editorial review of the public comment version as well as the final publication. ## Executive Summary\n\nThe principles of zero trust, as described in NIST Special Publication (SP) 800-207, have become the guiding markers for developing secure zero trust architecture. A well-established class of applications is the cloud-native application class. The generally accepted characterization of a cloud-native application includes the following:\n\n- The application is made up of a set of loosely coupled components called microservices. Each of the microservices can be hosted on different physical or virtual machines (VMs) and even be geographically distributed (e.g., within several facilities that belong to the enterprise, such as the headquarters, branch offices, and in various cloud service provider environments). - Any transaction involving the application may also involve one or more inter-service (microservice) calls across the network. - A widespread feature (though not necessarily a requirement for cloud-native applications) is the presence of a software platform called the service mesh that provides an integrated set of all application services (e.g., services discovery, networking connections, communication resilience, and security services like authentication and authorization)."}], "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": 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 Zero Trust Architecture provide? (Part 3)"}, {"role": "assistant", "content": "ores disponibles para el propósito. En esta publicación puede haber referencias a otras que actualmente están siendo desarrolladas por NIST de acuerdo con sus responsabilidades estatutarias asignadas.\nLa información contenida en esta publicación, incluidos conceptos y metodologías, puede ser utilizada por los organismos federales incluso antes de la finalización de dichas publicaciones complementarias. Por lo tanto, hasta que se finalice cada publicación, los requisitos, directrices y procedimientos actuales, cuando existan, seguirán siendo operativos. A efectos de planificación y transición, los organismos federales pueden seguir de cerca el desarrollo de estas nuevas publicaciones del NIST. Se anima a las organizaciones a revisar todos los borradores de publicaciones durante los periodos de comentarios públicos y proporcionar retroalimentación al NIST. Muchas publicaciones sobre ciberseguridad del NIST, aparte de las mencionadas anteriormente, están disponibles en https://csrc.nist.gov/publications. ## Los comentarios sobre esta publicación pueden enviarse a\n\nInstituto Nacional de Estándares y Tecnología A la atención de: Advanced Network Technologies Division, Information Technology Laboratory\n\n100 Bureau Drive (Mail Stop 8920) Gaithersburg, MD 20899-8920\n\nCorreo electrónico: zerotrust-arch@nist.gov\n\nTodos los comentarios están sujetos a la Ley de Libertad de Información (FOIA). ## Informes sobre tecnología de sistemas informáticos\n\nEl Laboratorio de Tecnología de la Información (ITL, por su nombre en inglés, Information Technology Laboratory) del Instituto Nacional de Estándares y Tecnología (NIST) promueve la economía y el bienestar público de Estados Unidos a través de su liderazgo técnico en la infraestructura de medición y normalización del país."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["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 Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.11.01.a: the risk (including supply chain risk) of unauthorized disclosure resulting from the processing, storage, or transmission of CUI is assessed.\n\n[SELECT FROM: risk assessment policy and procedures; security planning policy and procedures; procedures for organizational assessments of risk; risk assessment; risk assessment results; risk assessment reviews; risk assessment updates; SCRM policy and procedures; inventory of critical systems, system components, and system services; procedures for organizational assessments of supply chain risk; acquisition policy; SCRM plan; system security plan; other relevant documents or records]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | ## 1 Introduction In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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\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 Planning?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| GV.SC-05 | Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties | Medium | R1: Cybersecurity supply chain risk management requirements should include cybersecurity performance and vulnerability, threat, and incident disclosure and information sharing."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication NIST SP 800-207A\n\n## A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Location Environments\n\nRamaswamy Chandramouli Zack Butcher\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-207A\n\n\n\n## NIST Special Publication NIST SP 800-207A\n\n## A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Location Environments\n\nRamaswamy Chandramouli\n\nComputer Security Division Information Technology Laboratory\n\nZack Butcher Tetrate, Inc. This publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-207A\n\nSeptember 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "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": 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 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 Information Integrity?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n- A built-in infrastructure for (a) providing service identities, (b) service discovery, and (c) external policy-based authorization engines in which policies incorporate contextual variables. Policies pertain to service-to-service and user-to-resource authentications and authorizations and ensure application integrity and confidentiality. These policies generally are expressed through a structure called access control. Some examples of access control models include: Next Generation Access Control (NGAC) model, and Attribute-based access control (ABAC) model.\n- Code for performing network-related functions (e.g., traffic routing) and for ensuring network resiliency through functions such as retries, timeouts, blue-green deployments, and circuit breaking.\n- More details on the container orchestration platform with an integrated service mesh can be found in [2], and an access control implementation in that platform is described extensively in [3].\n\n- Measure the integrity and security posture of all resources by establishing a continuous diagnostics and mitigation (CDM) or similar system to monitor the state of devices and applications and apply patches or fixes as needed.\n- An enterprise should collect data about the resource security posture, network traffic, and access requests; process that data; and use any insight gained to improve policy creation and enforcement. This data can also be used to provide context for access requests from subjects."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Zero Trust Architecture:\n\n| | | 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 2 require for Incident Response?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\noperations, exercising an incident response plan, and monitoring network traffic). Individuals are the people applying the specifications, mechanisms, or activities described above.\n\n## 3.6. Incident Response"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- Based on NIST SP 800-53, Revision 5 and the NIST SP 800-53B moderate impact control baseline.\n- Applies updated tailoring criteria addressing stakeholder feedback (adding new, consolidating, and withdrawing requirements).\n- Includes increased specificity in security requirements.\n- Introduces organization-defined parameters (ODP) to increase flexibility to better manage organizationspecific risks.\n\nControl Baseline: A set of controls you can implement to meet strategic, legal, regulatory, or contractual security and privacy requirements and manage risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 14)"}, {"role": "assistant", "content": "effectiveness of security\nand privacy controls associated with systems and their environments of operation and to\nprovide credible and meaningful inputs to the organization’s risk management process.\nA well-\nexecuted assessment helps determine the validity of the controls contained in the organization’s\nsecurity and privacy plans and subsequently employed in organizational systems and\nenvironments of operation. Control assessments facilitate a cost-effective approach to\nmanaging risk by identifying weaknesses or deficiencies in systems, thus enabling the\norganization to determine appropriate risk responses in a disciplined manner that is consistent\nwith organizational mission and business needs. SP 800-53A is a companion guideline to [SP 800-53] Security and Privacy Controls for Systems\nand Organizations. Each publication provides guidance for implementing specific steps in the\nRisk Management Framework (RMF).1 SP 800-53 and [SP 800-53B] address the Select step of the\nRMF and provide guidance on security and privacy control selection (i.e., determining the\ncontrols needed to manage risks to organizational operations and assets, individuals, other\norganizations, and the Nation). SP 800-53A addresses the Assess and Monitor steps of the RMF\nand provides guidance on the security and privacy control assessment processes. SP 800-53A\nalso includes guidance on how to build effective assessment plans and how to analyze and\nmanage assessment results. SP 800-53A provides a process that allows organizations to tailor the assessment procedures\noutlined in the guidance. Tailoring involves customizing the assessment procedures to match\nthe characteristics of the system and its environment of operation more closely."}], "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": 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 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 Access Control?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n- Applying a threat-centric approach to security requirements specification;\n- Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16\n- Implementing dual authorization controls for the most critical or sensitive operations;\n- Limiting persistent storage to isolated enclaves or domains;\n- Implementing a comply-to-connect approach for systems and networks;\n- Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components;\n- Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components;\n- Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and\n- Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 15)"}, {"role": "assistant", "content": "gns to achieve cyber resiliency and survivability. 4 Unless specified by legislation, regulation, or government-wide policy, the term system is used in this publication instead of information system.\nThis change reflects a broad-based and holistic definition of systems that includes general-purpose systems, industrial control systems, cyber-physical systems, and individual devices that are part of the Internet of Things. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n- Provide information security situational awareness. The assessment procedures in this publication 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. ## THE SCOPE OF ENHANCED SECURITY REQUIREMENT ASSESSMENTS\n\nThe scope of the assessments conducted using the procedures described in this publication is guided and informed by the system security plans for the organizational systems processing, storing, or transmitting CUI. The assessments focus on the overall effectiveness of the security safeguards intended to satisfy the enhanced security requirements defined in [SP 800-172]."}], "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": 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 Control Baselines for Information Systems and Organizations provide? (Part 20)"}, {"role": "assistant", "content": "| SYSTEMANDSERVICESACQUISITION FAMILY .........................................................................\n| 42 |\n| 3.18 | SYSTEMANDCOMMUNICATIONSPROTECTIONFAMILY .......................................................... | 46 |\n| 3.19 | SYSTEMANDINFORMATIONINTEGRITYFAMILY ..................................................................... | 51 |\n| 3.20 | SUPPLYCHAINRISKMANAGEMENTFAMILY ........................................................................... | 55 |\n| REFERENCES .................................................................................................................................. | REFERENCES .................................................................................................................................."}], "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": 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 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 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\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. This publication 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."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 8)"}, {"role": "assistant", "content": "e requirements also apply to services, including externally provided services, that process, store, or transmit CUI, or that provide security protections, for the system requiring enhanced protection.\nThe protection of a specific service to include CUI that is processed, stored or transmitted during the provision of that service, is achieved by implementing the enhanced security requirements for the service, or the system or system components responsible for providing that service. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. The term organizational system is used in many of the enhanced security requirements. It has a specific meaning regarding the applicability of the enhanced requirements as described above. Appropriate scoping considerations for the requirements are important factors in determining protection-related investment decisions and managing security risk for nonfederal organizations that have the responsibility of protecting CUI associated with critical programs and high value assets. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## FRAMEWORK FOR IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY\n\nOrganizations that have implemented or plan to implement the NIST Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| |-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | ASSESSMENT OBJECTIVE Determine if: | ASSESSMENT OBJECTIVE Determine if: | | | 3.11.6e[a] | Supply chain risks associated with organizational systems and system components are identified."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "nt security and privacy controls that meet mission and business needs, assess the effectiveness of the controls, authorize the systems for operation, and continuously monitor the systems.\nExercising due diligence and implementing robust and comprehensive information security and privacy risk management programs can facilitate compliance with applicable laws, regulations, executive orders, and government-wide policies. Risk management frameworks and risk management processes are essential in developing, implementing, and maintaining the protection measures necessary to address stakeholder needs and the current threats to organizational operations and assets, individuals, other organizations, and the Nation. Employing effective risk-based processes, procedures, methods, and technologies ensures that information systems and organizations have the necessary trustworthiness and resiliency to support essential mission and business functions, the U.S. critical infrastructure, and continuity of government. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## COMMON SECURITY AND PRIVACY FOUNDATIONS\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."}], "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": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n3.2.4 DEVELOP ASSESSMENT PROCEDURES FOR ORGANIZATION-SPECIFIC CONTROLS\n\nBased on organizational policies, mission or business function requirements, and an assessment\nof risk, organizations may choose to develop and implement additional (organization-specific)\ncontrols or control enhancements for their systems that are beyond the scope of [SP 800-53]."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 Zero Trust Architecture provide? (Part 2)"}, {"role": "assistant", "content": "as normas y directrices no se aplicarán a los sistemas de seguridad nacional sin la aprobación expresa de los funcionarios federales apropiados que ejercen la autoridad política sobre dichos sistemas.\nEsta directriz es coherente con los requisitos de la Circular A-130 de la Oficina de Gestión y Presupuesto (OMB). Nada de lo que figura en esta publicación debe interpretarse como contradictorio con las normas y directrices que el Secretario de Comercio ha hecho obligatorias y vinculantes para los organismos federales en virtud de la autoridad legal. Estas directrices tampoco deben interpretarse como una alteración o sustitución de las autoridades existentes del Secretario de Comercio, el Director de la OMB o cualquier otro funcionario federal. Esta publicación puede ser utilizada por organizaciones no gubernamentales de forma voluntaria y no está sujeta a derechos de autor en los Estados Unidos. No obstante, el NIST agradecerá que se cite su procedencia. Publicación especial 800-207 del Instituto Nacional de Estándares y Tecnología (NIST)\n\nInst. Nac. Est. Technol. Publ. Espec. 800-207, 59 páginas (agosto de 2020) CODEN: NSPUE2\n\nEsta publicación está disponible en inglés de forma gratuita en: https://doi.org/10.6028/NIST.SP.800-207\n\nEn este documento pueden identificarse ciertas entidades, equipos o materiales comerciales con el fin de describir adecuadamente un procedimiento o concepto experimental. Dicha identificación no implica una recomendación o aprobación por parte del NIST, ni que las entidades, materiales o equipos sean necesariamente los mejores disponibles para el propósito. En esta publicación puede haber referencias a otras que actualmente están siendo desarrolladas por NIST de acuerdo con sus responsabilidades estatutarias asignadas."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["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 5)"}, {"role": "assistant", "content": "s and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n## Overview\n\n## Structure of SP 800-171\n\nSP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page). | Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Understanding the Security Requirements in SP 800-171\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n\n\n## Top 5 Frequently Asked Questions\n\n## Top five questions NIST receives on SP 800-171:\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Configuration Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n| 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 |"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 6)"}, {"role": "assistant", "content": ". Entre ellas se encuentran Greg Holden, director del proyecto ZTA del Consejo Federal de CIO; Alper Kerman, director del proyecto ZTA del NIST/Centro Nacional de Ciberseguridad; y Douglas Montgomery.\nEn la traducción, un especial reconocimiento a las personas que colaboraron de alguna u otra forma con la gestión, redacción, terminología específica y compaginación: Fabien Spychiger, CEO Dreamlab Technologies Chile; Javier Toro Rodríguez, Cybersecurity Service Manager, Dreamlab Tecnologies Chile; Stéphane Bürgi, Senior Technical Writer Dreamlab Technologies Chile y Celeste Gauna, Cyberintelligence Analyst Dreamlab Technologies Chile. ## Audiencia\n\nEste documento pretende describir la confianza cero para los arquitectos de seguridad empresarial. Se intenta ayudar a la comprensión de la confianza cero para los sistemas civiles no clasificados y proporcionar una hoja de ruta para migrar y desplegar conceptos de seguridad de confianza cero a un entorno empresarial. Los responsables de ciberseguridad de las agencias, los administradores de red y los directivos también pueden obtener información sobre la confianza cero y la ZTA a partir de este documento. Esta guía no pretende ser un plan de despliegue único para la ZTA, ya que cada empresa tendrá sus propios casos de uso y activos de datos que requieran protección. Si se parte de un conocimiento sólido del negocio y los datos de la organización, se obtendrá un enfoque sólido de la confianza cero. ## Información sobre marcas registradas\n\nTodas las marcas registradas o comerciales pertenecen a sus respectivas organizaciones. ## Aviso de divulgación de patentes\n\nAVISO: el laboratorio de tecnologías de la información (ITL) ha solicitado que los titulares de registros de patentes cuyo uso pueda ser necesario para el cumplimiento de las orientaciones o requisitos de esta publicación comuniquen dichos registros de patentes al ITL."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["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 Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Access Control\n\n## Getting Started with Access Control"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 2)"}, {"role": "assistant", "content": "ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 is CMMC practice AC.L2-3.1.7 (NIST 3.1.7)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.7. 3.1.7."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.7", "cmmc_practice_id": "AC.L2-3.1.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 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": "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 Maintenance?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n...................................................................... 14\nCHAPTER THREE THE CONTROLS .................................................................................................\n16\n3.1 ACCESS CONTROL .................................................................................................................. 18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 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 System and Communications Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 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 Security and Privacy Controls for Information Systems and Organizations provide? (Part 16)"}, {"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\nTable of Contents\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 ............................................................................."}], "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": 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 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": "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 does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nWith a renewed emphasis on the use of trustworthy, secure information systems and supply\nchain security, it is essential that organizations express their security and privacy requirements\nwith clarity and specificity in order to obtain the systems, components, and services necessary\nfor mission and business success. Accordingly, this publication provides controls in the System\nand Services Acquisition (SA) and Supply Chain Risk Management (SR) families that are directed\nat developers. The scope of the controls in those families includes information system, system\ncomponent, and system service development and the associated developers whether the\ndevelopment is conducted internally by organizations or externally through the contracting and\nacquisition processes. The affected controls in the control catalog include SA-8, SA-10, SA-11,\nSA-15, SA-16, SA-17, SA-20, SA-21, SR-3, SR-4, SR-5, SR-6, SR-7, SR-8, SR-9, and SR-11. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................"}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide?"}, {"role": "assistant", "content": "## Assessing Enhanced Security Requirements for Controlled Unclassified Information\n\nRON ROSS VICTORIA PILLITTERI KELLEY DEMPSEY\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\n\n\n## NIST Special Publication 800-172A\n\n## Assessing Enhanced Security Requirements for Controlled Unclassified Information\n\nRON ROSS VICTORIA PILLITTERI KELLEY DEMPSEY\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172A\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by the National Institute of Standards and Technology (NIST) to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["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 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 does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 2)"}, {"role": "assistant", "content": "ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n[SELECT FROM: access control policy and procedures; procedures for least privilege; list of system-generated privileged accounts; list of system administration personnel; system audit records; system configuration settings; system security plan; list of system-generated security functions or security-relevant information assigned to system accounts or roles; other relevant documents or records]\n\nFor example, many technical security requirements are satisfied by security capabilities that are examine the security functions of products and established configuration settings. Assessments built into commercial information technology products and systems. Product assessments are typically conducted by independent, third-party testing organizations. 5 These assessments can also be conducted to demonstrate compliance with industry, national, or international security standards as well as developer and vendor claims. Since many information technology"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "The guide was developed and is maintained by the Joint Task Force Transformation Initiative Interagency Working Group, part of an ongoing information security partnership among the U.S. Department of Defense, the Intelligence Community, the Committee on National Security Systems, the Department of Homeland Security, and U.S. federal civil agencies. SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. SP 800-53 Revision 4 is part of the NIST Special Publication 800-series that reports on the NIST Information Technology Laboratory's (ITL) computer security-related research, guidelines, and outreach. The publication provides a comprehensive set of security controls, three security control baselines (low, moderate, and high impact), and guidance for tailoring the appropriate baseline to specific needs according to the organization's missions, environments of operation, and technologies used. As the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 is CMMC practice AC.L2-3.1.10 (NIST 3.1.10)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.10. 3.1.10."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.10", "cmmc_practice_id": "AC.L2-3.1.10", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 7)"}, {"role": "assistant", "content": "nts, third-party assessments, or assessments conducted by sponsoring organizations (e.g., government agencies). Such approaches may be specified in contracts or in agreements by participating parties.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## DEFINITION AND USAGE OF THE TERM INFORMATION SYSTEM\n\nUnless 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. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## ORGANIZATIONAL SYSTEMS\n\nThe term organizational system is used in many of the CUI enhanced security requirements in [SP 800-172] and the associated assessment procedures in this publication. In that context, an organizational system is a nonfederal system that processes, stores, or transmits CUI associated with a critical program or high value asset. Specifically, enhanced security requirements apply to the system components or services that process, store, or transmit CUI or that provide security protections for those components or services as mandated by a federal agency in a contract, grant, or other agreement."}], "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": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n3.4.3e Employ automated discovery and management tools to maintain an up-to-date, complete, accurate, and readily available inventory of system components. 3.4.3. 3.4.3e | Employ automated discovery and management tools to maintain an up-to-date, complete, accurate, and readily available inventory of system components."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nOrganizations are concerned about the risks associated with products and services that may potentially contain malicious functionality, are counterfeit, or are vulnerable due to poor manufacturing and development practices within the supply chain. These risks are associated with an enterprise's decreased visibility into and understanding of how the technology they acquire is developed, integrated, and deployed or the processes, procedures, standards, and practices used to ensure the security, resilience, reliability, safety, integrity, and quality of the products and services.\n\nThis publication provides guidance to organizations on identifying, assessing, and mitigating cybersecurity risks throughout the supply chain at all levels of their organizations. The publication integrates cybersecurity supply chain risk management (C-SCRM) into risk management activities by applying a multilevel, C-SCRM-specific approach, including guidance on the development of C-SCRM strategy implementation plans, C-SCRM policies, C-SCRM plans, and risk assessments for products and services."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 14)"}, {"role": "assistant", "content": "ent 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.\nAn assessment process is an information-gathering and evidenceproducing activity to determine the effectiveness of the safeguards implemented to meet the set of security requirements specified in [SP 800-172]. The information gathered and evidence produced can be used by an organization to:\n\n- Identify problems or shortfalls in the organization's security and risk management programs,\n- Identify security weaknesses and deficiencies in organizational systems 4 and the environments in which those systems operate,\n- Prioritize risk mitigation decisions and activities,\n- Confirm that identified security weaknesses and deficiencies in organizational systems and environments of operation have been addressed,\n- Support continuous monitoring activities, and\n\n1 The National Archives and Records Administration CUI Registry [NARA CUI] is the online repository for information, guidance, policy, and requirements on handling CUI. 2 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 that significantly increases capabilities and mission effectiveness or extends the expected effective life of an essential system/capability [DOD ACQ]. 3 The enhanced security requirements are designed to respond to the advanced persistent threat (APT) for CUI associated with a high value asset or critical program by promoting penetration-resistant architectures, damagelimiting operations, and designs to achieve cyber resiliency and survivability. 4 Unless specified by legislation, regulation, or government-wide policy, the term system is used in this publication instead of information system."}], "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": 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 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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 18)"}, {"role": "assistant", "content": "| |\n| D.4.1.6.\nImpact Analysis...................................................................................................................226 | |\n| D.4.1.7. Risk Response Analysis.......................................................................................................227 | |\n| D.4.1.8. Roles and Responsibilities ..................................................................................................228 | |\n| D.4.1.9. Definitions ..........................................................................................................................228 | |\n| D.4.1.10."}], "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": 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 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.04.05[01]: physical access restrictions associated with changes to the system are defined and documented."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nlar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172A Natl. Inst. Stand. Technol. Spec. Publ. 800-172A, 62 pages (March 2022)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["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 Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nDEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..................................................................................\n7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................"}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 12)"}, {"role": "assistant", "content": "| ..............................................................................................................\n17 |\n| 3.7 MAINTENANCE | ...................................................................................................................... 18 |\n| 3.8 MEDIAPROTECTION | .............................................................................................................. 18 |\n| 3.9 PERSONNEL SECURITY | ............................................................................................................ 18 |\n| 3.10 PHYSICAL PROTECTION ........................................................................................................ | 19 |\n| 3.11 RISKASSESSMENT | ................................................................................................................ 19 |\n| 3.12 SECURITY ASSESSMENT | ........................................................................................................"}], "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": 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 Services Acquisition?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes assist with maintaining cross-references | |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ID.RA-09 | The authenticity and integrity of hardware and software are assessed prior to acquisition and use | Medium | N1: See the notes for ID.RA."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "n before the\ncompletion of such companion publications. Thus, until each publication is completed, current\nrequirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and\ntransition purposes, federal agencies may wish to closely follow the development of these new\npublications by NIST. Organizations are encouraged to review draft publications during the designated public comment\nperiods and provide feedback to NIST. Many NIST publications, other than the ones noted above,\nare available at https://csrc.nist.gov/publications. Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology\nAttn: Computer Security Division, Information Technology Laboratory\n100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. i\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nReports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory\n(ITL) promotes the U.S. economy and public welfare by providing technical leadership for the\nNation’s measurement and standards infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT)."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 17)"}, {"role": "assistant", "content": "cy is followed. 12 'Adequately addressed by other related controls' means that the protection capability offered by the control is provided by another control in the same or different control family.\nUsing this tailoring option helps to eliminate potential redundancy in requirements without affecting the protection of CUI in nonfederal systems and organizations. specified for confidentiality protection. The Program Management (PM) family is not included because it is not associated with any control baseline. Finally, the Contingency Planning (CP) family is not included because it addresses availability. 13\n\nTable 1. Security 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\nOrganization-defined parameters (ODPs) are included in certain security requirements. ODPs provide flexibility through the use of assignment and selection operations to allow federal agencies and nonfederal organizations to specify values for the designated parameters in the requirements. 14 Assignment and selection operations provide the capability to customize the security requirements based on specific protection needs. The determination of ODP values can be guided and informed by laws, Executive Orders, directives, regulations, policies, standards, guidance, or mission and business needs."}], "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": 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 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 Personnel Security?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n- Applying a threat-centric approach to security requirements specification;\n- Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16\n- Implementing dual authorization controls for the most critical or sensitive operations;\n- Limiting persistent storage to isolated enclaves or domains;\n- Implementing a comply-to-connect approach for systems and networks;\n- Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components;\n- Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components;\n- Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and\n- Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 5)"}, {"role": "assistant", "content": "quirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.\n## Keywords\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors also wish to recognize the scientists, engineers, and research staff from the NIST Computer Security and the Applied Cybersecurity Divisions for their exceptional contributions in helping to improve the content of the publication. A special note of thanks to Pat O'Reilly, Jim Foti, Jeff Brewer, Chris Enloe, Ned Goren, and the entire NIST web team for their outstanding administrative support. Finally, the authors also gratefully acknowledge the contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\npublic. Sometimes, the media learns of incidents through alternate sources (i.e., not through public affairs personnel). Having a media engagement strategy in place can greatly aid in this situation.\n| CSF Element | CSF Element Description regarding cybersecurity- | Priority | Recommendations, Considerations, Notes notifications, data breach reporting, and |\n|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| GV.OC-04 | understood and managed Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated | Medium | N1: Understanding critical external dependencies on the organization's operations can aid in prioritizing response and recovery efforts. |\n| GV.OC-05 | Outcomes, capabilities, and services that the organization depends on are understood and communicated | Medium | N1: Understanding critical dependencies on external resources (e.g., cloud-based hosting providers and managed service providers) can aid in prioritizing response and recovery efforts."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Zero Trust Architecture provide? (Part 13)"}, {"role": "assistant", "content": "| | | ..............................................................................................................................................................54 | | | 7.3.4 | Formulación de políticas para el candidato a la ZTA ............................................................................54 | | | 7.3.5 | Identificación de soluciones candidatas ...............................................................................................55 | | | 7.3.6 | Implementación inicial y control ..........................................................................................................56 | | | 7.3.7 | Ampliación de la ZTA ............................................................................................................................56 | | | REFERENCIAS................................................................................................................................................................58 | REFERENCIAS................................................................................................................................................................58 | | | Lista de apéndices | Lista de apéndices | | | APÉNDICE A | : | SIGLAS.....................................................................................................................................................61 | | B.1 | E STUDIO SOBRE LA TECNOLOGÍA ........................................................................................................................63 | | | B.2 | BRECHAS QUE IMPIDEN EL PASO INMEDIATO A LA ZTA...........................................................................................64 | | | B.2.1 | Falta de términos comunes para el diseño, la planificación y la adquisición de ZTA ...........................64 | | | B.2.2 | Percepción de que la ZTA entra en conflicto con las políticas federales de ciberseguridad existentes ..............................................................................................................................................................64 | ..."}], "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": 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 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 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 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 8)"}, {"role": "assistant", "content": "ederal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui.\n- NIST is responsible for developing and publishing the security requirements for the protection of CUI. How requirements are mandated, and any compliance issues related to nonfederal implementation of SP 800-171, are the responsibility of the federal agency requiring its use , as expressed in a specific contract or agreement. ## Additional NIST Resources\n\n- NIST's Protecting CUI Frequently Asked Questions\n- Changes Between SP 800-171 Rev. 2 and Rev. 3 (.xlsx)\n- The NIST Cybersecurity and Privacy Reference Tool (CPRT) provides online, interactive versions of the updated security requirements in SP 800-171, Revision 3 and the updated assessment procedures in SP 800-171A, Revision 3\n- Event Recording: ' CUI Security Requirements Workshop ,' which provides a general overview of SP 800 -171 and SP 800-171A\n- NIST Small Business Cybersecurity Corner\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n## What to Expect\n\nThe following pages delve deeper into the SP 800-171 R3 publication to provide more details for those responsible for implementing the requirements 3 . The following pages cover:\n\n\n\nPage 8: Key differences between SP 800-171 R2 and R3. Pages 9-10: General tips for getting started. Pages 11-28: Tips for getting started, broken out by Control Family. 3 We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 12)"}, {"role": "assistant", "content": "| ..............................................................................................................\n17 |\n| 3.7 MAINTENANCE | ...................................................................................................................... 18 |\n| 3.8 MEDIAPROTECTION | .............................................................................................................. 18 |\n| 3.9 PERSONNEL SECURITY | ............................................................................................................ 18 |\n| 3.10 PHYSICAL PROTECTION ........................................................................................................ | 19 |\n| 3.11 RISKASSESSMENT | ................................................................................................................ 19 |\n| 3.12 SECURITY ASSESSMENT | ........................................................................................................"}], "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": 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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Acquisition or procurement responsibilities (e.g., contracting officers)\n- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts)\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n[SELECT FROM: access control policy and procedures; procedures for least privilege; list of system-generated privileged accounts; list of system administration personnel; system audit records; system configuration settings; system security plan; list of system-generated security functions or security-relevant information assigned to system accounts or roles; other relevant documents or records]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 12)"}, {"role": "assistant", "content": "functional and assurance specifications, design documentation, and architectures) associated with a system. Mechanisms are the hardware, software, and firmware safeguards implemented within a system.\nActivities are the protectionrelated actions supporting a system that involve people (e.g., conducting system backup\n\n2 SP 800-53A [5] provides additional information on the assessment process and the individuals steps listed above. 3 Artifacts may be in formats other than documents (e.g., databases, Governance, Risk, and Compliance [GRC] tools, or Open Security Controls Assessment Language [OSCAL]). operations, exercising an incident response plan, and monitoring network traffic). Individuals are the people applying the specifications, mechanisms, or activities described above. Assessment methods define the nature and extent of the assessor's actions and are used to facilitate understanding, achieve clarification, or obtain evidence. The assessment methods include examine , interview , and test . The examine method is the process of reviewing, studying, inspecting, or analyzing assessment objects. The interview method is the process of holding discussions with individuals or groups about assessment objects. The test method is the process of exercising assessment objects (i.e., activities, mechanisms) under specified conditions to compare actual with expected behavior. Assessment methods include attributes of depth and coverage , which define the rigor, scope, and level of effort for the assessment as well as the degree of assurance that the security requirements have been satisfied. See SP 800-53A, Appendix C, Assessment Method Descriptions [5]."}], "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": 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 Security Assessment?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n- The global control plane can be leveraged to perform the functions of individual control planes at the enterprise level rather than at the cluster level (e.g., issuing identities to all services in the enterprise by leveraging the enterprise Public Key Infrastructure (PKI) system).\n- The global control plane can also be used to shut down a specific control plane if all cluster nodes under the jurisdiction of that control plane have been compromised.\n- The management plane provides the human-computer interfaces (e.g., user interfaces, such as command line interfaces and APIs) that enable enterprise-level systems to work by encoding organizational processes related to the usage of various tools (e.g., policy definition and evaluation tools, telemetry tools) at the lower layer.\n\n- Identity-tier policies enable the automated testing of policies. Policies that are independent of infrastructure can be tested by merely exercising the application and observing the outcomes (e.g., trace the sequence of service calls and requests or responses instead of configuring the infrastructure correctly for test runs).\n- Identity-tier policies enable 'policy as code' (PaC). With the availability of tools for the declarative specification of policies through PaC, identity-tier policies can be defined and implemented by incorporating the code into automated workflows, such as continuous integration/continuous delivery (CI/CD) pipelines.\n- Identity-tier policies enable fine-grained access control by providing visibility into application call sequences/interdependencies and data flows through request-level tracking, which enables the enforcement of security policies for application traffic that is both north-south and east-west, irrespective of the environment (e.g., corporate data center or cloud infrastructure)."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 11)"}, {"role": "assistant", "content": "gnificant contributions from individuals and organizations in the public and private sectors whose constructive comments improved the overall quality, thoroughness, and usefulness of this publication.\nThe authors also wish to thank the NIST technical editing and production staff - Jim Foti, Jeff Brewer, Eduardo Takamura, Isabel Van Wyk, Cristina Ritfeld, Derek Sappington, and Carolyn Schmidt - for their outstanding support in preparing this document for publication. Finally, a special note of thanks goes out to Kelley Dempsey for the initial research and development of the content used in the prototype CUI overlay. ## Historical Contributions\n\nThe authors also wish to acknowledge the following organizations and individuals for their historic contributions to this publication:\n\n- Organizations: National Archives and Records Administration, Department of Defense\n- Individuals: Carol Bales, Matthew Barrett, Jon Boyens, Devin Casey, Christian Enloe, Gary Guissanie, Peggy Himes, Robert Glenn, Elizabeth Lennon, Vicki Michetti, Dorian Pappas, Karen Quigg, Mark Riddle, Matthew Scholl, Mary Thomas, Murugiah Souppaya, Patricia Toth, and Patrick Viscuso\n\n## 1. Introduction\n\nExecutive Order (EO) 13556 [1] established a government-wide program to standardize the way the executive branch handles Controlled Unclassified Information (CUI). 1 EO 13556 required that the CUI program emphasize openness, transparency, and uniformity of government-wide practices and that the program implementation take place in a manner consistent with Office of Management and Budget (OMB) policies and National Institute of Standards and Technology (NIST) standards and guidelines. As the CUI program Executive Agent, the National Archives and Records Administration (NARA) provides information, guidance, policy, and requirements on handling CUI [4]. This includes approved CUI categories and descriptions, the basis for safeguarding and dissemination controls, and procedures for the use of CUI."}], "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": 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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nMany organizations may use more than one of these approaches, such as internally performing basic incident response and engaging third-party resources for assistance with certain incidents. Larger organizations may have multiple incident response teams, with each team responsible for a particular logical or physical segment of the organization. When this model is employed, the teams should be part of a single coordinated entity (e.g., a federation) to ensure that incident response processes, procedures, and training are consistent across the organization and that information is shared among teams. The Community Profile is intended for use by most organizations, regardless of sector, size, or other factors. Additional versions of this Community Profile could be developed for narrower audiences, such as federal agencies, small businesses, or educational institutions. For more information on CSF 2.0 Community Profiles, see the Framework Resource Center."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 13)"}, {"role": "assistant", "content": "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.\nviii\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\nINFORMATION SYSTEMS — A BROAD-BASED PERSPECTIVE\n\nAs we push computers to “the edge,” building an increasingly complex world of interconnected\nsystems and devices, security and privacy continue to dominate the national dialogue. There is\nan urgent need to further strengthen the underlying systems, products, and services that we\ndepend on in every sector of the critical infrastructure to ensure that those systems, products,\nand services are sufficiently trustworthy and provide the necessary resilience to support the\neconomic and national security interests of the United States. NIST Special Publication 800-53,\nRevision 5, responds to this need by embarking on a proactive and systemic approach to develop\nand make available to a broad base of public and private sector organizations a comprehensive\nset of security and privacy safeguarding measures for all types of computing platforms, including\ngeneral purpose computing systems, cyber-physical systems, cloud systems, mobile systems,\nindustrial control systems, and Internet of Things (IoT) devices. Safeguarding measures include\nboth security and privacy controls to protect the critical and essential operations and assets of\norganizations and the privacy of individuals."}], "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": 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 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 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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 5)"}, {"role": "assistant", "content": ", and academic organizations. ## Supplemental Content\n\nNIST has established an Incident Response project page that hosts links to resources with additional information on incident response activities.\nBy moving links from this document to a website, NIST can update and expand them as needed without having to release a new version of this publication. For more information on CSF 2.0 Community Profiles, see the Framework Resource Center. ## Audience\n\nThe target audience for this publication includes cybersecurity program leadership, cybersecurity personnel, and others who are responsible for preparing for, detecting, responding to, or recovering from cybersecurity incidents. This publication is intended for use by most organizations, regardless of sector, size, or other factors. ## Trademark Information\n\nAll registered trademarks belong to their respective organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["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 Awareness and Training?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 17)"}, {"role": "assistant", "content": "| |\n| D.4.1.2.\nDescription .........................................................................................................................218 | |\n| D.4.1.3. Information Gathering and Scoping Analysis .....................................................................219 | |\n| D.4.1.4. Threat Analysis ...................................................................................................................225 | |\n| D.4.1.5. Vulnerability Analysis .........................................................................................................225 | |\n| D.4.1.6."}], "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": 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 does CMMC Level 2 require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/171/a/r3/final, including related content, potential updates, and document history.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.02.01.ODP[01]: the frequency at which to provide security literacy training to system users after initial training is defined . A.03.02.01.ODP[02]: events that require security literacy training for system users are defined. A.03.02.01.ODP[03]: the frequency at which to update security literacy training content is defined. A.03.02.01.ODP[04]: events that require security literacy training content updates are defined. A.03.02.01.a.01[01]: security literacy training is provided to system users as part of initial training for new users. security literacy training is provided to system users"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nOrganizations are concerned about the risks associated with products and services that may potentially contain malicious functionality, are counterfeit, or are vulnerable due to poor manufacturing and development practices within the supply chain. These risks are associated with an enterprise's decreased visibility into and understanding of how the technology they acquire is developed, integrated, and deployed or the processes, procedures, standards, and practices used to ensure the security, resilience, reliability, safety, integrity, and quality of the products and services. | 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "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 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 guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\naft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n8 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products).\nSince many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 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 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 does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information.\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nother than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide?"}, {"role": "assistant", "content": "\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Configuration Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n| 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 |"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nIn developing standards and guidelines required by [FISMA], NIST consults with other federal agencies and\noffices as well as private sector entities to improve information security, avoid unnecessary and costly\nduplication of effort, and ensure that NIST publications complement the standards and guidelines\nemployed for the protection of national security systems. In addition to its comprehensive public review\nand vetting process, NIST collaborates with the Office of the Director of National Intelligence (ODNI), the\nDepartment of Defense (DoD), and the Committee on National Security Systems (CNSS) to establish and\nmaintain a unified framework and common foundation for information security across the Federal\nGovernment. A common foundation and framework for information security provides the intelligence,\ndefense, and civilian sectors of the Federal Government and their contractors more uniform and\nconsistent ways to manage risks to organizational operations and assets, individuals, other organizations,\nand the Nation that result from the operation and use of systems. A common foundation and framework\nalso provides a strong basis for the reciprocal acceptance of security authorization decisions and facilitate\ninformation sharing. NIST also works with public and private sector entities to establish and maintain\nspecific mappings and relationships between the security standards and guidelines developed by NIST, the\nInternational Organization for Standardization (ISO), and the International Electrotechnical Commission\n(IEC)."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 10)"}, {"role": "assistant", "content": "Parameters\n- Appendix E: Change Log\n\nThe contents of this publication can be used for many different assessment-related purposes to determine organizational compliance with the security requirements.\nThe broad range of potential assessment methods and objects listed in this publication does not necessarily reflect and should not be directly associated with actual compliance or noncompliance. Rather, the selection of specific assessment methods and objects from the list provided can help generate a picture of overall compliance with the security requirements. There is no expectation about the number of methods or objects needed to determine compliance with the security requirements. Moreover, the entire list of potential assessment objects should not be viewed as required artifacts needed to determine compliance. Organizations have the flexibility to determine the specific methods and objects sufficient to obtain the needed evidence to support any claims of compliance. ## 2. The Fundamentals\n\nThe process used by organizations and assessors to assess the security requirements in SP 800171 [3] includes (1) preparing for the assessment, (2) developing a security assessment plan, (3) conducting the assessment, and (4) documenting, analyzing, and reporting the assessment results. 2 The remainder of this section describes the structure and content of the procedures used to assess the security requirements and the importance of assurance cases in providing the evidence necessary to determine compliance with the requirements. ## 2.1. Assessment Procedures\n\nThe security requirements in SP 800-171 are organized into 17 families, as illustrated in Table 1. The assessment procedures in Sec. 3 are grouped by similar family designations to ensure the completeness and consistency of assessments. The procedures have been derived from the assessment procedures in SP 800-53A [5]. Table 1."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to\nrespond to ITL calls for patents and ITL has not undertaken a patent search in order to identify\nwhich, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose\nuse may be required for compliance with the guidance or requirements of this publication, no\nsuch patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent\ninfringement in the use of this publication. v\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nNIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nDEVELOPING COMMON INFORMATION SECURITY AND PRIVACY FOUNDATIONS\nCOLLABORATION AMONG PUBLIC AND PRIVATE SECTOR ENTITIES\n\nIn developing standards and guidelines required by [FISMA], NIST consults with other federal agencies and\noffices as well as private sector entities to improve information security, avoid unnecessary and costly\nduplication of effort, and ensure that NIST publications complement the standards and guidelines\nemployed for the protection of national security systems. In addition to its comprehensive public review\nand vetting process, NIST collaborates with the Office of the Director of National Intelligence (ODNI), the\nDepartment of Defense (DoD), and the Committee on National Security Systems (CNSS) to establish and\nmaintain a unified framework and common foundation for information security across the Federal\nGovernment."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information.\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| | | 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 5)"}, {"role": "assistant", "content": "quirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.\n## Keywords\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors also wish to recognize the scientists, engineers, and research staff from the NIST Computer Security and the Applied Cybersecurity Divisions for their exceptional contributions in helping to improve the content of the publication. A special note of thanks to Pat O'Reilly, Jim Foti, Jeff Brewer, Chris Enloe, Ned Goren, and the entire NIST web team for their outstanding administrative support. Finally, the authors also gratefully acknowledge the contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nso develop and maintain procedures for particularly important processes that may be urgently needed during emergency situations, such as redeploying the organization's primary authentication platform.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------|\n| PR.AA (Identity Management, Authentication, and Access Control) | Access to physical and logical assets is limited to authorized users, services, and hardware and managed commensurate with the assessed risk of unauthorized access | Medium | N1: See the notes for PR. |\n| PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed by the organization | Medium | N1: See the notes for PR. |\n| PR.AA-02 | Identities are proofed and bound to credentials based on the context of interactions | Medium | N1: See the notes for PR."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 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 additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 18)"}, {"role": "assistant", "content": "P[06]: circumstances requiring users to log out of the system are defined . A.03.01.01.a[01]:\n\nA.03.01.01.a[02]:\n\nsystem account types allowed are defined. system account types prohibited are defined.\nA.03.01.01.b[01]: system accounts are created in accordance with organizational policy, procedures, prerequisites, and criteria. A.03.01.01.b[02]: system accounts are enabled in accordance with organizational policy, procedures, prerequisites, and criteria. A.03.01.01.b[03]: system accounts are modified in accordance with organizational policy, procedures, prerequisites, and criteria. A.03.01.01.b[04]: system accounts are disabled in accordance with organizational policy, procedures, prerequisites, and criteria. A.03.01.01.b[05]: system accounts are removed in accordance with organizational policy, procedures, prerequisites, and criteria. A.03.01.01.c.01: authorized users of the system are specified. A.03.01.01.c.02: group and role memberships are specified. A.03.01.01.c.03: access authorizations (i.e., privileges) for each account are specified. A.03.01.01.d.01: access to the system is authorized based on a valid access authorization. A.03.01.01.d.02: access to the system is authorized based on intended system usage. A.03.01.01.e: the use of system accounts is monitored. A.03.01.01.f.01: system accounts are disabled when the accounts have expired. A.03.01.01.f.02: system accounts are disabled when the accounts have been inactive for <A.03.01.01.ODP[01]: time period> . A.03.01.01.f.03: system accounts are disabled when the accounts are no longer associated with a user or individual. A.03.01.01.f.04: system accounts are disabled when the accounts violate organizational policy. A.03.01.01.f.05: system accounts are disabled when significant risks associated with individuals are discovered. A.03.01.01.g.01: account managers and designated personnel or roles are notified within <A.03.01.01.ODP[02]: time period> when accounts are no longer required."}], "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": 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 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 does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\ncurity officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control.\nAs we push computers to 'the edge,' building a complex world of interconnected information systems and devices, security and privacy risks (including supply chain risks) continue to be a large part of the national conversation and topics of great importance. The significant increase in the complexity of the hardware, software, firmware, and systems within the public and private sectors (including the U.S. critical infrastructure) represents a significant increase in attack surface that can be exploited by adversaries. Moreover, adversaries are using the supply chain as an attack vector and effective means of penetrating our systems, compromising the integrity of system elements, and gaining access to critical assets."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n## Incident Response Recommendations and Considerations for Cybersecurity Risk Management\n\n## Incident Response Recommendations and Considerations for Cybersecurity Risk Management\n\nNelson A, Rekhi S, Souppaya M, Scarfone K (2025) Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-61r3. https://doi.org/10.6028/NIST.SP.800-61r3"}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 14)"}, {"role": "assistant", "content": "ization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored. - Identify (ID): The organization's current cybersecurity risks are understood.\n- Protect (PR): Safeguards to manage the organization's cybersecurity risks are used. - Detect (DE): Possible cybersecurity attacks and compromises are found and analyzed. - Respond (RS): Actions regarding a detected cybersecurity incident are taken. - Recover (RC): Assets and operations affected by a cybersecurity incident are restored. All six Functions have vital roles in incident response. Govern, Identify, and Protect help organizations prevent some incidents, prepare to handle incidents that do occur, reduce the impact of those incidents, and improve incident response and cybersecurity risk management practices based on lessons learned. Detect, Respond, and Recover help organizations discover, manage, prioritize, contain, eradicate, and recover from cybersecurity incidents, as well as perform incident reporting, notification, and other incident-related communications. Fig. 2. Incident response life cycle model based on CSF 2.0 Functions\n\n\n\nThe bottom level reflects that the preparation activities of Govern, Identify, and Protect are not part of the incident response itself. Rather, they are much broader cybersecurity risk management activities that also support incident response. Incident response is shown in the top level of the figure: Detect, Respond, and Recover. Additionally, the need for continuous improvement is indicated as the middle level with the Improvement Category (ID.IM) within the Identify Function and the dashed green lines. Lessons learned from performing all activities in all Functions are fed into Improvement, and those lessons are analyzed, prioritized, and used to inform all of the Functions."}], "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": 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 Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 16)"}, {"role": "assistant", "content": "processing, storing, or transmitting CUI. The assessments focus on the overall effectiveness of the security safeguards intended to satisfy the enhanced security requirements defined in [SP 800-172].\n## 1.2 TARGET AUDIENCE\n\nThis publication serves system, information security, and privacy professionals, including individuals with:\n\n- System development responsibilities (e.g., program managers, system developers, system owners, systems integrators, system security engineers);\n- Information security assessment and monitoring responsibilities (e.g., system evaluators, assessors, independent verifiers/validators, auditors, analysts, system owners);\n- Information security, privacy, risk management, governance, and oversight responsibilities (e.g., authorizing officials, chief information officers, chief privacy officers, chief information security officers, system managers, information security managers); and\n- Information security implementation and operational responsibilities (e.g., system owners, information owners/stewards, mission and business owners, systems administrators, system security officers). ## 1.3 ORGANIZATION OF THIS SPECIAL PUBLICATION\n\nThe remainder of this special publication is organized as follows:\n\nChapter Two describes the fundamental concepts associated with assessments of CUI enhanced security requirements, including assessment procedures, methods, objects, and assurance cases that can be created using evidence produced during assessments. Chapter Three provides a catalog of assessment procedures for the CUI enhanced security requirements in [SP 800-172], including assessment objectives and potential assessment methods and objects for each procedure. Supporting appendices 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."}], "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": 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 guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide?"}, {"role": "assistant", "content": "\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Security and Privacy Controls for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by\nNIST in accordance with its assigned statutory responsibilities. The information in this publication,\nincluding concepts, practices, and methodologies may be used by federal agencies even before the\ncompletion of such companion publications. Thus, until each publication is completed, current\nrequirements, guidelines, and procedures, where they exist, remain operative. For planning and\ntransition purposes, federal agencies may wish to closely follow the development of these new\npublications by NIST. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 10)"}, {"role": "assistant", "content": "and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance.\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement. Tailoring: The process by which control baselines are modified to achieve certain organizational goals and objectives. Definitions provided are intended as plain language. Review the NIST Glossary for official NIST definitions. Determine if your business has CUI. ## General Tips for Getting Started with NIST SP 800-171\n\nEveryone will have different approaches to getting started, but here are a few tips to get you started down the right path:\n\nUnderstand current (or future) legal, regulatory, or contractual requirements for protecting CUI. The federal agency is responsible for communicating what CUI the business is responsible for protecting as part of the contractual arrangement. If there are questions, reach out to the contracting officer. The business may also have additional compliance requirements beyond SP 800-171. If so, an initial task might be to understand where the requirements overlap and where they differ. With that information, the business can begin addressing requirements that meet multiple compliance requirements. Understand how CUI flows into, within, and out of the business. \n\nInventorying what systems or components the business has, and how the data flows into, within, and out of those systems or components, helps practitioners understand the scope of applicability of SP 800-171 security requirements to business systems. \n\nScope and Applicability of SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n17 The Audit and Accountability, Maintenance, Media Protection, and Physical Protection families do not contain enhanced security requirements at this time.\n\n## 3.8 MEDIA PROTECTION"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 14)"}, {"role": "assistant", "content": "| | B.3 | BRECHAS SISTÉMICAS QUE AFECTAN A LA ZTA......................................................................................................65 | | | B.3.1 | Estandarización de las interfaces entre componentes.........................................................................65 | | | B.3.2 | Nuevas normas para hacer frente a la dependencia excesiva de las API propietarias.........................66 | | | B.4 | L AGUNAS EN EL CONOCIMIENTO DE LA ZTA Y FUTURAS ÁREAS DE INVESTIGACIÓN ........................................................66 | | | B.4.1 | Respuesta de los atacantes a la ZTA.....................................................................................................66 | | | B.4.2 | Experiencia del usuario en un entorno ZTA..........................................................................................67 | | | B.4.3 | Resiliencia de la ZTA ante las disrupciones de la empresa y la red ......................................................67 | | | B.5 | Referencias ................................................................................................................................................68 | | | Lista de figuras Figura 1: Accesos | de la confianza | cero..........................................................................................................................14 | | Figura 2: Componentes lógicos del núcleo de la confianza cero ..................................................................................19 | Figura 2: Componentes lógicos del núcleo de la confianza cero ..................................................................................19 | | | Figura 3: Modelo de agente y puerta de enlace de los dispositivos.............................................................................25 | Figura 3: Modelo de agente y puerta de enlace de los dispositivos.............................................................................25 | | | Figura 4: Modelo de puerta de enclave........................................................................................................................26 | Figura 4: Modelo de puerta de enclave........................................................................................................................26 | | | Figura 5:"}], "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": 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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 16)"}, {"role": "assistant", "content": "ategory) |\n| Post-Incident Activity | Identify (Improvement Category) |\n\nOrganizations should use the incident response life cycle framework or model that suits them best.\nThe model in this document is based on CSF 2.0 to take advantage of the wealth of resources available for CSF 2.0 and aid organizations that are already using the CSF. The appropriate incident response life cycle framework or model for an organization depends on many factors; for example, larger and more technology-dependent organizations are likely to benefit more from using a framework or model emphasizing continuous improvement than other organizations would. Regardless of the incident response life cycle framework or model used, every organization should take incident response into consideration throughout their cybersecurity risk management activities. ## 2.2. Incident Response Roles and Responsibilities\n\nIn the past, incident response activities were performed almost exclusively by incident handlers from the organization's own incident response team. Today, while incident handlers are still critically important, most organizations increasingly recognize that the success of their incident response efforts depend on the participation of many internal and external parties who hold a wide variety of roles and responsibilities and may be spread around the world. Roles and responsibilities will differ for each organization and may also differ within an organization based on the nature of a particular incident. Examples of incident response roles and responsibilities include the following:\n\n- Leadership . The organization's leadership team oversees incident response, allocates funding, and may have decision-making authority on high-impact response actions, such as shutting down or rebuilding critical services. - Incident handlers."}], "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": 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 3 require for Access Control?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n- Applying a threat-centric approach to security requirements specification;\n- Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16\n- Implementing dual authorization controls for the most critical or sensitive operations;\n- Limiting persistent storage to isolated enclaves or domains;\n- Implementing a comply-to-connect approach for systems and networks;\n- Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components;\n- Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components;\n- Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and\n- Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 12)"}, {"role": "assistant", "content": "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.\nIn this way, CSF 2.0 provides a common language that facilitates access to a large number of other resources. This publication supersedes SP 800-61r2 (Revision 2), Computer Security Incident Handling Guide [SP800-61r2]. ## 1.2. Document Structure\n\nThe remainder of this document is organized into the following sections and appendices:\n\n- Section 2 discusses how incident response has evolved to become a critical part of cybersecurity risk management, as well as how the concept of the incident response life cycle has changed to reflect that. - Section 3 presents incident response recommendations and considerations for an organization's cybersecurity risk management practices. They are organized and documented as a CSF 2.0 Community Profile. - The References section lists references cited throughout this publication. - Appendix A and Appendix B provide an acronyms list and a glossary, respectively. - Appendix C contains a change log of the major changes made since the previous revision. ## 2. Incident Response as Part of Cybersecurity Risk Management\n\nThis section explains the fundamental concepts of incident response as an integral part of cybersecurity risk management. Section 2.1 explores the incident response life cycle and proposes a new life cycle model based on CSF 2.0 Functions. Section 2.2 discusses incident response roles and responsibilities both inside and outside an organization. Finally, Section 2.3 briefly examines incident response policies, processes, and procedures. ## 2.1. Incident Response Life Cycle Model\n\nFig. 1 depicts the incident response life cycle model illustrated in the previous version of this publication [SP800-61r2]. Fig. 1."}], "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": 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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n- Technology professionals. Cybersecurity, privacy, system, network, cloud, and other technology architects, engineers, and administrators, as well as software developers, may be involved in incident response and recovery efforts. - Legal. Legal experts can review incident response plans, policies, and procedures to ensure compliance with applicable laws and regulations, including the right to privacy. Legal experts can also review contracts with technology suppliers and other third parties when there are incident response implications. In addition, incident responders can seek guidance from their organization's legal department if a particular incident may have legal ramifications, such as the prosecution of a suspect, lawsuits, or situations that require a memorandum of understanding (MOU) or other binding agreement. - Public affairs and media relations. Depending on the nature and impact of an incident, it may be necessary to inform the media and, by extension, the public. Sometimes, the media learns of incidents through alternate sources (i.e., not through public affairs personnel). Having a media engagement strategy in place can greatly aid in this situation."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nvia mutual Transport Layer Security (mTLS) when a service makes an initial connection establishment as part of its inter-service call. This authentication is not performed again in subsequent calls.\nHowever, the security of this operation is ensured by not allowing the connections to be very long (usually as long as the time to live [TTL] of the service's identity certificate or as short as 15-30 minutes, depending on the configuration)."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 Media Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| ACT-IAC | American Council for Technology and Industry Advisory Council. (2019). Zero Trust Cybersecurity Current Trends . Disponible en https://www.actiac.org/zero- trust-cybersecurity-current-trends |\n|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Anderson | Anderson B., McGrew D. (2017). Machine Learning for Encrypted Malware Traffic Classification: Accounting for Noisy Labels and Non- Stationarity. Proceedings of the 23rd ACMSIGKDD International Conference on Knowledge Discovery and Data Mining (ACM, Halifax, Nova Scotia, Canada), pp. 1723-1732. https://doi.org/10.1145/3097983.3098163 |\n| BCORE | Department of Defense CIO. (2007). Department of Defense Global Information Grid Architecture Vision Version 1.0 June 2007. Disponible en http://www.acqnotes.com/Attachments/DoD%20GIG%20Architectural% 20Vision,%20June%2007.pdf |\n| CSA-SDP | Cloud Security Alliance. (2015). SDP Specification 1.0. Disponible en https://cloudsecurityalliance.org/artifacts/sdp-specification-v1-0/ |\n| FIPS199 | National Institute of Standards and Technology. (2004). Standards for Security Categorization of Federal Information and Information Systems. (U."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "g/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-171r3. https://doi.org/10.6028/NIST.SP.800-171r3\n\n## Author ORCID iDs\n\nRon Ross: 0000-0002-1099-9757\n\nVictoria Pillitteri: 0000-0002-7446-7506\n\n## Submit Comments\n\n## 800-171comments@list.nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/171/r3/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe protection of Controlled Unclassified Information (CUI) is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides federal agencies with recommended security requirements for protecting the confidentiality of CUI when the information is resident in nonfederal systems and organizations. The requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. The security requirements are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations. This publication can be used in conjunction with its companion publication, NIST Special Publication 800-171A, which provides a comprehensive set of procedures to assess the security requirements."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nderal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?\n| The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. |\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nInformation technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .\nISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 8)"}, {"role": "assistant", "content": "e requirements also apply to services, including externally provided services, that process, store, or transmit CUI, or that provide security protections, for the system requiring enhanced protection.\nThe protection of a specific service to include CUI that is processed, stored or transmitted during the provision of that service, is achieved by implementing the enhanced security requirements for the service, or the system or system components responsible for providing that service. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. The term organizational system is used in many of the enhanced security requirements. It has a specific meaning regarding the applicability of the enhanced requirements as described above. Appropriate scoping considerations for the requirements are important factors in determining protection-related investment decisions and managing security risk for nonfederal organizations that have the responsibility of protecting CUI associated with critical programs and high value assets. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## FRAMEWORK FOR IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY\n\nOrganizations that have implemented or plan to implement the NIST Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 require for Physical Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\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...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 in Nonfederal Systems and Organizations provide? (Part 18)"}, {"role": "assistant", "content": "specific protection needs. The determination of ODP values can be guided and informed by laws, Executive Orders, directives, regulations, policies, standards, guidance, or mission and business needs.\nOnce specified, the values for the organizationdefined parameters become part of the requirement. ## ORGANIZATION-DEFINED PARAMETERS\n\nOrganization-defined parameters are an important part of a security requirement specification. ODPs provide both 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. In addition, ODPs support consistent security assessments in determining whether specified 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. A discussion section is included with each requirement. It is derived from the control discussion sections in SP 800-53 and provides additional information to facilitate the implementation and assessment of the requirements. The discussion section is informative, not normative. It is not intended to extend the scope of a requirement or influence the solutions that organizations may use to satisfy a requirement. The use of examples is notional, not exhaustive, and does not reflect the potential options available to organizations. A references section provides the source\n\n13 CP-09 and CP-09(08) are included by exception to ensure the confidentiality of backup information is projected. 14 NIST does not establish or assign values for ODPs. If ODP values for selected security requirements are not formally established or assigned by a federal agency or a consortium of federal agencies, nonfederal organizations must assign those values to complete the requirements."}], "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": 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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 13)"}, {"role": "assistant", "content": "...197 | |\n| D.1.1.3. Strategic Objectives............................................................................................................198 | |\n| D.1.1.4.\nImplementation Plan and Progress Tracking......................................................................199 | |\n| D.1.1.5. Roles and Responsibilities ..................................................................................................201 | |\n| D.1.1.6. Definitions ..........................................................................................................................202 | |\n| D.1.1.7. Revision and Maintenance.................................................................................................202 | |\n| D.2.1. C-SCRM Policy Template..........................................................................................................203 | |\n| D.2.1.1. Authority and Compliance..................................................................................................203 | |\n| D.2.1.2. Description .........................................................................................................................204 | |\n| D.2.1.3. Policy ..................................................................................................................................205 | |\n| D.2.1.4. Roles and Responsibilities ..................................................................................................206 | |\n| D.2.1.5. Definitions ..........................................................................................................................207 | |\n| D.2.1.6. Revision and Maintenance.................................................................................................207 | |\n| D.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": 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 Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nEl NCPS (por su nombre en inglés National Cybersecurity Protection System y conocido operativamente como Einstein) es un sistema integrado que incluye subsistemas. Este ofrece servicios de detección de intrusiones, análisis avanzados, intercambio de información y prevención de intrusiones para defender al Gobierno Federal de las ciberamenazas. Los objetivos del NCPS, que se alinean con los objetivos generales de la confianza cero, consisten en gestionar el riesgo cibernético, mejorar la ciberprotección y capacitar a los socios para asegurar el ciberespacio. Los sensores de Einstein permiten al Centro Nacional de Integración de la Ciberseguridad y las Comunicaciones (NCCIC, por su nombre en inglés National Cybersecurity and Communications Integration Center) de la Agencia de Seguridad de Infraestructura y Ciberseguridad CISA (por su nombre en inglés Cybersecurity and Infrastructure Security Agency) responder a incidentes significativos en las agencias federales y defender sus redes."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. This publication provides security and privacy control baselines for the Federal Government. There are three security control baselines (one for each system impact level-low-impact, moderate-impact, and high-impact), as well as a privacy baseline that is applied to systems irrespective of impact level. In addition to the control baselines, this publication provides tailoring guidance and a set of working assumptions that help guide and inform the control selection process."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n## Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations\n\n## Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations\n\nBoyens J, Smith A, Bartol N, Winkler K, Holbrook A, Fallon M (2022) Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-161r1-upd1, Includes updates as of Novem ber 1, 2024. https://doi.org/10.6028/NIST.SP.800-161r1-upd1"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nINCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XI\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nor mobile devices/systems, do not require a separate risk management process but rather a tailored set of controls and specific implementation details determined by applying the existing RMF process.\n1 An information system is a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information [44 USC 3502]. The term information system includes, for example, general-purpose computing systems; industrial/process control systems; cyber-physical systems; weapons systems; super computers; command, control, and communications systems; devices such as smart phones and tablets; environmental control systems; embedded devices/sensors; and paper-based systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 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 does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nassessments. Such collaboration helps organizations leverage information from providers, reduce redundancy, identify potential courses of action for risk responses, and reduce the burden on providers.\nExamples of different types of descriptive information that organizations can include in security and privacy plans include: descriptive name of the system and system identifier; system version or release number; manufacturer and supplier information; individual responsible for the system; system contact information; organization that manages, owns, or controls the system; system location; purpose of the system and missions/business processes supported; how the system is integrated into the enterprise architecture; SDLC phase; results of the categorization process and privacy risk assessment; authorization boundary; laws, directives, policies, regulations, or standards affecting individuals' privacy and the security of the system; architectural description of the system including network topology; information types; hardware, firmware, and software components that are part of the system; hardware, software, and system interfaces (internal and external); information flows within the system; network connection rules for communicating with external systems; interconnected systems and identifiers for those systems; physical or other processes, components and equipment controlled by system elements; system users (including affiliations, access rights, privileges, citizenship); system provenance in the supply chain; maintenance or other relevant agreements; potential suppliers for replacement components for the system; alternative compatible system components; number and location in inventory of replacement system components; ownership or operation of the system (government-owned, government-operated; government-owned, contractor-operated; contractor-owned, contractor-operated; nonfederal [state and local governments, grantees]); incident response points of contact; authorization date and authorization termination date; and ongoing authorization status."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT).\nITL’s responsibilities include the development\nof management, administrative, technical, and physical standards and guidelines for the cost-\neffective security of other than national security-related information in federal information\nsystems. The Special Publication 800-series reports on ITL’s research, guidelines, and outreach\nefforts in information systems security and privacy and its collaborative activities with industry,\ngovernment, and academic organizations. Abstract\n\nThis publication provides a catalog of security and privacy controls for information systems and\norganizations to protect organizational operations and assets, individuals, other organizations,\nand the Nation from a diverse set of threats and risks, including hostile attacks, human errors,\nnatural disasters, structural failures, foreign intelligence entities, and privacy risks. The controls\nare flexible and customizable and implemented as part of an organization-wide process to\nmanage risk. The controls address diverse requirements derived from mission and business\nneeds, laws, executive orders, directives, regulations, policies, standards, and guidelines. Finally,\nthe consolidated control catalog addresses security and privacy from a functionality perspective\n(i.e., the strength of functions and mechanisms provided by the controls) and from an assurance\nperspective (i.e., the measure of confidence in the security or privacy capability provided by the\ncontrols). Addressing functionality and assurance helps to ensure that information technology\nproducts and the systems that rely on those products are sufficiently trustworthy."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 18)"}, {"role": "assistant", "content": "rses, 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.\n## Related Resources:\n\n- View all SP 800-171 Awareness and Training Requirements and Assessment Procedures\n- NIST Free and Low-Cost Online Cybersecurity Learning Content\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n- NARA CUI training\n- Center for Development of Security Excellence Security Awareness Hub\n\n81&/$66,),('GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1)250$7,21GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1\n\n\n\n## Getting Started with Audit and Accountability\n\n## Family: Audit and Accountability\n\nDescription: Creating, protecting, and retaining system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity; and ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. ## Getting Started with Audit and Accountability\n\n\n\nUnderstand and track who is performing actions within business system(s), what those actions are, and when those actions are taken. Having the ability to review system activity and analyze records, generate reports, resolve audit log process failures, and protect audit data gives the business insight into potential unauthorized activity and improves the ability to respond quickly and appropriately. Consider automated tools for conducting audit and logging activities. Products range from free, open-source tools to commercially available ones. ## Define, maintain, and protect 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."}], "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": 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": "How does Assessing Enhanced Security Requirements for Controlled Unclassified Information support CMMC certification?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nlar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172A Natl. Inst. Stand. Technol. Spec. Publ. 800-172A, 62 pages (March 2022)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 14)"}, {"role": "assistant", "content": "..................................................... 50 | APPENDIX C MAPPINGTABLES ....................................................................................................\n50 |\n| APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 | APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 |\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Errata\n\nThis table contains changes that have been incorporated into Special Publication 800-172. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. Any potential updates for this 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 the SP 800-172 publication details. | DATE | TYPE | CHANGE | PAGE |\n|--------|--------|----------|--------|\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## CHAPTER ONE\n\n## INTRODUCTION\n\nTHE NEED TO PROTECT CONTROLLED UNCLASSIFIED INFORMATION\n\noday, 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."}], "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": 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 Configuration Management?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes | |---------------|-----------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 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": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to 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 does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n8 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products).\nSince many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 16)"}, {"role": "assistant", "content": "| |\n| D.3.1.14.\nAttachments.....................................................................................................................216 | |\n| D.3.1.15. C-SCRM Plan and Life Cycles ............................................................................................216 | |\n| D.4.1. C-SCRM Template ....................................................................................................................218 | |\n| D.4.1.1. Authority and Compliance..................................................................................................218 | |\n| D.4.1.2."}], "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": 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 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 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 Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Access Control\n\n## Getting Started with Access Control"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nne or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control.\n- Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 14)"}, {"role": "assistant", "content": ".................207 | |\n| D.2.1.6. Revision and Maintenance.................................................................................................207 | |\n| D.3.1.\nC-SCRM Plan Template ............................................................................................................209 | |\n| D.3.1.1. System Name and Identifier...............................................................................................209 | |\n| D.3.1.2. System Description.............................................................................................................209 | |\n| D.3.1.3. System Information Type and Categorization....................................................................210 | |\n| D.3.1.4. System Operational Status.................................................................................................211 | |\n| D.3.1.5. System/Network Diagrams, Inventory, and Life Cycle Activities .......................................211 | |\n| D.3.1.6. Information Exchange and System Connections................................................................212 | |\n| D.3.1.7. Security Control Details......................................................................................................212 | |\n| D.3.1.8. Role Identification ..............................................................................................................213 | |\n| D.3.1.9. Contingencies and Emergencies.........................................................................................214 | |\n| D.3.1.10. Related Laws, Regulations, and Policies...........................................................................215 | |\n\n| D.3.1.11."}], "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": 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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 11)"}, {"role": "assistant", "content": "| 9 | | | Multi-Tier Policies for ZTA for Cloud-Native Application | | | | Implementing Environments ..........................................................................................................................................12 | Implementing Environments ..........................................................................................................................................12 | | | Reference Application Infrastructure Scenario...........................................................12 | | | | Role of the Service Mesh in Policy Deployment, Enforcement, and Updates.............13 | | | | Policy Deployment for Reference Application Infrastructure.......................................14 | | | | Another Application Infrastructure Scenario...............................................................15 | | | | Functional Roles of Application Infrastructure Elements in Enforcing Policies ...........16 | | | | Comparison of Identity-Tier and Network-Tier Policies | ..............................................17 | | 4.6.1."}], "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": 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 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 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\nte 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.\nWhile encryption could prevent unauthorized disclosure of PII, it would not address any privacy risks related to disclosures to parties that are authorized to decrypt and access the PII. To mitigate this privacy risk, organizations would need to assess the risk of allowing authorized parties to decrypt the information and potentially select controls that would mitigate that risk. In such an example, an organization might select controls to enable individuals to understand the organization's disclosure practices and exercise choices about this access or use differential privacy or privacy-enhancing cryptographic techniques to disassociate the information from an individual."}], "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 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 does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 13)"}, {"role": "assistant", "content": "i\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.\n5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nExecutive Summary\n\nSecurity and privacy control assessments are not about checklists, simple pass/fail results, or\ngenerating paperwork to pass inspections or audits. Rather, control assessments are the\nprincipal vehicle used to verify that selected security and privacy controls are implemented and\nmeeting stated goals and objectives. Special Publication (SP) 800-53A, Assessing Security and\nPrivacy Controls in Information Systems and Organizations, facilitates security control\nassessments and privacy control assessments conducted within an effective risk management\nframework. A major design objective for SP 800-53A is to provide an assessment framework and\ninitial starting point for assessment procedures that are flexible enough to meet the needs of\ndifferent organizations while providing consistency in conducting control assessments. Control\nassessment results provide organizational officials with:\n\n• Evidence of the effectiveness of implemented controls,\n• An indication of the quality of the risk management processes, and\n•\n\nInformation about the security and privacy strengths and weaknesses of systems that\nare supporting organizational missions and business functions. The findings identified by assessors are used to determine the overall effectiveness of security\nand privacy controls associated with systems and their environments of operation and to\nprovide credible and meaningful inputs to the organization’s risk management process."}], "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": 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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 5)"}, {"role": "assistant", "content": "quirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.\n## Keywords\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors also wish to recognize the scientists, engineers, and research staff from the NIST Computer Security and the Applied Cybersecurity Divisions for their exceptional contributions in helping to improve the content of the publication. A special note of thanks to Pat O'Reilly, Jim Foti, Jeff Brewer, Chris Enloe, Ned Goren, and the entire NIST web team for their outstanding administrative support. Finally, the authors also gratefully acknowledge the contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 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 Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| ...................................................................................................\n3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "................................3 | 2. The Fundamentals.....................................................................................................................3 |\n| 3.\nThe Security Requirements........................................................................................................6 | 3. The Security Requirements........................................................................................................6 | 3. The Security Requirements........................................................................................................6 |\n| References.......................................................................................................................................75 | References.......................................................................................................................................75 | References.......................................................................................................................................75 |\n| Appendix A. | Acronyms ................................................................................................................83 | |\n| Appendix B. | Glossary...................................................................................................................85 | |\n| Appendix C."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.3. 3.1.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 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": "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 Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nInformation security programs are responsible for protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction (i.e., unauthorized system activity or behavior) in order to provide confidentiality, integrity, and availability. Privacy programs are responsible for managing the risks to individuals associated with the creation, collection, use, processing, dissemination, storage, maintenance, disclosure, or disposal (collectively referred to as 'processing') of personally identifiable information (PII) and for ensuring compliance with applicable privacy requirements. 11 When a system processes PII, the information security and privacy programs have a shared responsibility to manage the impacts to individuals that arise from security risks and collaborate to determine the security categorization and the selection and tailoring of controls from the security control baselines."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 19)"}, {"role": "assistant", "content": "| PROGRAMMANAGEMENTFAMILY .......................................................................................\n| 37 |\n| 3.14 | PERSONNEL SECURITY FAMILY .............................................................................................. | 39 |\n| 3.15 | PERSONALLY IDENTIFIABLEINFORMATIONPROCESSINGANDTRANSPARENCYFAMILY ............. | 40 |\n| 3.16 | RISKASSESSMENT FAMILY .................................................................................................... | 41 |\n| 3.17 | SYSTEMANDSERVICESACQUISITION FAMILY ........................................................................."}], "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": 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 Planning?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n.............................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..............................................................................\n8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................. 18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE ...................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Assessing Security Requirements for Controlled Unclassified Information support CMMC certification?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171Ar3\n\n\n\n## NIST Special Publication\n\n## NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-171Ar3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n8 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products).\nSince many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nA CSF Community Profile is a baseline of CSF outcomes that is created and published to address shared interests and goals for reducing cybersecurity risk among a number of organizations. A Community Profile is typically developed for a particular sector, subsector, technology, threat type, or other use case [CSF2.0]."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "blication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n## Audience\n\nThis publication serves a diverse group of individuals and organizations in the public and private sectors, including:\n\n- Federal agencies responsible for managing and protecting CUI\n- Nonfederal organizations responsible for protecting CUI\n- Individuals with system development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Individuals with acquisition or procurement responsibilities (e.g., contracting officers)\n- Individuals with system, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Individuals with security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, analysts, independent verifiers and validators)\n\nThe above roles and responsibilities can be viewed from two perspectives:\n\n- Federal perspective : The entity establishing and conveying the security requirements in contractual vehicles or other types of agreements\n- Nonfederal perspective : The entity responding to and complying with the security requirements set forth in contracts or agreements\n\n## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information.\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nthe Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies.\nThe scope of this publication pertains to federal information systems, which are discrete sets of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information, whether such information is in digital or non-digital form. Information resources include information and related resources, such as personnel, equipment, funds, and information technology."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nbust and comprehensive information security and privacy risk\nmanagement programs can facilitate compliance with applicable laws, regulations, executive\norders, and governmentwide policies.\nRisk management frameworks and risk management\nprocesses are essential in developing, implementing, and maintaining the protection measures\nnecessary to address stakeholder needs and the current threats to organizational operations\nand assets, individuals, other organizations, and the Nation. Employing effective risk-based\nprocesses, procedures, methods, and technologies ensures that information systems and\norganizations have the necessary trustworthiness and resiliency to support essential mission and\nbusiness functions, the U.S. critical infrastructure, and continuity of government."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control. 9 Reciprocity is an agreement between organizations to accept one another's security assessment results in order to reuse system resources or to accept each other's assessed security posture in order to share information. 10 [SP 800-64] and [SP 800-160 v1] provide guidance on security considerations in the SDLC. Organizations may choose to divide security and privacy requirements into more granular categories depending on where the requirements are employed in the SDLC and for what purpose. Organizations may use the term capability requirement to describe a capability that the system or organization must provide to satisfy a stakeholder protection need. In addition, organizations may refer to system requirements that pertain to particular hardware, software, and firmware components of a system as specification requirements -that is, capabilities that implement all or part of a control and that may be assessed (i.e., as part of the verification, validation, testing, and evaluation processes)."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication describes the Risk Management Framework (RMF) and provides guidelines for applying the RMF to information systems and organizations. The RMF provides a disciplined, structured, and flexible process for managing security and privacy risk that includes information security categorization; control selection, implementation, and assessment; system and common control authorizations; and continuous monitoring. The RMF includes activities to prepare organizations to execute the framework at appropriate risk management levels. The RMF also promotes near real-time risk management and ongoing information system and common control authorization through the implementation of continuous monitoring processes; provides senior leaders and executives with the necessary information to make efficient, cost-effective, risk management decisions about the systems supporting their missions and business functions; and incorporates security and privacy into the system development life cycle. Executing the RMF tasks links essential risk management processes at the system level to risk management processes at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication contains comprehensive updates to the Risk Management Framework . The updates include an alignment with the constructs in the NIST Cybersecurity Framework; the integration of privacy risk management processes; an alignment with system life cycle security engineering processes; and the incorporation of supply chain risk management processes. Organizations can use the frameworks and processes in a complementary manner within the RMF to effectively manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. Revision 2 includes a set of organization-wide RMF tasks that are designed to prepare information system owners to conduct system-level risk management activities. The intent is to increase the effectiveness, efficiency, and cost-effectiveness of the RMF by establishing a closer connection to the organization's missions and business functions and improving the communications among senior leaders, managers, and operational personnel. assess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "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": 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 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 does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 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 additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 15)"}, {"role": "assistant", "content": "y of sources and conducting different types of activities during an assessment. An assurance case is a body of evidence organized into an argument demonstrating that some claim about a system is true.\nFor security assessments conducted using the procedures in this publication, that claim is 'compliance' with the security requirements in SP 800-171. Assessors obtain evidence during security assessments to allow designated officials 4 to make objective determinations about compliance with the security requirements. The evidence needed to make such determinations can be obtained from various sources, including independent, third-party assessments or other types of assessments, depending on the needs of the organization establishing the requirements and the organization conducting the assessments. For example, many technical security requirements are satisfied by security capabilities that are examine the security functions of products and established configuration settings. Assessments built into commercial information technology products and systems. Product assessments are typically conducted by independent, third-party testing organizations. 5 These assessments can also be conducted to demonstrate compliance with industry, national, or international security standards as well as developer and vendor claims. Since many information technology\n\n4 A designated official is an official, either internal or external to a nonfederal organization, with the responsibility to determine organizational compliance with the security requirements. 5 Examples of third-party testing organizations include Common Criteria Testing Laboratories that evaluate IT products in accordance with ISO/IEC 15408 [6] and Cryptographic Module Validation Program Testing Laboratories that evaluate cryptographic modules in accordance with Federal Information Processing Standard (FIPS) 140 [7]."}], "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": 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 does CMMC require for Security Assessment?"}, {"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 |\n|------------------|-------------------------------------------------------|----------------------------|------------------------------|------------------------------|------------------------------|\n| CONTROL NUMBER | CONTROL NAME CONTROL ENHANCEMENT NAME | PRIVACY CONTROL BASELINE | LOW | MOD | HIGH |\n| CA-1 | Policy and Procedures | x | x | x | x |\n| CA-2 | Control Assessments | x | x | x | x |\n| CA-2(1) | INDEPENDENT ASSESSORS | | | x | x |\n| CA-2(2) | SPECIALIZED ASSESSMENTS | | | | x |\n| CA-2(3) | LEVERAGING RESULTS FROM EXTERNAL ORGANIZATIONS | | | | |\n| CA-3 | Information Exchange | | x | x | x |\n| CA-3(1) | UNCLASSIFIED NATIONAL SECURITY SYSTEM CONNECTIONS | W: Moved to SC-7(25). | W: Moved to SC-7(25). | W: Moved to SC-7(25). | W: Moved to SC-7(25)."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "tise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D.\nThe controls described assist organizations in defining the controls needed to satisfy minimum assurance requirements. Where additional assurance is desired to achieve risk management objectives, Table E-4 provides additional security controls and control enhancements to achieve enhanced assurance. Implementers should note that designation of assurance-related controls is not intended to imply a greater level of importance for such controls. Achieving adequate security for organizational information systems requires the correct combination of both functionality- and assurance-related security controls. ## 6 Security Controls\n\nAppendix F, the Security Control Catalog, provides a comprehensive range of countermeasures for organizations and information systems. The security controls are designed to be technologyneutral such that the focus is on the fundamental countermeasures needed to protect organizational information during processing, storage, or transmission. SP 800-53 Rev. 4, therefore, does not provide guidance on the application of security controls to specific technologies, environments of operation, or missions/business functions. These specific areas may be addressed using overlays (see below). Control enhancements are included with many security controls and are selected in order to increase the strength of the base control. Control enhancements are intended to be implemented only in conjunction with implementation of the base control. Some security controls and control enhancements include one or more assignment and selection statements. These are variable parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nuld be developed for narrower audiences, such as federal agencies, small businesses, or educational institutions. For more information on CSF 2.0 Community Profiles, see the Framework Resource Center.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------|\n| PR.AA (Identity Management, Authentication, and Access Control) | Access to physical and logical assets is limited to authorized users, services, and hardware and managed commensurate with the assessed risk of unauthorized access | Medium | N1: See the notes for PR. |\n| PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed by the organization | Medium | N1: See the notes for PR. |\n| PR.AA-02 | Identities are proofed and bound to credentials based on the context of interactions | Medium | N1: See the notes for PR."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nother than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 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 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": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\naft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 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 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 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 Control Baselines for Information Systems and Organizations provide? (Part 15)"}, {"role": "assistant", "content": "| CONTROLBASELINE ASSUMPTIONS ...........................................................................................\n| 8 |\n| 2.4 | TAILORING CONTROLBASELINES .............................................................................................. | 9 |\n| 2.5 | CAPABILITIES ......................................................................................................................... | 14 |\n| CHAPTER THREE THECONTROLBASELINES................................................................................. | CHAPTER THREE THECONTROLBASELINES................................................................................. | 15 |\n| 3.1 | ACCESSCONTROLFAMILY ......................................................................................................"}], "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": 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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | ## 1 Introduction In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800\n\n## NIST SP 800-161r1-upd1\n\n## Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations\n\nJon Boyens Angela Smith Nadya Bartol Kris Winkler Alex Holbrook Matthew Fallon\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n\n\n\n## NIST Special Publication 800 NIST SP 800-161r1-upd1\n\n## Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations\n\nJon Boyens Angela Smith Computer Security Division Information Technology Laboratory\n\nNadya Bartol Kris Winkler Alex Holbrook Matthew Fallon Boston Consulting Group\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n\nMay 2022\n\nINCLUDES UPDATES AS OF 1 1 -01 -2024; SEE APPENDIX K\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nLaurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 6)"}, {"role": "assistant", "content": "curity 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\n## Acknowledgements\n\nThis publication was developed by the Joint Task Force Interagency Working Group. The group includes representatives from the Civil, Defense, and Intelligence Communities. The National Institute of Standards and Technology wishes to acknowledge and thank the senior leaders from the Departments of Commerce and Defense, the Office of the Director of National Intelligence, the Committee on National Security Systems, and the members of the interagency working group whose dedicated efforts contributed significantly to the publication. ## Department of Defense\n\n## Office of the Director of National Intelligence\n\nJohn Sherman\n\nDana Deasy\n\nChief Information Officer\n\nChief Information Officer\n\nEssye B. Miller\n\nVacant\n\nPrincipal Deputy CIO and DoD Senior Information Security Officer\n\nDeputy Chief Information Officer\n\nThomas P. Michelli\n\nSusan Dorr\n\nActing Deputy Chief Information Officer for Cybersecurity\n\nDirector, Cybersecurity Division and Chief Information Security Officer\n\nVicki Michetti\n\nWallace Coggins\n\nDirector, Cybersecurity Policy, Strategy, International, and Defense Industrial Base Directorate\n\nDirector, Security Coordination Center\n\n## National Institute of Standards and Technology\n\n## Committee on National Security Systems\n\nCharles H."}], "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": 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 Configuration Management?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\norganizations. It provides guidance for\ntailoring control baselines and for developing overlays to support the security and privacy\nrequirements of stakeholders and their organizations.\nCNSS Instruction 1253 provides control\nbaselines and guidance for security categorization and security control selection for national\nsecurity systems."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nne or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control.\n- Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 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 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 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 AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n3.2.1 DETERMINE WHICH SECURITY AND PRIVACY CONTROLS ARE TO BE ASSESSED\n\nThe security plan and privacy plan provide an overview of the security and privacy requirements\nfor the system and organization and describe the security controls and privacy controls in place\nor planned for meeting those requirements."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 11)"}, {"role": "assistant", "content": "......................................................136 | |\n| A.2.20.\nFAMILY: SYSTEM AND COMMUNICATIONS PROTECTION .....................................................147 | |\n| A.2.21. FAMILY: SYSTEM AND INFORMATION INTEGRITY .................................................................153 | |\n| A.2.22. FAMILY: SUPPLY CHAIN RISK MANAGEMENT........................................................................157 | |\n| B. C-SCRM Control Summary............................................................................................ | 164 |\n| Appendix Appendix C. RISK EXPOSURE | FRAMEWORK...................................................................................... 172 |\n| C.1.1. SCENARIO 1: Influence or Control by Foreign Governments Over Suppliers...........................177 | |\n\n| C.1.2."}], "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": 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 Assessing Security and Privacy Controls in Information Systems and Organizations:\n\ngs and relationships between the security standards and guidelines developed by NIST, the\nInternational Organization for Standardization (ISO), and the International Electrotechnical Commission\n(IEC).\nIdentify determination statements for organization-defined parameters (ODPs) first and separately\nfrom the determination statements for each control item;\nImprove the readability of the assessment procedures;\nProvide a structured schema for automated tools when assessment information is imported into such\ntools;\nProvide greater flexibility in conducting assessments by giving organizations the capability to target\ncertain aspects of controls (highlighting the particular weaknesses and/or deficiencies in controls),\nImprove the efficiency of security and privacy control assessments;\nSupport continuous monitoring and ongoing authorization programs by providing a greater number\nof component parts of security and privacy controls that can be assessed at organization-defined\nfrequencies and degrees of rigor."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 10)"}, {"role": "assistant", "content": "and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance.\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement. Tailoring: The process by which control baselines are modified to achieve certain organizational goals and objectives. Definitions provided are intended as plain language. Review the NIST Glossary for official NIST definitions. Determine if your business has CUI. ## General Tips for Getting Started with NIST SP 800-171\n\nEveryone will have different approaches to getting started, but here are a few tips to get you started down the right path:\n\nUnderstand current (or future) legal, regulatory, or contractual requirements for protecting CUI. The federal agency is responsible for communicating what CUI the business is responsible for protecting as part of the contractual arrangement. If there are questions, reach out to the contracting officer. The business may also have additional compliance requirements beyond SP 800-171. If so, an initial task might be to understand where the requirements overlap and where they differ. With that information, the business can begin addressing requirements that meet multiple compliance requirements. Understand how CUI flows into, within, and out of the business. \n\nInventorying what systems or components the business has, and how the data flows into, within, and out of those systems or components, helps practitioners understand the scope of applicability of SP 800-171 security requirements to business systems. \n\nScope and Applicability of SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 5)"}, {"role": "assistant", "content": "quirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.\n## Keywords\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors also wish to recognize the scientists, engineers, and research staff from the NIST Computer Security and the Applied Cybersecurity Divisions for their exceptional contributions in helping to improve the content of the publication. A special note of thanks to Pat O'Reilly, Jim Foti, Jeff Brewer, Chris Enloe, Ned Goren, and the entire NIST web team for their outstanding administrative support. Finally, the authors also gratefully acknowledge the contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nuirements. When deciding whether to require and implement C-SCRM practices and controls, acquirers should consider both the costs of implementing these controls and the risks of not implementing them.\napplicable existing data and documentation that may provide evidence\n\n| Levels | Level Name | Generic Stakeholder | Activities |\n|----------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 3 | Operational | Systems Management: Architects, developers, system owners, QA/QC, testing, contracting personnel, C-SCRM PMO staff, control engineer and/or control system operator, etc. | • Develop C-SCRM plans. • Implement C-SCRM policies and requirements. • Adhere to constraints provided by Level 1 and Level 2. • Tailor C-SCRM to the context of the individual system, and apply it throughout the SDLC. • Report on C-SCRM to Level 2. |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 8)"}, {"role": "assistant", "content": "Barrett, Kathleen Coupe, Jeff Eisensmith, Chris Enloe, Ned Goren, Matthew Halstead, Jody Jacobs, Ralph Jones, Martin Kihiko, Raquel Leone, and the scientists, engineers, and research staff from the Computer Security Division and the Applied Cybersecurity Division for their exceptional contributions in helping to improve the content of the publication."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["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 require for Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nSecurity and privacy control assessments are not about checklists, simple pass/fail results, or\ngenerating paperwork to pass inspections or audits. Rather, control assessments are the\nprincipal vehicle used to verify that selected security and privacy controls are implemented and\nmeeting stated goals and objectives. Special Publication (SP) 800-53A, Assessing Security and\nPrivacy Controls in Information Systems and Organizations, facilitates security control\nassessments and privacy control assessments conducted within an effective risk management\nframework. A major design objective for SP 800-53A is to provide an assessment framework and\ninitial starting point for assessment procedures that are flexible enough to meet the needs of\ndifferent organizations while providing consistency in conducting control assessments. Control\nassessment results provide organizational officials with:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nOrganizations must exercise due diligence in managing information security and privacy risk. This is accomplished, in part, by establishing a comprehensive risk management program that uses the flexibility inherent in NIST publications to categorize systems, select and implement security and privacy controls that meet mission and business needs, assess the effectiveness of the controls, authorize the systems for operation, and continuously monitor the systems. Exercising due diligence and implementing robust and comprehensive information security and privacy risk management programs can facilitate compliance with applicable laws, regulations, executive orders, and government-wide policies. Risk management frameworks and risk management processes are essential in developing, implementing, and maintaining the protection measures necessary to address stakeholder needs and the current threats to organizational operations and assets, individuals, other organizations, and the Nation. Employing effective risk-based processes, procedures, methods, and technologies ensures that information systems and organizations have the necessary trustworthiness and resiliency to support essential mission and business functions, the U.S. critical infrastructure, and continuity of government. '…The Task Force notes that the cyber threat to U.S. critical infrastructure is outpacing efforts to reduce pervasive vulnerabilities, so that for the next decade at least the United States must lean significantly on deterrence to address the cyber threat posed by the most capable U.S. adversaries. It is clear that a more proactive and systematic approach to U.S. cyber deterrence is urgently needed…'\n\nThe security and privacy controls specified in the baselines represent the state-of-the-practice protection measures for individuals, information systems, and organizations."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 19)"}, {"role": "assistant", "content": "d with individuals are discovered. A.03.01.01.g.01: account managers and designated personnel or roles are notified within <A.03.01.01.ODP[02]: time period> when accounts are no longer required.\nA.03.01.01.g.02: account managers and designated personnel or roles are notified within <A.03.01.01.ODP[03]: time period> when users are terminated or transferred. A.03.01.01.g.03: account managers and designated personnel or roles are notified within <A.03.01.01.ODP[04]: time period> when system usage or the need-to-know changes for an individual. A.03.01.01.h: users are required to log out of the system after <A.03.01.01.ODP[05]: time period> of expected inactivity or when the following circumstances occur: <A.03.01.01.ODP[06]: circumstances> ."}], "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": 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 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 3)"}, {"role": "assistant", "content": "The guide was developed and is maintained by the Joint Task Force Transformation Initiative Interagency Working Group, part of an ongoing information security partnership among the U.S. Department of Defense, the Intelligence Community, the Committee on National Security Systems, the Department of Homeland Security, and U.S. federal civil agencies. SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. SP 800-53 Revision 4 is part of the NIST Special Publication 800-series that reports on the NIST Information Technology Laboratory's (ITL) computer security-related research, guidelines, and outreach. The publication provides a comprehensive set of security controls, three security control baselines (low, moderate, and high impact), and guidance for tailoring the appropriate baseline to specific needs according to the organization's missions, environments of operation, and technologies used. As the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 12)"}, {"role": "assistant", "content": "Over Suppliers...........................177 | |\n\n| C.1.2.\nSCENARIO 2: Telecommunications Counterfeits......................................................................181 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| C.1.3. SCENARIO 3: Industrial Espionage............................................................................................184 | |\n| C.1.4. SCENARIO 4: Malicious Code Insertion ....................................................................................188 | |\n| C.1.5. SCENARIO 5: Unintentional Compromise ................................................................................190 | |\n| C.1.6. SCENARIO 6: Vulnerable Reused Components Within Systems ..............................................193 | |\n| Appendix D. C-SCRM Templates....................................................................................................... | 196 |\n| D.1.1. C-SCRM Strategy and Implementation Plan Template............................................................196 | |\n| D.1.1.1. Purpose...............................................................................................................................196 | |\n| D.1.1.2. Authority and Compliance..................................................................................................197 | |\n| D.1.1.3. Strategic Objectives............................................................................................................198 | |\n| D.1.1.4."}], "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": 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 Planning?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ..................................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 4)"}, {"role": "assistant", "content": "additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process.\nThe baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . A separate guideline, SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, provides specific guidelines that facilitate periodic assessment of security controls to ensure that controls have been implemented correctly, are operating as intended, and are meeting the organization's security requirements. ## 2 NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)\n\nNIST SP 800-39, Managing Information Security Risk , defines risk management as 'the program and supporting processes to manage information security risk to organizational operations (including mission, functions, and reputation), organizational assets, individuals, other organizations, and the Nation'. To integrate the risk management process throughout an organization and to address its mission and business concerns, a three-tiered approach is employed. The process is carried out across three tiers with the objective of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Risk Assessment?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nence is urgently needed…'\n\nThe security and privacy controls specified in the baselines represent the state-of-the-practice protection measures for individuals, information systems, and organizations.\nThe controls comprising the baselines are periodically reviewed and revised to reflect the experience gained from using the controls; new or revised laws, executive orders, directives, regulations, policies, and standards; changing security and privacy requirements; emerging threats, vulnerabilities, attacks, and information processing methods; and the availability of new technologies. Thus, the security and privacy controls specified in the baselines are also expected to change over time as controls are withdrawn, revised, and added. In addition to the need for change, the need for stability is addressed by requiring that proposed changes to the baseline undergo a rigorous and transparent public review process to obtain public and private sector feedback and to build a consensus for baseline changes. The public review process provides a stable, flexible, and technically sound set of security and privacy control baselines."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nInformation technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .\nISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nEach service mesh instance has two main logical components: 1) a control plane that implements the APIs needed to define various configurations and policies that govern access between various microservices in that cluster and 2) a data plane that enforces those policies at runtime. However, a uniform set of policies is also needed to govern access between any pair of microservices or services in the enterprise irrespective of their location or the service mesh instance of which they are a part. This requires a global control plane that can define a uniform set of policies applicable to the entire set of services that operate in the enterprise and disseminate them to the control planes of the individual service mesh instances. It is technically possible to have a single service mesh control plane instance (i.e., single service mesh instance) that manages multiple clusters spanning multiple environments (i.e., on-premises and on clouds). However, this architecture may make the multiple clusters a single failure domain and potentially defeat the very purpose of designing a multi-cluster configuration (i.e., availability). Thus, running a service mesh control plane instance for each cluster isolates the failure domain and improves availability and scalability. Further, providing the required underlying network connectivity to facilitate every workload (since each workload or application instance has an associated sidecar proxy that forms the data plane) to communicate with a single\n\nNote on the above recommendation: In an ideal situation, services would be authenticated for each service request. Since this is highly disruptive from the point of view of application transaction response, this authentication is accomplished at the connection level via mutual Transport Layer Security (mTLS) when a service makes an initial connection establishment as part of its inter-service call. This authentication is not performed again in subsequent calls."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.\nParameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nControl AC-19 Discussion: Change “Many controls for mobile\ndevices are reflected in other controls allocated to the initial control\nbaselines as starting points for the development of security plans\nand overlays using the tailoring process."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 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 require for Access Control?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nesses at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems.\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 2)"}, {"role": "assistant", "content": "ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Security Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 Security and Privacy Controls for Information Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "e\nMatthew A. Kozma\nChief Information Officer\n\nJohn Sherman\nPrincipal Deputy CIO\n\nMichael E. Waschull\nDeputy Chief Information Officer\n\nMark Hakun\nDeputy CIO for Cybersecurity and DoD SISO\n\nClifford M.\nConner\nCybersecurity Group and IC CISO\n\nKevin Dulany\nDirector, Cybersecurity Policy and Partnerships\n\nVacant\nDirector, Security Coordination Center\n\nNational Institute of Standards\nand Technology\nCharles H. Romine\nDirector, Information Technology Laboratory\n\nKevin Stine\nActing Cybersecurity Advisor, ITL\n\nMatthew Scholl\nChief, Computer Security Division\n\nKevin Stine\nChief, Applied Cybersecurity Division\n\nRon Ross\nFISMA Implementation Project Leader\n\nCommittee on National Security\nSystems\nMark G. Hakun\nChair\n\nSusan Dorr\nCo-Chair\n\nKevin Dulany\nTri-Chair—Defense Community\n\nChris Johnson\nTri-Chair—Intelligence Community\n\nVicki Michetti\nTri-Chair—Civil Agencies\n\nJoint Task Force Working Group\n\nVictoria Pillitteri\nNIST, JTF Leader\n\n McKay Tolboe\n DoD\n\nDorian Pappas\nIntelligence Community\n\nKelley Dempsey\nNIST\n\nEhijele Olumese\nThe MITRE Corporation\n\n Lydia Humphries\n Booz Allen Hamilton\n\nDaniel Faigin\nAerospace Corporation\n\nNaomi Lefkovitz\nNIST\n\nEsten Porter\nThe MITRE Corporation\n\n Julie Nethery Snyder\n The MITRE Corporation\n\nChristina Sames\nThe MITRE Corporation\n\nChristian Enloe\nNIST\n\nDavid Black\nThe MITRE Corporation\n\n Rich Graubart\n The MITRE Corporation\n\nPeter Duspiva\nIntelligence Community\n\nKaitlin Boeckl\nNIST\n\nEduardo Takamura\nNIST\n\n Ned Goren\n NIST\n\nAndrew Regenscheid\nNIST\n\nJon Boyens\nNIST\n\niii\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 Configuration Management?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 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 additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 15)"}, {"role": "assistant", "content": "oring criteria applied to the NIST guidelines to obtain the requirements. - Section 3 lists the security requirements for protecting the confidentiality of CUI in nonfederal systems and organizations.\nThe 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: Tailoring Criteria\n- Appendix D: Organization-Defined Parameters\n- Appendix E: Change Log\n\n8 Nonfederal organizations that collect or maintain information on behalf of a federal agency or that use or operate a system on behalf of an agency must comply with the requirements in FISMA [9]. 9 System components include workstations, servers, notebook computers, smartphones, tablets, input and output devices, network components, operating systems, virtual machines, database management systems, and applications. ## 2. The Fundamentals\n\nThis section describes the assumptions and methodology used to develop the requirements to protect the confidentiality of CUI in nonfederal systems and organizations. It also includes the tailoring 10 criteria applied to the controls in SP 800-53 [8]. ## 2.1. Security Requirement Assumptions\n\nThe security requirements in this publication are based on the following assumptions:\n\n- Federal information designated as CUI has the same value, whether such information resides in a federal or nonfederal system or organization. - Statutory and regulatory requirements for the protection of CUI are consistent in federal and nonfederal systems and organizations. - Safeguards implemented to protect CUI are consistent in federal and nonfederal systems and organizations. - The confidentiality impact value for CUI is no less than moderate . 11\n- Nonfederal organizations can directly implement a variety of potential security solutions or use external service providers to satisfy security requirements. ## 2.2."}], "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": 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 does CMMC Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 8)"}, {"role": "assistant", "content": "ederal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui.\n- NIST is responsible for developing and publishing the security requirements for the protection of CUI. How requirements are mandated, and any compliance issues related to nonfederal implementation of SP 800-171, are the responsibility of the federal agency requiring its use , as expressed in a specific contract or agreement. ## Additional NIST Resources\n\n- NIST's Protecting CUI Frequently Asked Questions\n- Changes Between SP 800-171 Rev. 2 and Rev. 3 (.xlsx)\n- The NIST Cybersecurity and Privacy Reference Tool (CPRT) provides online, interactive versions of the updated security requirements in SP 800-171, Revision 3 and the updated assessment procedures in SP 800-171A, Revision 3\n- Event Recording: ' CUI Security Requirements Workshop ,' which provides a general overview of SP 800 -171 and SP 800-171A\n- NIST Small Business Cybersecurity Corner\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n## What to Expect\n\nThe following pages delve deeper into the SP 800-171 R3 publication to provide more details for those responsible for implementing the requirements 3 . The following pages cover:\n\n\n\nPage 8: Key differences between SP 800-171 R2 and R3. Pages 9-10: General tips for getting started. Pages 11-28: Tips for getting started, broken out by Control Family. 3 We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nBalancing exposure to cybersecurity risks throughout the supply chain with the costs and benefits of implementing C-SCRM practices and controls should be a key component of the acquirer's overall approach to C-SCRM. Enterprises should be aware that implementing C-SCRM practices and controls necessitates additional financial and human resources. Requiring a greater level of testing, documentation, or security features from suppliers, developers, system integrators, external system service providers, and other ICT/OT-related service providers may increase the price of a product or service, which may result in increased cost to the acquirer. This is especially true for those products and services developed for general-purpose applications and not tailored to the specific enterprise security or C-SCRM requirements. When deciding whether to require and implement C-SCRM practices and controls, acquirers should consider both the costs of implementing these controls and the risks of not implementing them."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 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 guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 15)"}, {"role": "assistant", "content": "the dashed green lines. Lessons learned from performing all activities in all Functions are fed into Improvement, and those lessons are analyzed, prioritized, and used to inform all of the Functions.\nThis reflects that organizations can learn new lessons at all times\n\n(e.g., detecting the presence of a new threat and characterizing its behavior) and communicate those lessons to the appropriate personnel so that the organization's incident response and other cybersecurity risk management policies, processes, and practices can be adjusted as needed. Table 1 maps the previous SP 800-61 incident response life cycle model's phases to the corresponding CSF 2.0 Functions used in this document. Table 1. Previous incident response life cycle model's phases and corresponding CSF 2.0 Functions\n\n| Previous Incident Response Life Cycle Model Phase | CSF 2.0 Functions |\n|-----------------------------------------------------|---------------------------------|\n| Preparation | Govern |\n| Preparation | Identify (all Categories) |\n| Preparation | Protect |\n| Detection & Analysis | Detect |\n| Detection & Analysis | Identify (Improvement Category) |\n| Containment, Eradication & Recovery | Respond |\n| Containment, Eradication & Recovery | Recover |\n| Containment, Eradication & Recovery | Identify (Improvement Category) |\n| Post-Incident Activity | Identify (Improvement Category) |\n\nOrganizations should use the incident response life cycle framework or model that suits them best."}], "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": 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": "How does Assessing Security Requirements for Controlled Unclassified Information support CMMC certification?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nother than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nne or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control.\n- Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-61r3\n\n## Incident Response Recommendations and Considerations for Cybersecurity Risk Management\n\nA CSF 2.0 Community Profile\n\nAlex Nelson Sanjay Rekhi Murugiah Souppaya Karen Scarfone\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-61r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-61r3\n\n## Incident Response Recommendations and Considerations for Cybersecurity Risk Management\n\nA CSF 2.0 Community Profile\n\nAlex Nelson Sanjay Rekhi Murugiah Souppaya*\n\nComputer Security Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity\n\n*Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-61r3\n\nApril 2025\n\n\n\nU.S. Department of Commerce\n\nHoward Lutnick, Secretary of Commerce\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."}], "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": 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 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 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 Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nInformation technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .\nISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 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 does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 19)"}, {"role": "assistant", "content": "ro» (BCORE, por su nombre en inglés black core ), la cual implicaba pasar de un modelo de seguridad basado en el perímetro a uno focalizado en la seguridad de las transacciones individuales (JERICHO).\nEl Foro Jericho -organización para proteger los sistemas y datos empresariales- del 2004 dio a conocer la idea de desperimetrización: los límites de la seguridad implícita basada en la ubicación de la red y las limitaciones de confiar en defensas únicas y estáticas en un gran segmento de red. El concepto de desperimetrización evolucionó y mejoró hasta convertirse en el término más amplio de confianza cero, que fue acuñado posteriormente por John Kindervag 3 mientras trabajaba en Forrester 4 . Luego, se convirtió en el término utilizado para describir diversas soluciones de ciberseguridad que se alejaban de la seguridad basada en la ubicación de la red y, en cambio, se centraban en la evaluación de la confianza en cada transacción. Tanto la industria privada como la enseñanza superior también han experimentado esta evolución desde la seguridad basada en el perímetro hacia una estrategia sustentada en los principios de la confianza cero. Desde hace más de una década se insta a los organismos federales a cambiar hacia una protección basada en estos nuevos principios, mediante la creación de prestaciones y políticas como la Ley Federal de Gestión de Seguridad de la Información (FISMA por su nombre en inglés Federal Information Security Modernization Act); seguida del Marco de Gestión de Riesgos (RMF por su apelación en inglés Risk Management Framework); la Gestión Federal de Identidades, Credenciales y Accesos (FICAM, por su nombre en inglés Federal Identity,\n\n3 https://go.forrester.com/blogs/next-generation-access-and-zero-trust/\n\n4 Cualquier mención de productos o servicios comerciales dentro de los documentos de NIST es solo para información y no implica una recomendación o respaldo por parte de NIST."}], "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": 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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate. The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 3)"}, {"role": "assistant", "content": "| help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n## Audience\n\n\n\n\n\nPages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality\n\n\n\nConfidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 \"Controlled Unclassified Information.\"\n\n## A Suite of Guidance\n\nNIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . \n\n\n\n\n\nNIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Access Control?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 2)"}, {"role": "assistant", "content": "ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n........................................................ 1 | CHAPTERONE INTRODUCTION......................................................................................................\n1 | 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": "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 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 does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Media Protection\n\nDescription: Protect system media, both paper and digital; limiting access to data on system media to authorized users; and sanitizing or destroying system media before disposal or release for reuse."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 20)"}, {"role": "assistant", "content": "-access-and-zero-trust/\n\n4 Cualquier mención de productos o servicios comerciales dentro de los documentos de NIST es solo para información y no implica una recomendación o respaldo por parte de NIST.\nCredential, and Access Management); la Conexión a Internet de confianza TIC (por su nombre en inglés Trusted Internet Connections), y los programas de Diagnóstico y Mitigación Continuos (CDM por su denominación en inglés Continuous Diagnostics and Mitigation). Todos estos planes tienen como objetivo restringir el acceso a los datos y a los recursos a las partes autorizadas. Cuando se iniciaron estos programas, estaban limitados por las capacidades técnicas de los sistemas de información. Las políticas de seguridad eran mayormente estáticas y se aplicaban en grandes «cuellos de botella» al alcance de la empresa para obtener el mejor resultado posible. A medida que la tecnología se consolida, se están pudiendo analizar y evaluar continuamente las solicitudes de acceso de forma dinámica y granular, sobre una base de «necesidad de acceso» que permite mitigar la exposición de los datos ocasionada por cuentas comprometidas, atacantes que monitorean las redes y otras amenazas. ## 1.2 Estructura del documento\n\nEl resto del documento se encuentra organizado de la siguiente manera:\n\n- Sección 2: define la ZT y la ZTA al mismo tiempo que enumera algunos postulados a la hora de diseñar una ZTA para una empresa. Esta sección también incluye una lista de los principios del diseño de ZT. - Sección 3: documenta los componentes lógicos o bloques de construcción de la ZT. Es posible que algunas implementaciones únicas conformen los componentes de la ZTA de forma diferente, pero que sirvan para la misma funcionalidad lógica. - Sección 4: enumera algunos posibles casos de uso en los que una ZTA puede hacer que los entornos empresariales sean más seguros y menos propensos a ataques exitosos."}], "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": 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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 8)"}, {"role": "assistant", "content": "e requirements also apply to services, including externally provided services, that process, store, or transmit CUI, or that provide security protections, for the system requiring enhanced protection.\nThe protection of a specific service to include CUI that is processed, stored or transmitted during the provision of that service, is achieved by implementing the enhanced security requirements for the service, or the system or system components responsible for providing that service. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. The term organizational system is used in many of the enhanced security requirements. It has a specific meaning regarding the applicability of the enhanced requirements as described above. Appropriate scoping considerations for the requirements are important factors in determining protection-related investment decisions and managing security risk for nonfederal organizations that have the responsibility of protecting CUI associated with critical programs and high value assets. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## FRAMEWORK FOR IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY\n\nOrganizations that have implemented or plan to implement the NIST Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 13)"}, {"role": "assistant", "content": "ocesses, and procedures. ## 2.1. Incident Response Life Cycle Model\n\nFig. 1 depicts the incident response life cycle model illustrated in the previous version of this publication [SP800-61r2]. Fig. 1.\nPrevious incident response life cycle model\n\n\n\nAt that time, incidents were relatively rare, the scope of most incidents was narrow and welldefined, and incident response and recovery was usually completed within a day or two. Under those conditions, it was realistic to treat incident response as a separate set of activities performed by a separate team of personnel and to depict all incident response activities as part of a circular life cycle. Formal post-incident activities would identify needed improvements and feed them into the preparation stage, thus starting the cycle again. Incident response activities were typically intermittent rather than continuous. However, the current state of incident response has greatly changed since then. Today, incidents occur frequently and cause far more damage. Recovering from them often takes weeks or months due to their breadth, complexity, and dynamic nature. Incident response is now considered a critical part of cybersecurity risk management that should be integrated across organizational operations. The lessons learned during incident response should often be shared as soon as they are identified, not delayed until after recovery concludes. Continuous improvement is increasingly necessary for all facets of cybersecurity risk management in order to keep up with modern threats. Fig. 2 shows a high-level incident response life cycle model based on the six CSF 2.0 Functions, which organize cybersecurity outcomes at their highest level:\n\n- Govern (GV): The organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored. - Identify (ID): The organization's current cybersecurity risks are understood."}], "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": 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 Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n- Applying a threat-centric approach to security requirements specification;\n- Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16\n- Implementing dual authorization controls for the most critical or sensitive operations;\n- Limiting persistent storage to isolated enclaves or domains;\n- Implementing a comply-to-connect approach for systems and networks;\n- Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components;\n- Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components;\n- Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and\n- Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 2)"}, {"role": "assistant", "content": "other than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["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 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 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 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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "ards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology.\nITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2."}], "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": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to 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 Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nDescription: Ensuring personnel are made aware of the security risks associated with their activities and of the applicable laws, directives, policies, standards, regulations, or procedures related to the security of organizational systems; and ensuring that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.\n\nRegularly provide basic and advanced security literacy training to new and existing staff. Customize the content to make it relevant -based on the systems that personnel have authorized access to, contextualized to the work environments of personnel (e.g., telework, shop floor), and tailored to the specific roles of personnel. The content should include:"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nDescription: Ensuring personnel are made aware of the security risks associated with their activities and of the applicable laws, directives, policies, standards, regulations, or procedures related to the security of organizational systems; and ensuring that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.\n\nRegularly provide basic and advanced security literacy training to new and existing staff. Customize the content to make it relevant -based on the systems that personnel have authorized access to, contextualized to the work environments of personnel (e.g., telework, shop floor), and tailored to the specific roles of personnel. The content should include:"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nSP 800-53A provides a process that allows organizations to tailor the assessment procedures\noutlined in the guidance. Tailoring involves customizing the assessment procedures to match\nthe characteristics of the system and its environment of operation more closely. The tailoring\nprocess described in this guidance gives organizations the flexibility needed to avoid assessment\napproaches that are unnecessarily complex or costly while simultaneously meeting the\nassessment requirements and risk management principles established in the RMF. Tailoring\ndecisions are left to the discretion of the organization to maximize flexibility in developing\nassessment plans – applying the results of risk assessments to determine the extent, rigor, and\nlevel of intensity of the assessments needed to provide sufficient assurance about the security\nand privacy posture of the system. CHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| | | 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "tise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D.\nThe controls described assist organizations in defining the controls needed to satisfy minimum assurance requirements. Where additional assurance is desired to achieve risk management objectives, Table E-4 provides additional security controls and control enhancements to achieve enhanced assurance. Implementers should note that designation of assurance-related controls is not intended to imply a greater level of importance for such controls. Achieving adequate security for organizational information systems requires the correct combination of both functionality- and assurance-related security controls. ## 6 Security Controls\n\nAppendix F, the Security Control Catalog, provides a comprehensive range of countermeasures for organizations and information systems. The security controls are designed to be technologyneutral such that the focus is on the fundamental countermeasures needed to protect organizational information during processing, storage, or transmission. SP 800-53 Rev. 4, therefore, does not provide guidance on the application of security controls to specific technologies, environments of operation, or missions/business functions. These specific areas may be addressed using overlays (see below). Control enhancements are included with many security controls and are selected in order to increase the strength of the base control. Control enhancements are intended to be implemented only in conjunction with implementation of the base control. Some security controls and control enhancements include one or more assignment and selection statements. These are variable parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 Zero Trust Architecture provide? (Part 8)"}, {"role": "assistant", "content": "## Tabla de contenidos | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["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": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 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 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 Incident Response?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nRisk assessments are also conducted to determine the potential that the use of an external provider for the development, implementation, maintenance, management, operation, or disposition of a system, system element, or service could create a loss, and the potential impact of that loss. The impact may be immediate (e.g., physical theft) or on-going (e.g., the ability of adversaries to replicate critical equipment because of theft). The impact may be endemic (e.g., limited to a single system) or systemic (e.g., including any system that uses a specific type of system component). Supply chain risk assessments consider vulnerabilities which may arise related to the disposition of a system or system element and from the use of external providers. Vulnerabilities in the supply chain may include a lack of traceability or accountability leading to the potential use of counterfeits, insertion of malware, or poor-quality systems. The use of external providers may result in a loss of visibility and control over how systems, system elements, and services are developed, deployed, and maintained. A clear understanding of the threats, vulnerabilities, and potential impacts of an adverse supply chain event can help organizations appropriately balance supply chain risk with risk tolerance. Supply chain risk assessments can include information from supplier audits, reviews, and supply chain intelligence. Organizations develop a strategy for collecting information, including a strategy for collaborating with providers on supply chain risk assessments. Such collaboration helps organizations leverage information from providers, reduce redundancy, identify potential courses of action for risk responses, and reduce the burden on providers."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.4.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThis publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, and availability protection. The enhanced security requirements are implemented in addition to the basic and derived requirements since those requirements are not designed to address the APT. The enhanced security requirements apply to those components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 3)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST.\nMany NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. Submit comments on this publication to: sec-cert@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe NIST Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, implementations, proofs of concept, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThe protection of Controlled Unclassified Information (CUI) in nonfederal systems and organizations is important to federal agencies and can directly impact the ability of the Federal Government to successfully carry out its assigned missions and business operations."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["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 14)"}, {"role": "assistant", "content": "..................................................... 50 | APPENDIX C MAPPINGTABLES ....................................................................................................\n50 |\n| APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 | APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 |\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Errata\n\nThis table contains changes that have been incorporated into Special Publication 800-172. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. Any potential updates for this 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 the SP 800-172 publication details. | DATE | TYPE | CHANGE | PAGE |\n|--------|--------|----------|--------|\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## CHAPTER ONE\n\n## INTRODUCTION\n\nTHE NEED TO PROTECT CONTROLLED UNCLASSIFIED INFORMATION\n\noday, 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."}], "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": 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 3)"}, {"role": "assistant", "content": "d States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-37, Revision 2 Natl. Inst. Stand. Technol. Spec. Publ. 800-37, Rev.\n2, 183 pages (December 2018)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-37r2\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the designated public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["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 2 require for Incident Response?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 in Nonfederal Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "..........85 | |\n| Appendix C.\n| Tailoring Criteria ......................................................................................................93 | |\n| Appendix D. | Organization-Defined Parameters ..........................................................................106 | |\n| Appendix E. | Change Log ............................................................................................................109 | |\n\n## List of Tables\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."}], "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": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "__________\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.\nThe 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\nHON. John Sherman\nChief Information Officer\n\nDr. Kelly Fletcher\nPrincipal Deputy Chief Information Officer\n\nDavid McKeown\nDeputy CIO for Cybersecurity and DoD CISO\n\nMark Hakun\nPrincipal Deputy CIO for Cybersecurity\n\nKevin Dulany\nDirector, Cybersecurity Policy and Partnerships\n\nOffice of the Director of National\nIntelligence\n\nMichael E. Waschull\nActing Chief Information Officer\n\nMichael E. Waschull\nDeputy Chief Information Officer\n\nC. Matthew Conner\nCybersecurity Group and IC CISO\n\nCheri Benedict\nDirector, Security Coordination Center\n\nNational Institute of Standards and\nTechnology\n\nCommittee on National Security\nSystems\n\nJames St. Pierre\nActing Director, Information Technology 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."}], "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": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 6)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1. Introduction..............................................................................................................................1 | 1. Introduction..............................................................................................................................1 | 1. Introduction..............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. The Fundamentals.....................................................................................................................3 | 2. The Fundamentals.....................................................................................................................3 | 2. The Fundamentals.....................................................................................................................3 |\n| 3."}], "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": 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 Incident Response?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n...........................................................64 | |\n| A.1.2.\nSelecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7. FAMILY: CONFIGURATION MANAGEMENT................................................................................87 | |\n| A.2.8. FAMILY: CONTINGENCY PLANNING ...........................................................................................98 | |\n| A.2.9."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n| 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 |"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "..................................................................115 | |\n| A.2.13.\nFAMILY: PHYSICAL AND ENVIRONMENTAL PROTECTION......................................................116 | |\n| A.2.14. FAMILY: PLANNING ................................................................................................................120 | |\n| A.2.15. FAMILY: PROGRAM MANAGEMENT ......................................................................................123 | |\n| A.2.16. FAMILY: PERSONNEL SECURITY..............................................................................................129 | |\n| A.2.17. FAMILY: PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY | ....132 |\n| A.2.18. FAMILY: RISK ASSESSMENT....................................................................................................132 | |\n| A.2.19. FAMILY: SYSTEM AND SERVICES ACQUISITION......................................................................136 | |\n| A.2.20."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nent some incidents, prepare to handle incidents that do occur, reduce the impact of those incidents, and improve incident response and cybersecurity risk management practices based on lessons learned.\nDetect, Respond, and Recover help organizations discover, manage, prioritize, contain, eradicate, and recover from cybersecurity incidents, as well as perform incident reporting, notification, and other incident-related communications."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n....................................................................................... | 63 |\n| A.1.1.\nC-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 3)"}, {"role": "assistant", "content": "| help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n## Audience\n\n\n\n\n\nPages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality\n\n\n\nConfidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 \"Controlled Unclassified Information.\"\n\n## A Suite of Guidance\n\nNIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . \n\n\n\n\n\nNIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 14)"}, {"role": "assistant", "content": "istry [4]. The requirements do not apply to nonfederal organizations that are collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency.\n8\n\nThe security requirements in this publication are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. 9 The requirements are intended for use by federal agencies in contractual vehicles or other agreements that are established between those agencies and nonfederal organizations. Appropriately scoping requirements is an important factor in determining protection-related investment decisions and managing security risks for nonfederal organizations. If nonfederal organizations designate system components for the processing, storage, or transmission of CUI, those organizations may limit the scope of the security requirements by isolating the system components in a separate security domain. Isolation can be achieved by applying architectural and design concepts (e.g., implementing subnetworks with firewalls or other boundary protection devices and using information flow control mechanisms). 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. ## 1.2. Organization of This Publication\n\nThe remainder of this special publication is organized as follows:\n\n- Section 2 describes the assumptions and methodology used to develop the security requirements for protecting the confidentiality of CUI, the format of the requirements, and the tailoring criteria applied to the NIST guidelines to obtain the requirements. - Section 3 lists the security requirements for protecting the confidentiality of CUI 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": 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 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 Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nInformation technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security .\nISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products). Since many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide?"}, {"role": "assistant", "content": "\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Incident Response?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 15)"}, {"role": "assistant", "content": "| |\n| D.3.1.10. Related Laws, Regulations, and Policies...........................................................................215 | |\n\n| D.3.1.11.\nRevision and Maintenance...............................................................................................215 | |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|\n| D.3.1.12. C-SCRM Plan Approval......................................................................................................216 | |\n| D.3.1.13. Acronym List.....................................................................................................................216 | |\n| D.3.1.14."}], "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": 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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 20)"}, {"role": "assistant", "content": "vices-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.\nThis may include establishing (1) zero trust by enabling mutual authentication in communication between any pair of services and (2) a robust access control mechanism based on an access control model (e.g., the attribute-based access control [ABAC] model) that can be used to express a wide set of policies and is scalable in terms of user base, objects (resources), and deployment environment. ## Scope\n\nThe scope of this document includes:\n\n- Identifying the requirements for realizing a ZTA for granular access control in microservices-based application platforms that include a service mesh infrastructure. - Identifying the infrastructural elements that should be part of the platform in order to configure and implement ZT principles. - Guidance for deploying a ZTA in the above platform and outlining the security assurances that the deployment can provide. - Recommend multi-tier policies that combine network-level (both coarse-grained and fine-grained) and identity-tier policies for enforcing ZT principles. The reference application platform consists of microservices-based applications using a service mesh with sidecar proxies as the application services infrastructure. The service mesh technology variation that uses a sidecar-less approach is not considered as the deployment of this technology is still in early stages. ## Target Audience\n\nThis guidance is intended for security architects and infrastructure designers in organizations with a hybrid IT environment (consisting of both on-premises and multiple cloud-based applications) with a combination of legacy and microservices-based (i.e., cloud-native) applications and a built-in application services infrastructure, such as a service mesh."}], "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": 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 Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\n- '…The executive branch operates its information technology (IT) on behalf of the American people. Its IT and data should be secured responsibly using all United States Government capabilities...'\n- '…Cybersecurity risk management comprises the full range of activities undertaken to protect IT and data from unauthorized access and other cyber threats, to maintain awareness of cyber threats, to detect anomalies and incidents adversely affecting IT and data, and to mitigate the impact of, respond to, and recover from incidents…'\n\nThe RMF emphasizes risk management by promoting the development of security and privacy capabilities into information systems throughout the system development life cycle (SDLC); 10 by maintaining situational awareness of the security and privacy posture of those systems on an ongoing basis through continuous monitoring processes; and by providing information to senior leaders and executives to facilitate decisions regarding the acceptance of risk to organizational operations and assets, individuals, other organizations, and the Nation arising from the use and operation of their systems. The RMF:\n\n- Chapter Two describes the concepts associated with managing information system-related security and privacy risk. This includes an organization-wide view of risk management; the RMF steps and task structure; the relationship between information security and privacy programs and how these programs are addressed in the RMF; information resources as system and system elements; authorization boundaries; security and privacy posture; and security and privacy considerations related to supply chain risk management."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\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. CONTROL BASELINES\n\nThe control baselines that have previously been included in NIST Special Publication 800-53 have\nbeen relocated to NIST Special Publication 800-53B. SP 800-53B contains security and privacy\ncontrol baselines for federal information systems and organizations. It provides guidance for\ntailoring control baselines and for developing overlays to support the security and privacy\nrequirements of stakeholders and their organizations."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice 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 additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "|\n| Appendix A. C-SCRM Security Controls...............................................................................................\n| 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nSee [SP 800-37], Task S-2, Control Tailoring, for additional guidance on tailoring control baselines for systems and environments of operation.' | 9 | | 12-10-2020 | Editorial | Section 2.4 (Footnote 28): Change 'Guidance on developing privacy plans is forthcoming.' to 'Guidance on developing privacy and supply chain risk management plans is forthcoming.' | 9 | | 12-10-2020 | Editorial | Table 3-1 (AC-3(1)) Title: Change 'FUNCTION' to 'FUNCTIONS' | 16 | | 12-10-2020 | Editorial | Table 3-1 (AC-3(6)): Change 'MP-4, SC-28' to 'MP-4 and SC-28' | 16 | | 12-10-2020 | Editorial | Table 3-1 (AC-13): Change 'AC-2, AU-6' to 'AC-2 and AU-6' | 18 | | 12-10-2020 | Editorial | Table 3-1 (AC-19(5)) Title: Change 'FULL DEVICE AND' to 'FULL DEVICE OR' | 19 | | 12-10-2020 | Editorial | Table 3-1 (AC-20(4)) Title: Change 'NETWORK-ACCESSIBLE' to 'NETWORK ACCESSIBLE' | 19 | | 12-10-2020 | Editorial | Table 3-2 (AT-3(5)) Title: Change 'ACCESSING PERSONALLY' to 'PROCESSING PERSONALLY' | 20 | | 12-10-2020 | Editorial | Table 3-3 (AU-7(2)) Title: Change 'SEARCH AND SORT' to 'SORT AND SEARCH' | 21 | | 12-10-2020 | Editorial | Table 3-3 (AU-15): Change 'Incorporated into' to 'Moved to' | 22 |"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 4)"}, {"role": "assistant", "content": "Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96].\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThis publication describes the Risk Management Framework (RMF) and provides guidelines for applying the RMF to information systems and organizations. The RMF provides a disciplined, structured, and flexible process for managing security and privacy risk that includes information security categorization; control selection, implementation, and assessment; system and common control authorizations; and continuous monitoring. The RMF includes activities to prepare organizations to execute the framework at appropriate risk management levels."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["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 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 2 require for Configuration Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide?"}, {"role": "assistant", "content": "\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "three security control baselines (one for each system impact level-low-impact, moderate-impact, and high-impact), as well as a privacy baseline that is applied to systems irrespective of impact level.\nIn addition to the control baselines, this publication provides tailoring guidance and a set of working assumptions that help guide and inform the control selection process. Finally, this publication provides guidance on the development of overlays to facilitate control baseline customization for specific communities of interest, technologies, and environments of operation. ## Keywords\n\nAssurance; impact level; privacy control; privacy control baseline; security control; security control baseline; tailoring; control selection; control overlays. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThis publication was developed by the Joint Task Force Interagency Working Group. The group includes representatives from the civil, defense, and intelligence communities. The National Institute of Standards and Technology wishes to acknowledge and thank the senior leaders from the Department of Commerce, Department of Defense, the Office of the Director of National Intelligence, the Committee on National Security Systems, and the members of the interagency working group whose dedicated efforts contributed significantly to this publication. ## Department of Defense\n\n## Office of the Director of National Intelligence\n\nMatthew A. Kozma Chief Information Officer\n\nDana Deasy\n\nChief Information Officer\n\nJohn Sherman\n\nMichael E. Waschull Deputy Chief Information Officer\n\nPrincipal Deputy CIO\n\nMark Hakun\n\nClifford M."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 16)"}, {"role": "assistant", "content": "UI is no less than moderate . 11\n- Nonfederal organizations can directly implement a variety of potential security solutions or use external service providers to satisfy security requirements. ## 2.2.\nSecurity Requirement Development Methodology\n\nStarting with the SP 800-53 controls in the SP 800-53B [12] moderate baseline, the controls are tailored to eliminate selected controls or parts of controls that are:\n\n- Primarily the responsibility of the Federal Government,\n- Not directly related to protecting the confidentiality of CUI,\n- Adequately addressed by other related controls, 12 or\n- Not applicable. SP 800-171 security requirements represent a subset of the controls that are necessary to protect the confidentiality of CUI. The security requirements are organized into 17 families, as illustrated in Table 1. Each family contains the requirements related to the general security topic of the family. Certain families from SP 800-53 are not included due to the tailoring criteria. For example, the PII Processing and Transparency (PT) family is not included because personally identifiable information (PII) is a category of CUI, and therefore, no additional requirements are\n\n10 Tailoring is the process by which control baselines are modified to achieve certain organizational goals and objectives [13]. 11 In accordance with 32 CFR 2002 [5], CUI is categorized at no less than the FIPS 199 [6] moderate confidentiality impact value. However, when federal law, regulation, or government-wide policy establishing the control of CUI specifies controls that differ from those of the moderate control baseline, then the applicable law, regulation, or government-wide policy is followed. 12 'Adequately addressed by other related controls' means that the protection capability offered by the control is provided by another control in the same or different control family."}], "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": 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 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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 5)"}, {"role": "assistant", "content": "quirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.\n## Keywords\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors also wish to recognize the scientists, engineers, and research staff from the NIST Computer Security and the Applied Cybersecurity Divisions for their exceptional contributions in helping to improve the content of the publication. A special note of thanks to Pat O'Reilly, Jim Foti, Jeff Brewer, Chris Enloe, Ned Goren, and the entire NIST web team for their outstanding administrative support. Finally, the authors also gratefully acknowledge the contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 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 does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nreover, adversaries are using the supply chain as an attack vector and effective means of penetrating our systems, compromising the integrity of system elements, and gaining access to critical assets.\n- To provide closer linkage and communication between the risk management processes and activities at the C-suite or governance level of the organization and the individuals, processes, and activities at the system and operational level of the organization;\n- To institutionalize critical risk management preparatory activities at all risk management levels to facilitate a more effective, efficient, and cost-effective execution of the RMF;\n- To demonstrate how the NIST Cybersecurity Framework [NIST CSF] can be aligned with the RMF and implemented using established NIST risk management processes;\n- To integrate privacy risk management processes into the RMF to better support the privacy protection needs for which privacy programs are responsible;\n- To promote the development of trustworthy secure software and systems by aligning life cycle-based systems engineering processes in NIST Special Publication 800-160, Volume 1 [SP 800-160 v1], with the relevant tasks in the RMF;\n- To integrate security-related, supply chain risk management (SCRM) concepts into the RMF to address untrustworthy suppliers, insertion of counterfeits, tampering, unauthorized production, theft, insertion of malicious code, and poor manufacturing and development practices throughout the SDLC; and\n- To allow for an organization-generated control selection approach to complement the traditional baseline control selection approach and support the use of the consolidated control catalog in NIST Special Publication 800-53, Revision 5."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| ...................................................................................................\n3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "The guide was developed and is maintained by the Joint Task Force Transformation Initiative Interagency Working Group, part of an ongoing information security partnership among the U.S. Department of Defense, the Intelligence Community, the Committee on National Security Systems, the Department of Homeland Security, and U.S. federal civil agencies. SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. SP 800-53 Revision 4 is part of the NIST Special Publication 800-series that reports on the NIST Information Technology Laboratory's (ITL) computer security-related research, guidelines, and outreach. The publication provides a comprehensive set of security controls, three security control baselines (low, moderate, and high impact), and guidance for tailoring the appropriate baseline to specific needs according to the organization's missions, environments of operation, and technologies used. As the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 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 Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "etary of Commerce, OMB Director, or any other federal official. This\npublication may be used by nongovernmental organizations on a voluntary basis and is not\nsubject to copyright in the United States.\nAttribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-53A Revision 5\nNatl. Inst. Stand. Technol. Spec. Publ. 800-53A, Rev. 5, 733 pages (January 2022)\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53Ar5\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an\nexperimental procedure or concept adequately. Such identification is not intended to imply\nrecommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or\nequipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities. The information in this publication, including\nconcepts, practices, and methodologies may be used by federal agencies even before the completion of\nsuch companion publications. Thus, until each publication is completed, current requirements, guidelines,\nand procedures, where they exist, remain operative. For planning and transition purposes, federal\nagencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the designated public comment periods\nand provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at\nhttps://csrc.nist.gov/publications."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\ncyber threat information sharing; Cybersecurity Framework; cybersecurity incident; cybersecurity risk management; incident handling; incident management; incident response.\n\n…an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies. [FISMA2014]\n\n- Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state"}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n...........................................................64 | |\n| A.1.2.\nSelecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7. FAMILY: CONFIGURATION MANAGEMENT................................................................................87 | |\n| A.2.8. FAMILY: CONTINGENCY PLANNING ...........................................................................................98 | |\n| A.2.9."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n| 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 |"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 8)"}, {"role": "assistant", "content": "ederal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui.\n- NIST is responsible for developing and publishing the security requirements for the protection of CUI. How requirements are mandated, and any compliance issues related to nonfederal implementation of SP 800-171, are the responsibility of the federal agency requiring its use , as expressed in a specific contract or agreement. ## Additional NIST Resources\n\n- NIST's Protecting CUI Frequently Asked Questions\n- Changes Between SP 800-171 Rev. 2 and Rev. 3 (.xlsx)\n- The NIST Cybersecurity and Privacy Reference Tool (CPRT) provides online, interactive versions of the updated security requirements in SP 800-171, Revision 3 and the updated assessment procedures in SP 800-171A, Revision 3\n- Event Recording: ' CUI Security Requirements Workshop ,' which provides a general overview of SP 800 -171 and SP 800-171A\n- NIST Small Business Cybersecurity Corner\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n## What to Expect\n\nThe following pages delve deeper into the SP 800-171 R3 publication to provide more details for those responsible for implementing the requirements 3 . The following pages cover:\n\n\n\nPage 8: Key differences between SP 800-171 R2 and R3. Pages 9-10: General tips for getting started. Pages 11-28: Tips for getting started, broken out by Control Family. 3 We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 9)"}, {"role": "assistant", "content": "ework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53].\nThe security control mappings can be useful to organizations that wish to demonstrate compliance to the security requirements in the context of their established information security programs when such programs have been built using the NIST security controls. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.4. 3.1.4."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 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 Assessing Security Requirements for Controlled Unclassified Information provide? (Part 16)"}, {"role": "assistant", "content": "e with ISO/IEC 15408 [6] and Cryptographic Module Validation Program Testing Laboratories that evaluate cryptographic modules in accordance with Federal Information Processing Standard (FIPS) 140 [7].\nproducts are assessed by commercial testing organizations and then subsequently deployed in hundreds of thousands of systems, these types of assessments can be carried out at a greater level of depth and provide deeper insights into the security capabilities of the products. The evidence needed to determine compliance with the security requirements is obtained by assessing the implementation of the safeguards and countermeasures selected to satisfy the requirements. Assessors can build on previously developed materials that started with the specification of the information security needs of the organization and were further improved during the design, development, and implementation of the system. These materials provide the initial evidence for an assurance case. Assessments can be conducted by system developers, system integrators, auditors, system owners, or the security staffs of organizations. The assessors or assessment teams bring available information about the system together, such as the results of component product assessments. The assessors can conduct additional system-level assessments using the assessment methods and procedures contained in this publication and the implementation information provided by the nonfederal organization in its system security plan. Assessments can be used to compile and evaluate the evidence needed by organizations to help determine the effectiveness of the safeguards implemented to protect CUI, the actions needed to mitigate security risks to the organization, and compliance with the security requirements. The assessment procedures in this publication are based on and sourced to the assessment procedures in SP 800-53A [5]."}], "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": 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 Control Baselines for Information Systems and Organizations provide? (Part 11)"}, {"role": "assistant", "content": "acy, 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.\nIn 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. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## USE OF EXAMPLES IN THIS PUBLICATION\n\nThroughout this publication, examples are used to illustrate, clarify, or explain certain items in chapter sections, controls, and control enhancements. These examples are illustrative in nature and are not intended to limit or constrain the application of controls or control enhancements by organizations."}], "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": 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 Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe scope of the assessments conducted using the procedures described in this publication is guided and informed by the system security plans for the organizational systems processing, storing, or transmitting CUI. The assessments focus on the overall effectiveness of the security safeguards intended to satisfy the enhanced security requirements defined in [SP 800-172].\n\nAssessments can be conducted by system developers, system integrators, system owners, evaluators, auditors, or the security staff of organizations. The assessors or assessment teams begin by obtaining and reviewing the results from individual component product or compliance assessments. The assessors then determine the additional system-level assessments required to achieve the needed assurance using the procedures and methods contained in this publication and based on the specific implementation information provided by nonfederal organizations in their system security plans. Assessments can be used to compile and evaluate the evidence needed by organizations to determine the effectiveness of the safeguards implemented to protect CUI, the actions needed to mitigate security-related risks, and compliance to the enhanced security requirements."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 8)"}, {"role": "assistant", "content": "gnificant contributions from individuals and organizations in the public and private sectors whose constructive comments improved the overall quality, thoroughness, and usefulness of this publication.\nThe authors also wish to thank the NIST technical editing and production staff - Jim Foti, Jeff Brewer, Eduardo Takamura, Isabel Van Wyk, Cristina Ritfeld, Derek Sappington, and Chris Enloe - for their outstanding support in preparing this document for publication. ## Historical Contributions\n\nThe authors wish to acknowledge the following individuals for their historic contributions to this publication: Jon Boyens, Devin Casey, Ned Goren, Gary Guissanie, Jody Jacobs, Jeff Marron, Vicki Michetti, Mark Riddle, Mary Thomas, Gary Stoneburner, Patricia Toth, and Patrick Viscuso. ## 1. Introduction\n\nThe security assessment process gathers information and produces evidence to determine the effectiveness of security requirements by:\n\n- Identifying potential problems or shortfalls in security and risk management programs\n- Identifying security weaknesses and deficiencies in systems and the environments in which those systems operate\n- Prioritizing risk mitigation decisions and activities\n- Confirming that identified security weaknesses and deficiencies in the system and environment of operation have been addressed\n- Supporting continuous monitoring activities and providing information security situational awareness\n\n## 1.1. Purpose and Applicability\n\nThe purpose of this publication is to provide procedures for assessing the security requirements in NIST Special Publication (SP) 800-171, Protecting Controlled Unclassified Information (CUI) in Nonfederal Systems and Organizations [3]. Organizations can use the assessment procedures to generate evidence that the security requirements have been satisfied."}], "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": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to 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": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 Configuration Management?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n## Control Baselines for Information Systems and Organizations\n\n## Control Baselines for Information Systems and Organizations\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. In addition to the control baselines, this publication provides tailoring guidance and a set of working assumptions that help guide and inform the control selection process. Finally, this publication provides guidance on the development of overlays to facilitate control baseline customization for specific communities of interest, technologies, and environments of operation."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities. The information in this publication, including\nconcepts, practices, and methodologies may be used by federal agencies even before the completion of\nsuch companion publications. Thus, until each publication is completed, current requirements, guidelines,\nand procedures, where they exist, remain operative. For planning and transition purposes, federal\nagencies may wish to closely follow the development of these new publications by NIST. The 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. This 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."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 9)"}, {"role": "assistant", "content": "rdless of the incident response life cycle framework or model used, every organization should take incident response into consideration throughout their cybersecurity risk management activities. ## 1.\nIntroduction\n\nWithin this document, an event is any observable occurrence that involves computing assets, including physical and virtual platforms, networks, services, and cloud environments. Examples of events are user login attempts, the installation of software updates, and an application responding to a transaction request. Many events focus on security or have security implications. Adverse events are any events associated with a negative consequence regardless of cause, including natural disasters, power failures, or cybersecurity attacks. This guide addresses only adverse cybersecurity events . Additional analysis is often needed to determine whether adverse cybersecurity events indicate that a cybersecurity incident has occurred. ## A cybersecurity incident (or simply incident ) is\n\n…an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["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 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 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 Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 20)"}, {"role": "assistant", "content": "users are required to log out of the system after <A.03.01.01.ODP[05]: time period> of expected inactivity or when the following circumstances occur: <A.03.01.01.ODP[06]: circumstances> .\n## ASSESSMENT METHODS AND OBJECTS\n\n## Examine\n\n[SELECT FROM: access control policy and procedures; personnel termination or transfer policies and procedures; procedures for account management; list of active system accounts and the name of the individual associated with each account;\n\n8\n\nsystem design documentation; list of conditions for group and role membership; system configuration settings; notifications of recent transfers, separations, or terminations of employees; list of recently disabled system accounts and the name of the individual associated with each account; list of user activities that pose significant organizational risks; access authorization records; account management compliance reviews; system monitoring and audit records; system security plan; system-generated list of accounts removed; system-generated list of emergency accounts disabled; system-generated list of disabled accounts; other relevant documents and records]\n\n## Interview\n\n[SELECT FROM: personnel with account management responsibilities; system administrators; personnel with information security responsibilities; system developers]\n\n## Test\n\n[SELECT FROM: processes for account management on the system; mechanisms for implementing account management]\n\n## REFERENCES\n\nSource Assessment Procedures: AC-02, AC-02(03), AC-02(05), AC-02(13)\n\n## 03.01.02 Access Enforcement\n\n## ASSESSMENT OBJECTIVE\n\n## Determine if:\n\nA.03.01.02[01]: approved authorizations for logical access to CUI are enforced in accordance with applicable access control policies. A.03.01.02[02]: approved authorizations for logical access to system resources are enforced in accordance with applicable access control policies."}], "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": 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 Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 11)"}, {"role": "assistant", "content": "| MEDIAPROTECTION.........................................................................................................................\n| 16 |\n| 3.9 | PERSONNEL SECURITY ...................................................................................................................... | 16 |\n| 3.10 | PHYSICAL PROTECTION................................................................................................................... | 17 |\n| 3.11 | RISK ASSESSMENT........................................................................................................................... | 17 |\n| 3.12 | SECURITY ASSESSMENT .................................................................................................................. | 22 |\n| 3.13 | SYSTEMANDCOMMUNICATIONSPROTECTION............................................................................. | 23 |\n| 3.14 | SYSTEMANDINFORMATIONINTEGRITY........................................................................................."}], "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": 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 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 Security and Privacy Controls for Information Systems and Organizations provide? (Part 18)"}, {"role": "assistant", "content": "................................................................. 162\n3.10 MEDIA PROTECTION ..........................................................................................................\n171\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 ....................... 229\n3.16 RISK ASSESSMENT .............................................................................................................. 238\n3.17 SYSTEM AND SERVICES ACQUISITION .................................................................................. 249\n3.18 SYSTEM AND COMMUNICATIONS PROTECTION ................................................................... 292\n3.19 SYSTEM AND INFORMATION INTEGRITY .............................................................................. 332\n3.20 SUPPLY CHAIN RISK MANAGEMENT ..................................................................................... 363\nREFERENCES ................................................................................................................................ 374\nAPPENDIX A GLOSSARY .............................................................................................................. 394\nAPPENDIX B ACRONYMS ............................................................................................................ 424\nAPPENDIX C CONTROL SUMMARIES .........................................................................................."}], "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": 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 Control Baselines for Information Systems and Organizations provide? (Part 16)"}, {"role": "assistant", "content": "| ACCESSCONTROLFAMILY ......................................................................................................\n| 16 |\n| 3.2 | AWARENESSANDTRAININGFAMILY ....................................................................................... | 20 |\n| 3.3 | AUDIT ANDACCOUNTABILITY FAMILY ..................................................................................... | 21 |\n| 3.4 | ASSESSMENT,AUTHORIZATION,ANDMONITORINGFAMILY ..................................................... | 23 |\n| 3.5 | CONFIGURATIONMANAGEMENTFAMILY ................................................................................"}], "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": 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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 3)"}, {"role": "assistant", "content": "| help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n## Audience\n\n\n\n\n\nPages 2-6 provide a general overview of SP 800-171, R3 -helpful to business leaders or those new to SP 800-171. Pages 7-27 are for those who are tasked with managing the implementation SP 800-171. It is not all-encompassing, but it does provide tips and resources to help with getting started. This section serves as a bridge to the larger SP 800-171 publication. ## Key Term: Confidentiality\n\n\n\nConfidentiality refers to the protection of information from unauthorized access and disclosure . *Definitions in this document are intended as plain language. View the official definition within 32 CFR Part 2002 \"Controlled Unclassified Information.\"\n\n## A Suite of Guidance\n\nNIST's suite of CUI guidance (shown in the table below) focuses on protecting the confidentiality 2 of CUI in nonfederal systems and organizations and recommends specific security requirements to achieve that objective. This guide will focus on SP 800-171, Revision 3 . \n\n\n\n\n\nNIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Systems is a set of recommended security requirements for protecting the confidentiality of CUI. NIST SP 800-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 6)"}, {"role": "assistant", "content": "............................... 1 | Executive Summary.................................................................................................................\n1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Introduction ...................................................................................................................... | Introduction ...................................................................................................................... | 2 |\n| | Background - Zero Trust Principles and Zero Trust Architecture................................"}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["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 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": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\ns specification requirements -that is, capabilities that implement all or part of a control and that may be assessed (i.e., as part of the verification, validation, testing, and evaluation processes).\nFinally, organizations may use the term statement of work requirements to refer to actions that must be performed operationally or during system development."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 does CMMC Level 2 require for Maintenance?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n....................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10.\nIncident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information.\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThe new format for assessment procedures introduced in Special Publication (SP) 800-53A Revision 4, is\nfurther improved in this revision (SP 800-53A Revision 5). The format continues to reflect the\ndecomposition of assessment objectives into more granular determination statements wherever possible,\nthus providing the capability to identify and assess specific parts of security and privacy controls. Updates\nto SP 800-53A Revision 5:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ..............................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 require for Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "The guide was developed and is maintained by the Joint Task Force Transformation Initiative Interagency Working Group, part of an ongoing information security partnership among the U.S. Department of Defense, the Intelligence Community, the Committee on National Security Systems, the Department of Homeland Security, and U.S. federal civil agencies. SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. SP 800-53 Revision 4 is part of the NIST Special Publication 800-series that reports on the NIST Information Technology Laboratory's (ITL) computer security-related research, guidelines, and outreach. The publication provides a comprehensive set of security controls, three security control baselines (low, moderate, and high impact), and guidance for tailoring the appropriate baseline to specific needs according to the organization's missions, environments of operation, and technologies used. As the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Media Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n|\n| FIPS199 | National Institute of Standards and Technology. (2004). Standards for Security Categorization of Federal Information and Information Systems. (U.\nS. Department of Commerce, Washington, DC). Federal Information Processing Standards Publication (FIPS). 199. https://doi.org/10.6028/NIST.FIPS.199 |\n| Gilman | Gilman E., Barth D. (2017). Zero Trust Networks: Building Secure Systems in Untrusted Networks (O'Reilly Media, Inc., Sebastopol, CA). Primera edición. |\n| HWAM | Department of Homeland Security. (2015). Hardware Asset Management (HWAM) Capability Description . Disponible en https://www.uscert.gov/sites/default/files/cdm_files/HWAM_CapabilityDescription.pdf |\n| IBNVN | Cohen R., Barabash K., Rochwerger B., Schour L., Crisan D., Birke R., Minkenberg C., Gusat M., Recio R., Jain V. (2013). An Intent-based Approach for Network Virtualization. 2013 IFIP/IEEE International Symposium on Integrated Network Management (IM 2013) . (IEEE, Ghent, Belgium), pp. 42-50. Disponible en https://ieeexplore.ieee.org/document/6572968 |\n| JERICHO | The Jericho Forum. (2007). Jericho Forum Commandments , version 1.2. Disponible en https://collaboration.opengroup.org/jericho/commandments_v1.2.pdf |"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 12)"}, {"role": "assistant", "content": "| ..............................................................................................................\n17 |\n| 3.7 MAINTENANCE | ...................................................................................................................... 18 |\n| 3.8 MEDIAPROTECTION | .............................................................................................................. 18 |\n| 3.9 PERSONNEL SECURITY | ............................................................................................................ 18 |\n| 3.10 PHYSICAL PROTECTION ........................................................................................................ | 19 |\n| 3.11 RISKASSESSMENT | ................................................................................................................ 19 |\n| 3.12 SECURITY ASSESSMENT | ........................................................................................................"}], "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": 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 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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 5)"}, {"role": "assistant", "content": "s and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n## Overview\n\n## Structure of SP 800-171\n\nSP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page). | Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Understanding the Security Requirements in SP 800-171\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n\n\n## Top 5 Frequently Asked Questions\n\n## Top five questions NIST receives on SP 800-171:\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nance. The decision to select a particular set of enhanced security requirements will be based on the mission and business needs of federal agencies and guided and informed by ongoing risk assessments.\nThe enhanced security requirements for nonfederal systems processing, storing, or transmitting CUI associated with critical programs or high value assets will be conveyed to nonfederal organizations by federal agencies in a contract, grant, or other agreement. The application of the enhanced security requirements to subcontractors will also be addressed by federal agencies in consultation with nonfederal organizations."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\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.\nThe authors also wish to recognize the professional staff from the NIST Computer Security Division and the Applied Cybersecurity Division and the input from representatives from the OMB Office of Information and Regulatory Affairs (OIRA) Privacy Branch and the Federal CIO Council and Interagency Working Group for their contributions in helping to improve the technical content of the publication. Finally, the authors gratefully acknowledge the significant contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose insightful and constructive comments improved the quality, thoroughness, and usefulness of this publication. ## HISTORICAL 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."}], "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": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nblication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n- 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)"}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nScope and Applicability of SP 800-171. The security requirements in NIST SP 800-171 are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. Appropriately scoping requirements is an important factor in determining protection-related investment decisions and managing security risks for your business. You may limit the scope of the security requirements by isolating the system components in a separate security domain. Isolation can be achieved by implementing subnetworks with firewalls or other boundary protection devices. Security domains may employ physical separation, logical separation, or a combination of both. This approach can provide adequate security for CUI and avoid increasing the organization's security posture beyond what it requires for protecting its missions, operations, and assets.\n\n- Permit only qualified and authorized individuals to access the system for the purpose of initiating changes. Access restrictions include physical and logical access controls, software libraries, workflow automation, media libraries, abstract layers (i.e., changes implemented into external interfaces rather than directly into the system), and change windows (i.e., changes occur only during specified times)."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n3.4.2e | ENHANCED SECURITY REQUIREMENT Employ automated mechanisms to detect misconfigured or unauthorized system components; after detection, [ Selection (one or more): remove the components; place the components in a quarantine or remediation network ] to facilitate patching, re- configuration, or other mitigations. 3.4.2e_ODP[1] | One or more of the following is/are selected: remove the components; place the components in a quarantine or remediation network. 3.4.2e[a] | Automated mechanisms to detect misconfigured or unauthorized system components are identified."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Media Protection\n\nDescription: Protect system media, both paper and digital; limiting access to data on system media to authorized users; and sanitizing or destroying system media before disposal or release for reuse."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 8)"}, {"role": "assistant", "content": "or services that process, store, or transmit CUI or that provide security protections for those components or services as mandated by a federal agency in a contract, grant, or other agreement.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["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 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "tise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D.\nThe controls described assist organizations in defining the controls needed to satisfy minimum assurance requirements. Where additional assurance is desired to achieve risk management objectives, Table E-4 provides additional security controls and control enhancements to achieve enhanced assurance. Implementers should note that designation of assurance-related controls is not intended to imply a greater level of importance for such controls. Achieving adequate security for organizational information systems requires the correct combination of both functionality- and assurance-related security controls. ## 6 Security Controls\n\nAppendix F, the Security Control Catalog, provides a comprehensive range of countermeasures for organizations and information systems. The security controls are designed to be technologyneutral such that the focus is on the fundamental countermeasures needed to protect organizational information during processing, storage, or transmission. SP 800-53 Rev. 4, therefore, does not provide guidance on the application of security controls to specific technologies, environments of operation, or missions/business functions. These specific areas may be addressed using overlays (see below). Control enhancements are included with many security controls and are selected in order to increase the strength of the base control. Control enhancements are intended to be implemented only in conjunction with implementation of the base control. Some security controls and control enhancements include one or more assignment and selection statements. These are variable parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Media Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n17 The Audit and Accountability, Maintenance, Media Protection, and Physical Protection families do not contain enhanced security requirements at this time.\n\n## 3.8 MEDIA PROTECTION"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nderal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?\n| The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. |\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 12)"}, {"role": "assistant", "content": "| ..............................................................................................................\n17 |\n| 3.7 MAINTENANCE | ...................................................................................................................... 18 |\n| 3.8 MEDIAPROTECTION | .............................................................................................................. 18 |\n| 3.9 PERSONNEL SECURITY | ............................................................................................................ 18 |\n| 3.10 PHYSICAL PROTECTION ........................................................................................................ | 19 |\n| 3.11 RISKASSESSMENT | ................................................................................................................ 19 |\n| 3.12 SECURITY ASSESSMENT | ........................................................................................................"}], "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": 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 NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nlar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172A Natl. Inst. Stand. Technol. Spec. Publ. 800-172A, 62 pages (March 2022)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["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 in Nonfederal Systems and Organizations provide? (Part 12)"}, {"role": "assistant", "content": "uidance, policy, and requirements on handling CUI [4]. This includes approved CUI categories and descriptions, the basis for safeguarding and dissemination controls, and procedures for the use of CUI.\n2 The CUI federal regulation [5] provides guidance to federal agencies on the designation, safeguarding, marking, dissemination, decontrolling, and disposition of CUI; establishes self-inspection and oversight requirements; and delineates other facets of the program. The CUI regulation requires federal agencies that use federal information systems 3 to process, store, or transmit CUI to comply with NIST standards and guidelines. The responsibility of federal agencies to protect CUI does not change when such information is shared with nonfederal organizations. 4 Therefore, a similar level of protection is needed when CUI is processed, stored, or transmitted by nonfederal organizations using nonfederal systems. 5 To maintain a consistent level of protection, the security requirements for safeguarding CUI in nonfederal systems and organizations must comply with Federal Information Processing Standards (FIPS 199) publication [6] and FIPS 200 [7]. The requirements are derived from the controls in NIST Special Publication (SP) 800-53 [8]. ## 1.1. Purpose and Applicability\n\nThis publication provides federal agencies with recommended security requirements 6 for protecting the confidentiality of CUI 7 when such information is resident in nonfederal systems and organizations and where there are no specific safeguarding requirements prescribed by the authorizing law, regulation, or government-wide policy for the CUI category listed in the CUI\n\n1 CUI is any information that a law, regulation, or government-wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under EO 13526 [2], any predecessor or successor order, or the Atomic Energy Act [3] as amended."}], "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": 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 additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 7)"}, {"role": "assistant", "content": "dell 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).\nThe authors also wish to recognize the professional staff from\nthe NIST Computer Security Division and Applied Cybersecurity Division, and the representatives\nfrom the Federal Chief Information Officer (CIO) Council, Federal Chief Information Security\nOfficer (CISO) Council, and Federal Privacy Council 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. 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\nHISTORICAL CONTRIBUTIONS TO NIST SPECIAL PUBLICATION 800-53A\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nThe authors wanted to acknowledge the many individuals who contributed to previous versions of Special\nPublication 800-53A since its inception in 2005."}], "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": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.4.1 | Requisitos de la red para admitir una ZTA... 3.4.1 Requisitos de la red para admitir una ZTA\n\n1. 3.4.1, todo el tráfico se inspecciona, se registra en la red y se analiza con el fin de identificar y reaccionar ante posibles ataques contra la empresa."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.14 (NIST 3.1.14)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.14. 3.1.14."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.14", "cmmc_practice_id": "AC.L2-3.1.14", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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 18)"}, {"role": "assistant", "content": "rses, 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.\n## Related Resources:\n\n- View all SP 800-171 Awareness and Training Requirements and Assessment Procedures\n- NIST Free and Low-Cost Online Cybersecurity Learning Content\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n- NARA CUI training\n- Center for Development of Security Excellence Security Awareness Hub\n\n81&/$66,),('GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1)250$7,21GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1\n\n\n\n## Getting Started with Audit and Accountability\n\n## Family: Audit and Accountability\n\nDescription: Creating, protecting, and retaining system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity; and ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. ## Getting Started with Audit and Accountability\n\n\n\nUnderstand and track who is performing actions within business system(s), what those actions are, and when those actions are taken. Having the ability to review system activity and analyze records, generate reports, resolve audit log process failures, and protect audit data gives the business insight into potential unauthorized activity and improves the ability to respond quickly and appropriately. Consider automated tools for conducting audit and logging activities. Products range from free, open-source tools to commercially available ones. ## Define, maintain, and protect 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."}], "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": 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 require for Physical Protection?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\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. 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": "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 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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "The guide was developed and is maintained by the Joint Task Force Transformation Initiative Interagency Working Group, part of an ongoing information security partnership among the U.S. Department of Defense, the Intelligence Community, the Committee on National Security Systems, the Department of Homeland Security, and U.S. federal civil agencies. SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. SP 800-53 Revision 4 is part of the NIST Special Publication 800-series that reports on the NIST Information Technology Laboratory's (ITL) computer security-related research, guidelines, and outreach. The publication provides a comprehensive set of security controls, three security control baselines (low, moderate, and high impact), and guidance for tailoring the appropriate baseline to specific needs according to the organization's missions, environments of operation, and technologies used. As the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Planning?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe enhanced security requirements are organized into 14 families consistent with the families for basic and derived requirements. Each family contains the requirements related to the general security topic of the family. The families are closely aligned with the minimum security requirements for federal information and information systems in [FIPS 200]. The security requirements for contingency planning , system and services acquisition , and planning are not included within the scope of this publication due to the tailoring criteria in [SP 800-171]. Table 1 lists the security requirement families addressed in this publication. 17\n\n- 3.11.4e Document or reference in the system security plan the security solution selected, the rationale for the security solution, and the risk determination."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 10)"}, {"role": "assistant", "content": "and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance.\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement. Tailoring: The process by which control baselines are modified to achieve certain organizational goals and objectives. Definitions provided are intended as plain language. Review the NIST Glossary for official NIST definitions. Determine if your business has CUI. ## General Tips for Getting Started with NIST SP 800-171\n\nEveryone will have different approaches to getting started, but here are a few tips to get you started down the right path:\n\nUnderstand current (or future) legal, regulatory, or contractual requirements for protecting CUI. The federal agency is responsible for communicating what CUI the business is responsible for protecting as part of the contractual arrangement. If there are questions, reach out to the contracting officer. The business may also have additional compliance requirements beyond SP 800-171. If so, an initial task might be to understand where the requirements overlap and where they differ. With that information, the business can begin addressing requirements that meet multiple compliance requirements. Understand how CUI flows into, within, and out of the business. \n\nInventorying what systems or components the business has, and how the data flows into, within, and out of those systems or components, helps practitioners understand the scope of applicability of SP 800-171 security requirements to business systems. \n\nScope and Applicability of SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 2)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | ## 1 Introduction In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nDescription: Ensuring personnel are made aware of the security risks associated with their activities and of the applicable laws, directives, policies, standards, regulations, or procedures related to the security of organizational systems; and ensuring that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities.\n\nRegularly provide basic and advanced security literacy training to new and existing staff. Customize the content to make it relevant -based on the systems that personnel have authorized access to, contextualized to the work environments of personnel (e.g., telework, shop floor), and tailored to the specific roles of personnel. The content should include:"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n## Family: Incident Response"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n5 There are four families in [SP 800-171] that do not contain enhanced security requirements: Audit and Accountability, Maintenance, Media Protection, and Physical Protection. | 3.1.1e | ENHANCED SECURITY REQUIREMENT Employ dual authorization to execute critical or sensitive system and organizational operations. | ENHANCED SECURITY REQUIREMENT Employ dual authorization to execute critical or sensitive system and organizational operations."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "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.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\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. 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## RISK MANAGEMENT\n\nOrganizations must exercise due diligence in managing information security and privacy risk. This is accomplished, in part, by establishing a comprehensive risk management program that uses the flexibility inherent in NIST publications to categorize systems, select and implement security and privacy controls that meet mission and business needs, assess the effectiveness of the controls, authorize the systems for operation, and continuously monitor the systems."}], "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": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.1.2 | ZTA y el uso de la microsegmentación... 3.1.2 ZTA y el uso de la microsegmentación\n\nUna empresa puede optar por implementar una ZTA basada en el emplazamiento de los recursos individuales o grupos de recursos en un único segmento de red protegido por un componente de seguridad denominado puerta de enlace ( gateway )."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Media Protection\n\nDescription: Protect system media, both paper and digital; limiting access to data on system media to authorized users; and sanitizing or destroying system media before disposal or release for reuse."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 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 does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 18)"}, {"role": "assistant", "content": "ity |\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.\nEach assessment objective includes a set of determination statements related to the CUI enhanced security requirement that is the subject of the assessment. Organization-defined parameters (ODP) that are part of selected enhanced security requirements are included in the initial determination statements for the assessment procedure. ODPs are included since the specified parameter values are used in subsequent determination statements. ODPs are numbered sequentially and noted in bold italics . Determination statements reflect the content of the enhanced security requirements to ensure traceability of the assessment results to the requirements. The application of an assessment procedure to an enhanced security requirement produces assessment findings . The findings are used to determine if the enhanced security requirement has been satisfied. Assessment objects are associated with the specific items being assessed. These objects can include specifications, mechanisms, activities, and individuals. Specifications are the document-based artifacts (e.g., security policies, procedures, plans, requirements, functional specifications, architectural\n\n5 There are four families in [SP 800-171] that do not contain enhanced security requirements: Audit and Accountability, Maintenance, Media Protection, and Physical Protection. 6 For additional guidance on assessment processes, methods, and objects, see [SP 800-53A]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\ndesigns) associated with a system. Mechanisms are the specific hardware, software, or firmware safeguards employed within a system."}], "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": 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 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control.\n\nThe Defense Science Board Report, Resilient Military Systems and the Advanced Cyber Threat [DSB 2013], provides a sobering assessment of the vulnerabilities in the United States Government, the U.S. critical infrastructure, and the systems supporting the mission-essential operations and assets in the public and private sectors.\n\n'…The Task Force notes that the cyber threat to U.S. critical infrastructure is outpacing efforts to reduce pervasive vulnerabilities, so that for the next decade at least the United States must lean significantly on deterrence to address the cyber threat posed by the most capable U.S. adversaries. It is clear that a more proactive and systematic approach to U.S. cyber deterrence is urgently needed…'"}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes assist with maintaining cross-references | |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ID.RA-09 | The authenticity and integrity of hardware and software are assessed prior to acquisition and use | Medium | N1: See the notes for ID.RA."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software... 3.1.3 ZTA y el uso de una infraestructura de red y perímetros definidos a través de software\n\nEl último modelo utiliza la infraestructura de red para implementar una ZTA."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 18)"}, {"role": "assistant", "content": "iesgo de esa misión y no puede lograrse simplemente con una sustitución masiva de la tecnología. Ahora bien, muchas organizaciones ya cuentan con elementos de la ZTA en su infraestructura empresarial.\nEstas deben tratar de implementar gradualmente los principios de confianza cero, cambios en los procesos y soluciones tecnológicas para proteger sus datos y funciones empresariales mediante casos de uso. La mayoría de las infraestructuras funcionarán en un modo híbrido, al tiempo que seguirán invirtiendo en iniciativas de modernización de TI (tecnologías de la información) y mejorando los procesos de negocio de la organización. Para que este sistema sea efectivo, se deben implementar prácticas exhaustivas de seguridad y recuperación de la información. Si se equilibra con las orientaciones y las políticas de ciberseguridad existentes, la gestión de la identidad y del acceso, el monitoreo continuo y las mejores prácticas, la ZTA puede proteger contra las amenazas comunes y mejorar la postura de seguridad de las empresas mediante un enfoque de riesgo gestionado. ## 1.1 Historia de los programas de confianza cero relacionados con las agencias federales\n\nEl concepto de confianza cero ha estado presente en la ciberseguridad antes de que se acuñara el término confianza cero . La Agencia de Sistemas de Defensa de la Información (DISA, por su nombre en inglés Defense Information Systems Agency) y el Departamento de Defensa publicaron un trabajo sobre una estrategia empresarial más segura denominada «núcleo negro» (BCORE, por su nombre en inglés black core ), la cual implicaba pasar de un modelo de seguridad basado en el perímetro a uno focalizado en la seguridad de las transacciones individuales (JERICHO)."}], "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": 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 Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Access Control\n\n## Getting Started with Access Control"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\n\nThe purpose of this publication is to provide procedures for assessing the security requirements in NIST Special Publication (SP) 800-171, Protecting Controlled Unclassified Information (CUI) in Nonfederal Systems and Organizations [3]. Organizations can use the assessment procedures to generate evidence that the security requirements have been satisfied. The scope of the security assessments conducted using the procedures described in this publication is guided and informed by the system security plans for systems that process, store, or transmit CUI. The assessment procedures offer the flexibility to customize assessments based on organizational policies and requirements, known threat and vulnerability information, system and platform dependencies, operational considerations, and tolerance for risk."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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 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 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": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 18)"}, {"role": "assistant", "content": "basis through a dynamic policy that takes the current status of the user, service, and requested resource into account. The above requirements can only be met through a comprehensive policy framework.\nThis document provides guidance for developing a policy framework that will form the foundation for realizing a zero trust architecture (ZTA) while incorporating zero trust principles into its design for cloud-native applications. The policy framework should also consist of a comprehensive set of policies that span all critical entities and resources in the application stack, including the network, network devices, users, and services. ## Background - Zero Trust Principles and Zero Trust Architecture\n\nA summary of the zero trust principles and the definition of a zero trust architecture, as described in SP 800-207, Zero Trust Architecture [1], are:\n\n- Zero trust is the term for an evolving set of cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users and resources. It is a set of security primitives rather than a particular set of technologies. Zero trust assumes that there is no implicit trust granted to user accounts based solely on their physical or network location (i.e., local area networks versus the internet) or to endpoints (devices) based on their ownership (e.g., enterprise or personally owned). Zero trust focuses on protecting resources (e.g., devices, services, workflows, network accounts) rather than network segments, as the network location is no longer seen as the prime component to the security posture of the resource. - A zero trust architecture uses zero trust principles to plan industrial and enterprise infrastructures and workflows. NIST's guidance on zero trust also contains 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."}], "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": 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 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nespective of impact level. In addition to the control baselines, this publication provides tailoring guidance and a set of working assumptions that help guide and inform the control selection process.\nFinally, this publication provides guidance on the development of overlays to facilitate control baseline customization for specific communities of interest, technologies, and environments of operation."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 12)"}, {"role": "assistant", "content": "sections, controls, and control enhancements. These examples are illustrative in nature and are not intended to limit or constrain the application of controls or control enhancements by organizations.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................."}], "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": 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 Access Control?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 5)"}, {"role": "assistant", "content": "s and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n## Overview\n\n## Structure of SP 800-171\n\nSP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page). | Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Understanding the Security Requirements in SP 800-171\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n\n\n## Top 5 Frequently Asked Questions\n\n## Top five questions NIST receives on SP 800-171:\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 13)"}, {"role": "assistant", "content": "or, scope, and level of effort for the assessment as well as the degree of assurance that the security requirements have been satisfied. See SP 800-53A, Appendix C, Assessment Method Descriptions [5].\nThe structure and content of an assessment procedure are provided in the example below:\n\n## 03.01.06 Least Privilege - Privileged Accounts\n\n## ASSESSMENT OBJECTIVE\n\nMulti-Part Determination Statement and ODP for Security Requirement\n\nSecurity Requirement Name\n\n## Determine if:\n\nA.03.01.06.ODP[01]: personnel or roles to which privileged accounts on the system are to be restricted are defined . A.03.01.06.a: privileged accounts on the system are restricted to <A.03.01.06.ODP[01]: personnel or roles> . A.03.01.06.b: users (or roles) with privileged accounts are required to use non-privileged accounts when accessing non-security functions or non-security information. ## ASSESSMENT METHODS AND OBJECTS\n\n## Examine\n\n[SELECT FROM: access control policy and procedures; procedures for least privilege; list of system-generated privileged accounts; list of system administration personnel; system audit records; system configuration settings; system security plan; list of system-generated security functions or security-relevant information assigned to system accounts or roles; other relevant documents or records]\n\n## Interview\n\n[SELECT FROM: personnel with responsibilities for defining least privileges; personnel with information security responsibilities; system administrators]\n\n## Test\n\n[SELECT FROM: mechanisms for implementing least privilege functions]\n\n## REFERENCES\n\nSource Assessment Procedures: AC-06(02), AC-06(05)\n\nDetermination statements have alphanumeric identifiers. Each determination statement begins with the letter ' A ' to indicate that it is part of an assessment procedure."}], "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": 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 Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n8 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products).\nSince many of the technical security controls defined in Appendix F are implemented in hardware, software, and firmware components of information systems, organizations can obtain significant benefit from the acquisition and employment of information technology products evaluated against the requirements of ISO/IEC 15408. The use of such products can provide evidence that certain security controls are implemented correctly, operating as intended, and producing the desired effect in satisfying stated security requirements."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by\nNIST in accordance with its assigned statutory responsibilities. The information in this publication,\nincluding concepts, practices, and methodologies may be used by federal agencies even before the\ncompletion of such companion publications. Thus, until each publication is completed, current\nrequirements, guidelines, and procedures, where they exist, remain operative. For planning and\ntransition purposes, federal agencies may wish to closely follow the development of these new\npublications by NIST.\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.\n\nDEVELOPMENT OF INFORMATION SYSTEMS, COMPONENTS, AND SERVICES"}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - The application is made up of a set of loosely coupled components called microservices. Each of the microservices can be hosted on different physical or virtual machines (VMs) and even be geographically distributed (e.g., within several facilities that belong to the enterprise, such as the headquarters, branch offices, and in various cloud service provider environments). - Any transaction involving the application may also involve one or more inter-service (microservice) calls across the network. - A widespread feature (though not necessarily a requirement for cloud-native applications) is the presence of a software platform called the service mesh that provides an integrated set of all application services (e.g., services discovery, networking connections, communication resilience, and security services like authentication and authorization). - Zero trust is the term for an evolving set of cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users and resources. It is a set of security primitives rather than a particular set of technologies."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. | Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 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 does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 15)"}, {"role": "assistant", "content": "Modelo de portal de recursos........................................................................................................................27 | Figura 5: Modelo de portal de recursos........................................................................................................................27 | | | Figura 6: Entorno de prueba de la aplicación ...............................................................................................................28 | Figura 6: Entorno de prueba de la aplicación ...............................................................................................................28 | | | Figura 7: Proceso del algoritmo de confianza...............................................................................................................29 | Figura 7: Proceso del algoritmo de confianza...............................................................................................................29 | | | Figura 8: Empresa con empleados remotos .................................................................................................................36 | Figura 8: Empresa con empleados remotos .................................................................................................................36 | | | Figura 9: Ejemplo de multinube ...................................................................................................................................36 | Figura 9: Ejemplo de multinube ...................................................................................................................................36 | | | Figura 10: Empresa con acceso para personal externo ................................................................................................38 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------| | Figura 11: Colaboración entre empresas......................................................................................................................39 | | Figura 12: Ciclo de implantación de una ZTA................................................................................................................52 | | Lista de tablas | ## 1 Introducción La infraestructura de una empresa típica se ha convertido en algo cada vez más complejo."}], "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": 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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.4.3. 3.4.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.07.04.b: media with diagnostic and test programs are checked for malicious code before the media are used in the system.\n\n[SELECT FROM: processes for approving, controlling, and monitoring maintenance tools; mechanisms for supporting or implementing the approval, control, or monitoring of maintenance tools; processes for preventing the unauthorized removal of information; processes for inspecting media for malicious code; mechanisms for supporting media sanitization or the destruction of equipment; mechanisms for supporting the verification of media sanitization; processes for inspecting maintenance tools; mechanisms for supporting or implementing the inspection of maintenance tools; mechanisms for supporting or implementing the inspection of media used for maintenance]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Media Protection\n\nDescription: Protect system media, both paper and digital; limiting access to data on system media to authorized users; and sanitizing or destroying system media before disposal or release for reuse."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process.\nThe baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . A separate guideline, SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, provides specific guidelines that facilitate periodic assessment of security controls to ensure that controls have been implemented correctly, are operating as intended, and are meeting the organization's security requirements. ## 2 NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)\n\nNIST SP 800-39, Managing Information Security Risk , defines risk management as 'the program and supporting processes to manage information security risk to organizational operations (including mission, functions, and reputation), organizational assets, individuals, other organizations, and the Nation'. To integrate the risk management process throughout an organization and to address its mission and business concerns, a three-tiered approach is employed. The process is carried out across three tiers with the objective of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Identification and Authentication?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n| Executive Summary.................................................................................................................\n1 | Executive Summary................................................................................................................. 1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Introduction ...................................................................................................................... | Introduction ...................................................................................................................... | 2 |\n| | Background - Zero Trust Principles and Zero Trust Architecture................................"}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 12)"}, {"role": "assistant", "content": "| Approaches for Deployment and the Limitations of Network-Tier Policies | ...............17 |\n| 4.6.2. | Prerequisites for the Deployment of Identity-Tier Policies........................................18 | |\n| 4.6.3."}], "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": 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 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 additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 20)"}, {"role": "assistant", "content": "e—\nensuring that those systems, components, and services are sufficiently trustworthy and provide\nthe necessary resilience to support the economic and national security interests of the United\nStates.\nThis update to NIST Special Publication (SP) 800-53 responds to the call by the DSB by\nembarking on a proactive and systemic approach to develop and make available to a broad base\nof public and private sector organizations a comprehensive set of safeguarding measures for all\ntypes of computing platforms, including general purpose computing systems, cyber-physical\nsystems, cloud-based systems, mobile devices, Internet of Things (IoT) devices, weapons\nsystems, space systems, communications systems, environmental control systems, super\ncomputers, and industrial control systems. Those safeguarding measures include implementing\nsecurity and privacy controls to protect the critical and essential operations and assets of\norganizations and the privacy of individuals. The objectives are to make the information systems\nwe depend on more penetration-resistant, limit the damage from attacks when they occur,\nmake the systems cyber-resilient and survivable, and protect individuals’ privacy. Revision 5 of this foundational NIST publication represents a multi-year effort to develop the\nnext generation of security and privacy controls that will be needed to accomplish the above\nobjectives. It includes changes to make the controls more usable by diverse consumer groups\n(e.g., enterprises conducting mission and business functions; engineering organizations\ndeveloping information systems, IoT devices, and systems-of-systems; and industry partners\nbuilding system components, products, and services)."}], "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": 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 System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nework. The assessment procedures, executed at various phases of the system\ndevelopment life cycle, are consistent with the security and privacy controls in NIST Special\nPublication 800-53, Revision 5.\nThe procedures are customizable and can be easily tailored to\nprovide organizations with the needed flexibility to conduct security and privacy control\nassessments that support organizational risk management processes and are aligned with the\nstated risk tolerance of the organization. Information on building effective security and privacy\nassessment plans is also provided with guidance on analyzing assessment results."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 9)"}, {"role": "assistant", "content": "| Enterprise Infrastructure Layer ...................................................................................\n| 6 |\n| | Designing a Policy Framework for ZTA for Cloud-Native Application Environments. 7 | Designing a Policy Framework for ZTA for Cloud-Native Application Environments. 7 |\n| | Functional Components of Identity-Based Segmentation Policies for ZTA.................. | 8 |\n| | Shortcomings of Identity-Based Segmentation Policies for Enterprise ZTA ................"}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["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 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes making on when to escalate or elevate incident response activities."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n- Identifying potential problems or shortfalls in security and risk management programs\n- Identifying security weaknesses and deficiencies in systems and the environments in which those systems operate\n- Prioritizing risk mitigation decisions and activities\n- Confirming that identified security weaknesses and deficiencies in the system and environment of operation have been addressed\n- Supporting continuous monitoring activities and providing information security situational awareness\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n[SELECT FROM: access control policy and procedures; procedures for publicly accessible content; list of users authorized to post publicly accessible content on organizational systems; training materials or records; records of publicly accessible information reviews; records of response to CUI discovered on public websites; system audit logs; security awareness training records; system security plan; other relevant documents or records]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 12)"}, {"role": "assistant", "content": "for the Federal agency's enterprise, but also for the Executive Branch as a whole. The E.O. states:\n\n- '…The executive branch operates its information technology (IT) on behalf of the American people.\nIts IT and data should be secured responsibly using all United States Government capabilities...'\n- '…Cybersecurity risk management comprises the full range of activities undertaken to protect IT and data from unauthorized access and other cyber threats, to maintain awareness of cyber threats, to detect anomalies and incidents adversely affecting IT and data, and to mitigate the impact of, respond to, and recover from incidents…'\n\nOMB Memorandum M-17-25, Reporting Guidance for Executive Order on Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure [OMB M-17-25] provides implementation guidance to Federal agencies for E.O. 13800. The memorandum states:\n\n'… An effective enterprise risk management program promotes a common understanding for recognizing and describing potential risks that can impact an agency's mission and the delivery of services to the public. Such risks include, but are not limited to, strategic, market, cyber, legal,\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\nreputational, political, and a broad range of operational risks such as information security, human capital, business continuity, and related risks…'\n\n'… Effective management of cybersecurity risk requires that agencies align information security management processes with strategic, operational, and budgetary planning processes…'\n\nOMB Circular 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)."}], "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": 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 Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-53A\nRevision 5\n\nAssessing Security and Privacy Controls in\nInformation Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53Ar5\n\n\f NIST Special Publication 800-53A\nRevision 5\n\n Assessing Security and Privacy Controls\nin Information Systems and\nOrganizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53Ar5\n\nJanuary 2022\n\nNational Institute of Standards and Technology\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce\nfor Standards and Technology & Director, National Institute of Standards and Technology\n\nU.S. Department of Commerce\nGina M. Raimondo, Secretary\n\n\fAuthority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the\nFederal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq., Public Law\n(P.L.) 113-283. NIST is responsible for developing information security standards and guidelines,\nincluding minimum requirements for federal information systems. Such information security\nstandards and guidelines shall not apply to national security systems without the express\napproval of the appropriate federal officials exercising policy authority over such systems. This\nguideline is consistent with the requirements of the Office of Management and Budget (OMB)\nCircular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made\nmandatory and binding on federal agencies by the Secretary of Commerce under statutory\nauthority. Nor should these guidelines be interpreted as altering or superseding the existing\nauthorities of the Secretary of Commerce, OMB Director, or any other federal official. This\npublication may be used by nongovernmental organizations on a voluntary basis and is not\nsubject to copyright in the United States."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Media Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n17 The Audit and Accountability, Maintenance, Media Protection, and Physical Protection families do not contain enhanced security requirements at this time.\n\n## 3.8 MEDIA PROTECTION"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n| Identify the role(s) responsible for security and provide the necessary resources. | Whether it is just one person or multiple people within the business, ensure roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nderal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?\n| The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. |\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-09-08\n\n## How to Cite this NIST Technical Series Publication:\n\nChandramouli R, Butcher Z (2023) A Zero-Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Location Environments. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-207A. https://doi.org/10.6028/NIST.SP.800-207A\n\n## Author ORCID iDs\n\nRamaswamy Chandramouli: 0000-0002-7387-5858\n\n## Contact Information\n\nsp800-207A-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nOne of the basic tenets of zero trust is to remove the implicit trust in users, services, and devices based only on their network location, affiliation, and ownership. NIST Special Publication 800207 has laid out a comprehensive set of zero trust principles and referenced zero trust architectures (ZTA) for turning those concepts into reality. A key paradigm shift in ZTAs is the change in focus from security controls based on segmentation and isolation using network parameters (e.g., Internet Protocol (IP) addresses, subnets, perimeter) to identities. From an application security point of view, this requires authentication and authorization policies based on application and service identities in addition to the underlying network parameters and user identities."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["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 5)"}, {"role": "assistant", "content": "s and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n## Overview\n\n## Structure of SP 800-171\n\nSP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page). | Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Understanding the Security Requirements in SP 800-171\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n\n\n## Top 5 Frequently Asked Questions\n\n## Top five questions NIST receives on SP 800-171:\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Planning?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities. The information in this publication, including\nconcepts, practices, and methodologies may be used by federal agencies even before the completion of\nsuch companion publications. Thus, until each publication is completed, current requirements, guidelines,\nand procedures, where they exist, remain operative. For planning and transition purposes, federal\nagencies may wish to closely follow the development of these new publications by NIST. SP 800-53A provides guidance on assessing controls in information security program plans,\nprivacy program plans, system security plans, and privacy plans. Where the guidance refers to all\nplans listed above, the term “security and privacy plans” is used. If the guidance is specific to a\nsingle type of plan (e.g., system security plan), the specific type of plan is specified. CHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos...............................................24"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"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": "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 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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 17)"}, {"role": "assistant", "content": "on infrastructure that encompasses multi-cloud and hybrid environments\n\n## Introduction\n\nZero trust (ZT) tenets or principles have been accepted as the guide markers for architecting all applications.\nThere are several reasons why adherence to these tenets is critical for obtaining necessary security assurances, especially for cloud-native applications. The enterprise application environments for this class of applications are highly geographically distributed and span multiple cloud and on-premises environments (e.g., headquarters, enterprise-operated data centers, branch offices). Further, the user base consists of both remote and on-premises employees. These two features call for establishing trust in all of the data sources and computing services of the enterprise - irrespective of their location - through secure communication and the validation of access policies. Apart from geographic distribution, another common feature of cloud-native applications is the presence of many microservices that are loosely coupled and collectively support business processes through extensive inter-service calls. This is augmented by an integrated infrastructure for providing all application services called the service mesh. These features emphasize the concept of identity for the various components of the application in the form of microservices as well as the users who access them through direct calls or clients (other services). This in turn highlights the critical need for authenticating these identities and for providing legitimate access on a per-session basis through a dynamic policy that takes the current status of the user, service, and requested resource into account. The above requirements can only be met through a comprehensive policy framework."}], "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": 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 does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication contains comprehensive updates to the Risk Management Framework . The updates include an alignment with the constructs in the NIST Cybersecurity Framework; the integration of privacy risk management processes; an alignment with system life cycle security engineering processes; and the incorporation of supply chain risk management processes. Organizations can use the frameworks and processes in a complementary manner within the RMF to effectively manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. Revision 2 includes a set of organization-wide RMF tasks that are designed to prepare information system owners to conduct system-level risk management activities. The intent is to increase the effectiveness, efficiency, and cost-effectiveness of the RMF by establishing a closer connection to the organization's missions and business functions and improving the communications among senior leaders, managers, and operational personnel. * Note: The publication pertains to information systems, which are discrete sets of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information, whether such information is in digital or non-digital form. Information resources include information and related resources, such as personnel, equipment, funds, and information technology. Therefore, information systems may or may not include hardware, firmware, and software. This publication is intended to help organizations manage security and privacy risk, and to satisfy the requirements in the Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 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 Configuration Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n| 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 |"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 5)"}, {"role": "assistant", "content": "s and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n## Overview\n\n## Structure of SP 800-171\n\nSP 800-171 security requirements are organized into 17 families, as illustrated in the table below. Each family is further broke n down into requirements related to the family's general security topic (see the example at the bottom of the page). | Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Understanding the Security Requirements in SP 800-171\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Overview\n\n\n\n## Top 5 Frequently Asked Questions\n\n## Top five questions NIST receives on SP 800-171:\n\n| How can I 'comply' with SP 800-171? | NIST does not have a role in determining compliance with the security requirements in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 12)"}, {"role": "assistant", "content": "omposition 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.\nUpdates\nto SP 800-53A Revision 5:\n\n•\n\n•\n•\n\n•\n\n•\n•\n\nIdentify determination statements for organization-defined parameters (ODPs) first and separately\nfrom the determination statements for each control item;\nImprove the readability of the assessment procedures;\nProvide a structured schema for automated tools when assessment information is imported into such\ntools;\nProvide greater flexibility in conducting assessments by giving organizations the capability to target\ncertain aspects of controls (highlighting the particular weaknesses and/or deficiencies in controls),\nImprove the efficiency of security and privacy control assessments;\nSupport continuous monitoring and ongoing authorization programs by providing a greater number\nof component parts of security and privacy controls that can be assessed at organization-defined\nfrequencies and degrees of rigor. The ability to apply assessment and monitoring resources in a targeted and precise manner and\nsimultaneously maximize the use of automation technologies can result in more timely and cost-effective\nassessment processes for organizations. Note: NIST [SP 800-53] will be updated accordingly to ensure that the numbering scheme for all security and privacy\ncontrols is consistent with the new format introduced in this publication. vii\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."}], "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": 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 additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-09-25 Supersedes NIST Special Publication 800-161r1 (May 2022) https://doi.org/10.6028/NIST.SP.800-161r1\n\n## How to Cite this NIST Technical Series Publication\n\nBoyens J, Smith A, Bartol N, Winkler K, Holbrook A, Fallon M (2022) Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-161r1-upd1, Includes updates as of Novem ber 1, 2024. https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n\n## Author ORCID iDs\n\nJon Boyens: 0000-0002-5666-8750\n\n## Contact Information\n\nscrm-nist@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/161/r1/upd1/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nOrganizations are concerned about the risks associated with products and services that may potentially contain malicious functionality, are counterfeit, or are vulnerable due to poor manufacturing and development practices within the supply chain."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 does CMMC Level 2 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n- Federal agencies responsible for managing and protecting CUI\n- Nonfederal organizations responsible for protecting CUI\n- Individuals with system development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Individuals with acquisition or procurement responsibilities (e.g., contracting officers)\n- Individuals with system, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Individuals with security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, analysts, independent verifiers and validators)\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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 does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nesses at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems.\n- Facilitates the categorization of information and systems, the selection, implementation, assessment, and monitoring of controls, and the authorization of information systems and common controls; 11\n- Promotes the use of automation for near real-time risk management and ongoing system and control authorization through the implementation of continuous monitoring processes;\n- Encourages the use of correct and timely metrics to provide senior leaders and managers with the necessary information to make cost-effective, risk-based decisions for information systems supporting their missions and business functions;\n- Facilitates the integration of security and privacy requirements 12 and controls into enterprise architecture, 13 SDLC, acquisition processes, and systems engineering processes;\n- Connects risk management processes at the organization and mission/business process levels to risk management processes at the information system level through a senior accountable official for risk management and risk executive (function); 14 and\n- Establishes responsibility and accountability for controls implemented within information systems and inherited by those systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "s\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV.\n5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nRISK MANAGEMENT\n\nOrganizations must exercise due diligence in managing information security and privacy risk. This\nis accomplished, in part, by establishing a comprehensive risk management program that uses\nthe flexibility inherent in NIST publications to categorize systems, select and implement security\nand privacy controls that meet mission and business needs, assess the effectiveness of the\ncontrols, authorize the systems for operation, and continuously monitor the systems. Exercising\ndue diligence and implementing robust and comprehensive information security and privacy risk\nmanagement programs can facilitate compliance with applicable laws, regulations, executive\norders, and governmentwide policies. Risk management frameworks and risk management\nprocesses are essential in developing, implementing, and maintaining the protection measures\nnecessary to address stakeholder needs and the current threats to organizational operations\nand assets, individuals, other organizations, and the Nation. Employing effective risk-based\nprocesses, procedures, methods, and technologies ensures that information systems and\norganizations have the necessary trustworthiness and resiliency to support essential mission and\nbusiness functions, the U.S. critical infrastructure, and continuity of government. vi\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 2)"}, {"role": "assistant", "content": "ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Awareness and Training?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos...............................................24"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 8)"}, {"role": "assistant", "content": "ederal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui.\n- NIST is responsible for developing and publishing the security requirements for the protection of CUI. How requirements are mandated, and any compliance issues related to nonfederal implementation of SP 800-171, are the responsibility of the federal agency requiring its use , as expressed in a specific contract or agreement. ## Additional NIST Resources\n\n- NIST's Protecting CUI Frequently Asked Questions\n- Changes Between SP 800-171 Rev. 2 and Rev. 3 (.xlsx)\n- The NIST Cybersecurity and Privacy Reference Tool (CPRT) provides online, interactive versions of the updated security requirements in SP 800-171, Revision 3 and the updated assessment procedures in SP 800-171A, Revision 3\n- Event Recording: ' CUI Security Requirements Workshop ,' which provides a general overview of SP 800 -171 and SP 800-171A\n- NIST Small Business Cybersecurity Corner\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n## What to Expect\n\nThe following pages delve deeper into the SP 800-171 R3 publication to provide more details for those responsible for implementing the requirements 3 . The following pages cover:\n\n\n\nPage 8: Key differences between SP 800-171 R2 and R3. Pages 9-10: General tips for getting started. Pages 11-28: Tips for getting started, broken out by Control Family. 3 We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Configuration Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 Security Assessment?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n|\n| ID.RA-10 | Critical suppliers are assessed prior to acquisition | Low | N1: See the notes for ID.RA. |\n| ID.IM (Improvement) | Improvements to organizational cybersecurity risk management processes, procedures, and activities are identified across all CSF Functions | Medium | N1: See the note for ID. |\n| ID.IM-01 | Improvements are identified from evaluations | Medium | R1: Periodically evaluate incident response program performance to identify problems and deficiencies that should be corrected. N1: Possible evaluation forms include self- assessments, third-party assessments, and independent audits. |\n| ID.IM-02 | Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties | High | N1: Incident response exercises and tests may provide helpful information for program evaluation and prepare staff and involved third parties (e.g., critical service providers and product suppliers) for future incident response activities. N2: See [SP800-84] for more information on simulations, tabletop discussions, and other forms of exercises. |\n| ID.IM-03 | Improvements are identified from the execution of operational processes, procedures, and activities | High | N1: The execution of operational processes, procedures, and activities includes all incident response and recovery efforts."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n3.2.6 FINALIZE ASSESSMENT PLAN AND OBTAIN APPROVAL TO EXECUTE PLAN\n\nAfter selecting the assessment procedures (including developing necessary procedures not\ncontained in the SP 800-53A catalog of procedures), tailoring the procedures for\nsystem/platform-specific and organization-specific conditions, optimizing the procedures for\nefficiency, and addressing the potential for unexpected events that may impact the assessment,\nthe assessment plan is finalized and the schedule is established, including key milestones for the\nassessment process."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.6", "cmmc_practice_id": "AT.L2-3.2.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 require for Identification and Authentication?"}, {"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": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Communications 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\nAddressed by 03.13.08.\n\nA.03.01.16.d[02]: wireless access to the system is protected using encryption."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 17)"}, {"role": "assistant", "content": "ES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................\n40\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 ....................................................................... 330\n4.12 PLANNING ............................................................................................................................. 361\n4.13 PROGRAM MANAGEMENT .................................................................................................... 372\n4.14 PERSONNEL SECURITY ..........................................................................................................."}], "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": 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 does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Getting Started with Awareness and Training\n\n## Family: Awareness and Training"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 15)"}, {"role": "assistant", "content": "r the assessment procedures\noutlined in the guidance. Tailoring involves customizing the assessment procedures to match\nthe characteristics of the system and its environment of operation more closely.\nThe tailoring\nprocess described in this guidance gives organizations the flexibility needed to avoid assessment\napproaches that are unnecessarily complex or costly while simultaneously meeting the\nassessment requirements and risk management principles established in the RMF. Tailoring\ndecisions are left to the discretion of the organization to maximize flexibility in developing\nassessment plans – applying the results of risk assessments to determine the extent, rigor, and\nlevel of intensity of the assessments needed to provide sufficient assurance about the security\nand privacy posture of the system. 1 [SP 800-37], Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach\nfor Security and Privacy, provides guidance on applying the RMF to systems and organizations. viii\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nNIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nTable of Contents\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ..............................................................."}], "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": 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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 20)"}, {"role": "assistant", "content": "anizational systems and may also have access to sensitive organizational data. Accordingly, the risk of malicious insiders or the service provider being compromised should be considered and addressed.\nNon-disclosure agreements (NDAs) and contracting clauses are options for deterring the unauthorized disclosure of sensitive data. ## 2.3. Incident Response Policies, Processes, and Procedures\n\nOrganizations should have policies that govern their cybersecurity incident response. While a policy is highly individualized to the organization, most incident response policies include the same key elements:\n\n- Statement of management commitment\n- Purpose and objectives of the policy\n- Scope of the policy (i.e., to whom and what it applies and under what circumstances)\n\n- Definition of events, cybersecurity incidents, investigations, and related terms\n- Roles, responsibilities, and authorities, such as which roles have the authority to confiscate, disconnect, or shut down technology assets\n- Guidelines for prioritizing incidents, estimating their severity, initiating recovery processes, maintaining or restoring operations, and other key actions\n- Performance measures\n\nProcesses and procedures should be based on the incident response policy and plan. Documented procedures should explain how technical processes and other operating procedures should be performed. Procedures can be tested or exercised periodically to verify their accuracy and can be used to help train new personnel. While it is impossible to have detailed procedures for every possible situation, organizations should consider documenting procedures for responding to the most common types of incidents and threats. Organizations should also develop and maintain procedures for particularly important processes that may be urgently needed during emergency situations, such as redeploying the organization's primary authentication platform."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_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 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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process.\nThe baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . A separate guideline, SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, provides specific guidelines that facilitate periodic assessment of security controls to ensure that controls have been implemented correctly, are operating as intended, and are meeting the organization's security requirements. ## 2 NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)\n\nNIST SP 800-39, Managing Information Security Risk , defines risk management as 'the program and supporting processes to manage information security risk to organizational operations (including mission, functions, and reputation), organizational assets, individuals, other organizations, and the Nation'. To integrate the risk management process throughout an organization and to address its mission and business concerns, a three-tiered approach is employed. The process is carried out across three tiers with the objective of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 4)"}, {"role": "assistant", "content": "h incorporating cybersecurity incident response recommendations and considerations throughout their cybersecurity risk management activities as described by the NIST Cybersecurity Framework (CSF) 2.0.\nDoing so can help organizations prepare for incident responses, reduce the number and impact of incidents that occur, and improve the efficiency and effectiveness of their incident detection, response, and recovery activities. Readers are encouraged to utilize online resources in conjunction with this document to access additional information on implementing these recommendations and considerations. ## Keywords\n\ncyber threat information sharing; Cybersecurity Framework; cybersecurity incident; cybersecurity risk management; incident handling; incident management; incident response. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Supplemental Content\n\nNIST has established an Incident Response project page that hosts links to resources with additional information on incident response activities."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["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 Access Control?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n- Applying a threat-centric approach to security requirements specification;\n- Employing system and security architectures that support logical and physical isolation using system and network segmentation techniques, virtual machines, and containers; 16\n- Implementing dual authorization controls for the most critical or sensitive operations;\n- Limiting persistent storage to isolated enclaves or domains;\n- Implementing a comply-to-connect approach for systems and networks;\n- Extending configuration management requirements by establishing authoritative sources for addressing changes to systems and system components;\n- Periodically refreshing or upgrading organizational systems and system components to a known state or developing new systems or components;\n- Employing a security operations center with advanced analytics to support continuous monitoring and protection of organizational systems; and\n- Using deception to confuse and mislead adversaries regarding the information they use for decision-making, the value and authenticity of the information they attempt to exfiltrate, or the environment in which they are operating.\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n## 3.1 ACCESS CONTROL"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nderal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?\n| The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. |\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 18)"}, {"role": "assistant", "content": "| MAINTENANCEFAMILY ..........................................................................................................\n| 32 |\n| 3.10 | MEDIAPROTECTIONFAMILY ................................................................................................. | 33 |\n| 3.11 | PHYSICALANDENVIRONMENTALPROTECTIONFAMILY .......................................................... | 34 |\n| 3.12 | PLANNINGFAMILY ............................................................................................................... | 36 |\n| 3.13 | PROGRAMMANAGEMENTFAMILY ......................................................................................."}], "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": 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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThis publication provides guidance to organizations on identifying, assessing, and mitigating cybersecurity risks throughout the supply chain at all levels of their organizations. The publication integrates cybersecurity supply chain risk management (C-SCRM) into risk management activities by applying a multilevel, C-SCRM-specific approach, including guidance on the development of C-SCRM strategy implementation plans, C-SCRM policies, C-SCRM plans, and risk assessments for products and services. acquire; C-SCRM; cybersecurity supply chain; cybersecurity supply chain risk management; information and communication technology; risk management; supplier; supply chain; supply chain risk assessment; supply chain assurance; supply chain risk; supply chain security. | 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls..............................................................................................."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_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 Security and Privacy Controls for Information Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "tions in the public and private sectors, both\nnationally and internationally, whose insightful and constructive comments improved the\noverall quality, thoroughness, and usefulness of this publication.\nHISTORICAL CONTRIBUTIONS TO NIST SPECIAL PUBLICATION 800-53\n\nThe authors wanted to acknowledge the many individuals who contributed to previous versions\nof Special Publication 800-53 since its inception in 2005. They include Marshall Abrams, Dennis\nBailey, Lee Badger, Curt Barker, Matthew Barrett, Nadya Bartol, Frank Belz, Paul Bicknell, Deb\nBodeau, Paul Brusil, Brett Burley, Bill Burr, Dawn Cappelli, Roger Caslow, Corinne Castanza, Mike\nCooper, Matt Coose, Dominic Cussatt, George Dinolt, Randy Easter, Kurt Eleam, Denise Farrar,\nDave Ferraiolo, Cita Furlani, Harriett Goldman, Peter Gouldmann, Tim Grance, Jennifer Guild,\nGary Guissanie, Sarbari Gupta, Priscilla Guthrie, Richard Hale, Peggy Himes, Bennett Hodge,\nWilliam Hunteman, Cynthia Irvine, Arnold Johnson, Roger Johnson, Donald Jones, Lisa Kaiser,\nStuart Katzke, Sharon Keller, Tom Kellermann, Cass Kelly, Eustace King, Daniel Klemm, Steve\nLaFountain, Annabelle Lee, Robert Lentz, Steven Lipner, William MacGregor, Thomas Macklin,\nThomas Madden, Robert Martin, Erika McCallister, Tim McChesney, Michael McEvilley, Rosalie\nMcQuaid, Peter Mell, John Mildner, Pam Miller, Sandra Miravalle, Joji Montelibano, Douglas\nMontgomery, George Moore, Rama Moorthy, Mark Morrison, Harvey Newstrom, Sherrill Nicely,\nRobert Niemeyer, LouAnna Notargiacomo, Pat O’Reilly, Tim Polk, Karen Quigg, Steve Quinn,\nMark Riddle, Ed Roback, Cheryl Roby, George Rogers, Scott Rose, Mike Rubin, Karen Scarfone,\nRoger Schell, Jackie Snouffer, Ray Snouffer, Murugiah Souppaya, Gary Stoneburner, Keith\nStouffer, Marianne Swanson, Pat Toth, Glenda Turner, Patrick Viscuso, Joe Weiss, Richard\nWilsher, Mark Wilson, John Woodward, and Carol Woody."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nDEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..................................................................................\n7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................"}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory\n(ITL) promotes the U.S. economy and public welfare by providing technical leadership for the\nNation’s measurement and standards infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT). ITL’s responsibilities include the development\nof management, administrative, technical, and physical standards and guidelines for the cost-\neffective security of other than national security-related information in federal information\nsystems. The Special Publication 800-series reports on ITL’s research, guidelines, and outreach\nefforts in information systems security and privacy and its collaborative activities with industry,\ngovernment, and academic organizations. As we push computers to “the edge,” building an increasingly complex world of interconnected\nsystems and devices, security and privacy continue to dominate the national dialogue. There is\nan urgent need to further strengthen the underlying systems, products, and services that we\ndepend on in every sector of the critical infrastructure to ensure that those systems, products,\nand services are sufficiently trustworthy and provide the necessary resilience to support the\neconomic and national security interests of the United States. NIST Special Publication 800-53,\nRevision 5, responds to this need by embarking on a proactive and systemic approach to develop\nand make available to a broad base of public and private sector organizations a comprehensive\nset of security and privacy safeguarding measures for all types of computing platforms, including\ngeneral purpose computing systems, cyber-physical systems, cloud systems, mobile systems,\nindustrial control systems, and Internet of Things (IoT) devices."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos...............................................24"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nThis publication is a supplement to NIST Special Publication 800-171 [SP 800-171]. It contains recommendations for enhanced security requirements to provide additional protection for Controlled Unclassified Information (CUI) in nonfederal systems and organizations when such information is associated with critical programs or high value assets. The enhanced security requirements are designed to respond to the advanced persistent threat (APT) and supplement the basic and derived security requirements in [SP 800-171]. While the security requirements in [SP 800-171] focus primarily on confidentiality protection, the enhanced security requirements in this publication address confidentiality, integrity, and availability protection. The enhanced security requirements are implemented in addition to the basic and derived requirements since those requirements are not designed to address the APT. The enhanced security requirements apply to those components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 2)"}, {"role": "assistant", "content": "y and Privacy\n\n## JOINT TASK FORCE\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-37r2\n\n## December 2018\n\n\n\nU.S. Department of Commerce Wilbur L.\nRoss, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-37, Revision 2 Natl. Inst. Stand. Technol. Spec. Publ. 800-37, Rev."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["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 is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.5.1. 3.5.1. 3.5.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory\n(ITL) promotes the U.S. economy and public welfare by providing technical leadership for the\nNation’s measurement and standards infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT). ITL’s responsibilities include the development\nof management, administrative, technical, and physical standards and guidelines for the cost-\neffective security of other than national security-related information in federal information\nsystems. The Special Publication 800-series reports on ITL’s research, guidelines, and outreach\nefforts in information systems security and privacy and its collaborative activities with industry,\ngovernment, and academic organizations. CHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n...................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6.\nAssessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| DATE | TYPE | REVISION | PAGE |\n|------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|\n| 12-10-2020 | Editorial | Section 1.4: Change 'NIST SP 800-53 [SP 800-53]' to '[SP 800-53]' | 3 |\n| 12-10-2020 | Editorial | Section 2.4 (Footnote 26): Change 'See [SP 800-37], Task P-4.' to 'See [SP 800-37], Task P-4, Organizationally-Tailored Control Baselines and Cybersecurity Framework Profiles (Optional), for additional guidance on tailoring control baselines for organization- wide use."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 13)"}, {"role": "assistant", "content": "| Advantages of Identity-Tier Policies.........................................................................19 | | | | Summary and Conclusions ............................................................................................20 | | | References ..............................................................................................................................23 | References ..............................................................................................................................23 | | | List of Figures | List of Figures | List of Figures | | Fig."}], "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": 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 Media Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n...........................................................64 | |\n| A.1.2.\nSelecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7. FAMILY: CONFIGURATION MANAGEMENT................................................................................87 | |\n| A.2.8. FAMILY: CONTINGENCY PLANNING ...........................................................................................98 | |\n| A.2.9."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| 3.11.6e | ENHANCED SECURITY REQUIREMENT Assess, respond to, and monitor supply chain risks associated with organizational systems and system components. | ENHANCED SECURITY REQUIREMENT Assess, respond to, and monitor supply chain risks associated with organizational systems and system components."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"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": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n3.2.5 OPTIMIZE SELECTED ASSESSMENT PROCEDURES TO ENSURE MAXIMUM EFFICIENCY\n\nAssessors have flexibility in organizing assessment plans that meet the needs of the organization\nand that provide the best opportunity for obtaining the necessary evidence to determine\nsecurity or privacy control effectiveness while reducing overall assessment costs. 3.2.5."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Zero Trust Architecture provide? (Part 16)"}, {"role": "assistant", "content": "Una única organización puede gestionar varias redes internas, oficinas remotas con su propia infraestructura local, personas a distancia o móviles y servicios en la nube. Esta complejidad ha superado los métodos tradicionales de seguridad de red perimetral, puesto que no existe un perímetro único y fácilmente identificable para la compañía. También, esta seguridad ha demostrado su insuficiencia, ya que una vez que los atacantes han traspasado la barrera, el movimiento lateral no tiene obstáculos. Esta difícil tarea ha impulsado el desarrollo de un nuevo modelo de ciberseguridad conocido como «confianza cero» (ZT, por su denominación en inglés zero trust ). El enfoque ZT se centra, fundamentalmente, en la protección de los datos y los servicios, pero puede y debe ampliarse para incluir todos los activos de la empresa (dispositivos, aplicaciones, componentes de infraestructura, virtuales y de la nube) y los sujetos (usuarios finales, aplicaciones y otras entidades no humanas que solicitan información de los recursos). A lo largo de este documento, se utilizará la palabra sujeto a menos que la sección se refiera directamente a un usuario final humano, en cuyo caso, se utilizará específicamente usuario en lugar del término más genérico sujeto . Los modelos de seguridad de confianza cero parten de la base de que el atacante está presente en el entorno y que el ambiente de la compañía no es diferente (o no es más confiable) a cualquier otro que no sea de la organización. En este nuevo paradigma, se debe asumir que no hay seguridad implícita. Se deben analizar y evaluar continuamente los riesgos para los activos y actividades corporativas y luego promulgar protecciones para mitigarlos. En la confianza cero, estas protecciones implican, por lo general, restringir el acceso a los recursos (como los datos, los medios informáticos y las aplicaciones o servicios) solo a aquellos sujetos y activos identificados como necesarios para el acceso."}], "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": 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 9)"}, {"role": "assistant", "content": "ework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53].\nThe security control mappings can be useful to organizations that wish to demonstrate compliance to the security requirements in the context of their established information security programs when such programs have been built using the NIST security controls. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:"}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication contains comprehensive updates to the Risk Management Framework . The updates include an alignment with the constructs in the NIST Cybersecurity Framework; the integration of privacy risk management processes; an alignment with system life cycle security engineering processes; and the incorporation of supply chain risk management processes. Organizations can use the frameworks and processes in a complementary manner within the RMF to effectively manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. Revision 2 includes a set of organization-wide RMF tasks that are designed to prepare information system owners to conduct system-level risk management activities. The intent is to increase the effectiveness, efficiency, and cost-effectiveness of the RMF by establishing a closer connection to the organization's missions and business functions and improving the communications among senior leaders, managers, and operational personnel. * Note: The publication pertains to information systems, which are discrete sets of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information, whether such information is in digital or non-digital form. Information resources include information and related resources, such as personnel, equipment, funds, and information technology. Therefore, information systems may or may not include hardware, firmware, and software. This publication is intended to help organizations manage security and privacy risk, and to satisfy the requirements in the Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nDEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..................................................................................\n7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................"}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n|\n| Appendix A. C-SCRM Security Controls...............................................................................................\n| 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n17 The Audit and Accountability, Maintenance, Media Protection, and Physical Protection families do not contain enhanced security requirements at this time.\n\n## 3.8 MEDIA PROTECTION"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 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 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 does CMMC Level 3 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nderal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'?\n| The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements. |\n| What is the relationship between NIST and CMMC? | The Cybersecurity Maturity Model Certification (CMMC) is a DOD program that references the security requirements in NIST SP 800-171 and SP 800-172. NIST is not involved in the design, development, or implementation of the CMMCmodel, accreditation body, or certification process. It is important to note that CMMCis currently based on SP 800-171, Revision 2. Contractors should check for specific requirements in their contracts to understand which version they are required to use. |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "tise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D.\nThe controls described assist organizations in defining the controls needed to satisfy minimum assurance requirements. Where additional assurance is desired to achieve risk management objectives, Table E-4 provides additional security controls and control enhancements to achieve enhanced assurance. Implementers should note that designation of assurance-related controls is not intended to imply a greater level of importance for such controls. Achieving adequate security for organizational information systems requires the correct combination of both functionality- and assurance-related security controls. ## 6 Security Controls\n\nAppendix F, the Security Control Catalog, provides a comprehensive range of countermeasures for organizations and information systems. The security controls are designed to be technologyneutral such that the focus is on the fundamental countermeasures needed to protect organizational information during processing, storage, or transmission. SP 800-53 Rev. 4, therefore, does not provide guidance on the application of security controls to specific technologies, environments of operation, or missions/business functions. These specific areas may be addressed using overlays (see below). Control enhancements are included with many security controls and are selected in order to increase the strength of the base control. Control enhancements are intended to be implemented only in conjunction with implementation of the base control. Some security controls and control enhancements include one or more assignment and selection statements. These are variable parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 2 require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nassessment; assessment method; assessment object; assessment procedure; assurance; Controlled Unclassified Information; coverage; FISMA; NIST Special Publication 800-171; NIST Special Publication 800-53A; nonfederal organization; nonfederal system; security assessment; security requirement.\n\n- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Acquisition or procurement responsibilities (e.g., contracting officers)\n- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts)\n\n- Federal perspective : The entity establishing and conveying security assessment requirements in contractual vehicles or other types of agreements\n- Nonfederal perspective : The entity responding to and complying with the security assessment requirements set forth in contracts or agreements"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\ncks. This guide addresses only adverse cybersecurity events . Additional analysis is often needed to determine whether adverse cybersecurity events indicate that a cybersecurity incident has occurred.\n- Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state"}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n.......24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3.\nLevel 2 -Mission and Business Process....................................................................................30 |\n| 2.3.4. Level 3 -Operational................................................................................................................32 |\n| 2.3.5. C-SCRM PMO..............................................................................................................................33 |\n| Critical Success Factors...................................................................................................................37 |\n| 3. |\n| 3.1.2. The Role of C-SCRM in the Acquisition Process .........................................................................40 |\n| 3.4.1. Foundational Practices ...............................................................................................................46 |"}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 12)"}, {"role": "assistant", "content": "| ..............................................................................................................\n17 |\n| 3.7 MAINTENANCE | ...................................................................................................................... 18 |\n| 3.8 MEDIAPROTECTION | .............................................................................................................. 18 |\n| 3.9 PERSONNEL SECURITY | ............................................................................................................ 18 |\n| 3.10 PHYSICAL PROTECTION ........................................................................................................ | 19 |\n| 3.11 RISKASSESSMENT | ................................................................................................................ 19 |\n| 3.12 SECURITY ASSESSMENT | ........................................................................................................"}], "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": 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 Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nAs we push computers to 'the edge,' building a complex world of interconnected information systems and devices, security and privacy risks (including supply chain risks) continue to be a large part of the national conversation and topics of great importance. The significant increase in the complexity of the hardware, software, firmware, and systems within the public and private sectors (including the U.S. critical infrastructure) represents a significant increase in attack surface that can be exploited by adversaries. Moreover, adversaries are using the supply chain as an attack vector and effective means of penetrating our systems, compromising the integrity of system elements, and gaining access to critical assets."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "ns. This publication can be used in conjunction with its companion publication, NIST Special Publication 800-171A, which provides a comprehensive set of procedures to assess the security requirements.\n## Keywords\n\nControlled Unclassified Information; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; nonfederal organizations; nonfederal systems; organization-defined parameter; security assessment; security control; security requirement. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "ociated with products and services that may potentially contain malicious functionality, are counterfeit, or are vulnerable due to poor manufacturing and development practices within the supply chain.\nThese risks are associated with an enterprise's decreased visibility into and understanding of how the technology they acquire is developed, integrated, and deployed or the processes, procedures, standards, and practices used to ensure the security, resilience, reliability, safety, integrity, and quality of the products and services. This publication provides guidance to organizations on identifying, assessing, and mitigating cybersecurity risks throughout the supply chain at all levels of their organizations. The publication integrates cybersecurity supply chain risk management (C-SCRM) into risk management activities by applying a multilevel, C-SCRM-specific approach, including guidance on the development of C-SCRM strategy implementation plans, C-SCRM policies, C-SCRM plans, and risk assessments for products and services. ## Keywords\n\nacquire; C-SCRM; cybersecurity supply chain; cybersecurity supply chain risk management; information and communication technology; risk management; supplier; supply chain; supply chain risk assessment; supply chain assurance; supply chain risk; supply chain security. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 16)"}, {"role": "assistant", "content": "h that provides an integrated set of all application services (e.g., services discovery, networking connections, communication resilience, and security services like authentication and authorization).\nThe realization of a zero trust architecture for the above class of cloud-native applications requires a robust policy framework. In order to follow zero trust principles, the constituent polices in the framework should consider the following scenario:\n\n- There should not be implicit trust in users, services, or devices based exclusively on their network location, affiliation, or ownership. Hence, policy definitions and associated security controls based on the segmentation or isolation of networks using network parameters (e.g., IP addresses, subnets, perimeter) are insufficient. These policies fall under the classification of network-tier policies. - To ensure the presence of zero trust principles throughout the entire application, networktier policies must be augmented with policies that establish trust in the identity of the various participating entities (e.g., users and services) irrespective of the location of the services or applications, whether on-premises or on multiple clouds. This document provides guidance for realizing a zero trust architecture that can enforce granular application-level policies for cloud-native applications. The guidance is anchored in the following:\n\n- A combination of network-tier and identity-tier policies\n- The components of cloud-native applications that enable the definition and deployment of those policies, such as edge, ingress, sidecar, and egress gateways; the creation, issuance, and maintenance of service identities; and the issuance of authentication and authorization tokens that carry user identities in the enterprise application infrastructure that encompasses multi-cloud and hybrid environments\n\n## Introduction\n\nZero trust (ZT) tenets or principles have been accepted as the guide markers for architecting all applications."}], "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": 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 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 Control Baselines for Information Systems and Organizations provide? (Part 5)"}, {"role": "assistant", "content": "ce\n\nMatthew A. Kozma Chief Information Officer\n\nDana Deasy\n\nChief Information Officer\n\nJohn Sherman\n\nMichael E. Waschull Deputy Chief Information Officer\n\nPrincipal Deputy CIO\n\nMark Hakun\n\nClifford M.\nConner\n\nDeputy CIO for Cybersecurity and DoD SISO\n\nCybersecurity Group and IC CISO\n\nKevin Dulany\n\nVacant\n\nDirector, 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."}], "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": 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 Media Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nging the risks to individuals associated with the creation, collection, use, processing, dissemination, storage, maintenance, disclosure, or disposal (collectively referred to as 'processing') of PII.\n30 When preparing to execute the steps of the RMF, organizations consider how to best promote and institutionalize collaboration between the two programs to ensure that the objectives of both disciplines are met at every step of the process."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Access Control?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n## 3.1. Preparation and Lessons Learned\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------|\n| PR.AA (Identity Management, Authentication, and Access Control) | Access to physical and logical assets is limited to authorized users, services, and hardware and managed commensurate with the assessed risk of unauthorized access | Medium | N1: See the notes for PR. |\n| PR.AA-01 | Identities and credentials for authorized users, services, and hardware are managed by the organization | Medium | N1: See the notes for PR. |\n| PR.AA-02 | Identities are proofed and bound to credentials based on the context of interactions | Medium | N1: See the notes for PR. |\n| PR.AA-03 | Users, services, and hardware are authenticated | Medium | N1: See the notes for PR."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 6)"}, {"role": "assistant", "content": "publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication.\n## Table of Contents\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Incident Response as Part of Cybersecurity Risk Management.........................................................4 |\n| 3. CSF 2.0 Community Profile for Cyber Incident Risk Management...................................................10 |\n| References.......................................................................................................................................36 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................38 |\n| Appendix B. Glossary .......................................................................................................................39 |\n| Appendix C. Change Log...................................................................................................................40 |\n| List of Tables |\n| Table 1. Previous incident response life cycle model's phases and corresponding CSF 2.0 Functions.....6 |\n| Table 2."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["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 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 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 additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 17)"}, {"role": "assistant", "content": "N .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES .............................................................................\n11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................. 18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .........................................................................................................."}], "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": 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 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 in Nonfederal Systems and Organizations provide? (Part 13)"}, {"role": "assistant", "content": "olicy requires to have safeguarding or disseminating controls, excluding information that is classified under EO 13526 [2], any predecessor or successor order, or the Atomic Energy Act [3] as amended.\n2 Procedures for the use of CUI include marking, safeguarding, transporting, disseminating, reusing, and disposing of the information. 3 A federal information system is a system that is used or operated by an executive agency, by a contractor of an executive agency, or by another organization on behalf of an executive agency. The term system is used in this publication to represent people, processes, and technologies involved in the processing, storage, or transmission of CUI. Systems can include operational technology (OT), information technology (IT), Internet of Things (IoT) devices, Industrial IoT (IIoT) devices, specialized systems, cyber-physical systems, embedded systems, and sensors. 4 A nonfederal organization is any entity that owns, operates, or maintains a nonfederal system. 5 A nonfederal system is any system that does not meet the criteria for a federal information system. 6 The term security requirement refers to the protection needs for a system or organization. Security requirements may be derived from laws, Executive Orders, directives, regulations, policies, standards, mission and business needs, or risk assessments. 7 In accordance with EO 13526 [2] and 32 CFR 2002 [5], the scope of CUI protection is primarily focused on confidentiality . However, the security objectives of confidentiality and integrity are closely related since many of the underlying security mechanisms support both objectives. Therefore, the security requirements in this publication address the protection of CUI from unauthorized disclosure and modification. registry [4]. The requirements do not apply to nonfederal organizations that are collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency."}], "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": 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 Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nDesde hace más de una década se insta a los organismos federales a cambiar hacia una protección basada en estos nuevos principios, mediante la creación de prestaciones y políticas como la Ley Federal de Gestión de Seguridad de la Información (FISMA por su nombre en inglés Federal Information Security Modernization Act); seguida del Marco de Gestión de Riesgos (RMF por su apelación en inglés Risk Management Framework); la Gestión Federal de Identidades, Credenciales y Accesos (FICAM, por su nombre en inglés Federal Identity,\n\nCredential, and Access Management); la Conexión a Internet de confianza TIC (por su nombre en inglés Trusted Internet Connections), y los programas de Diagnóstico y Mitigación Continuos (CDM por su denominación en inglés Continuous Diagnostics and Mitigation). Todos estos planes tienen como objetivo restringir el acceso a los datos y a los recursos a las partes autorizadas. Cuando se iniciaron estos programas, estaban limitados por las capacidades técnicas de los sistemas de información. Las políticas de seguridad eran mayormente estáticas y se aplicaban en grandes «cuellos de botella» al alcance de la empresa para obtener el mejor resultado posible. A medida que la tecnología se consolida, se están pudiendo analizar y evaluar continuamente las solicitudes de acceso de forma dinámica y granular, sobre una base de «necesidad de acceso» que permite mitigar la exposición de los datos ocasionada por cuentas comprometidas, atacantes que monitorean las redes y otras amenazas. 6. Toda autentificación y autorización a un recurso es dinámica y se aplica de forma estricta antes de permitir el acceso . Se trata de un ciclo constante de acceso, escaneo y evaluación de amenazas, adaptación y reevaluación continua de la confianza en permanente comunicación."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n- Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state\n\nProcesses and procedures should be based on the incident response policy and plan. Documented procedures should explain how technical processes and other operating procedures should be performed. Procedures can be tested or exercised periodically to verify their accuracy and can be used to help train new personnel. While it is impossible to have detailed procedures for every possible situation, organizations should consider documenting procedures for responding to the most common types of incidents and threats. Organizations should also develop and maintain procedures for particularly important processes that may be urgently needed during emergency situations, such as redeploying the organization's primary authentication platform."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": ". 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nThe authors wanted to acknowledge the many individuals who contributed to previous versions of Special\nPublication 800-53A since its inception in 2005.\nThey include Marshall Abrams, Dennis Bailey, Matt\nBarrett, Nadya Bartol, Frank Belz, Paul Bicknell, Deb Bodeau, Brett Burley, Bill Burr, Dawn Cappelli,\nCorinne Castanza, Matt Coose, George Dinolt, Donna Dodson, Randy Easter, Kurt Eleam, Jennifer Fabius,\nDaniel Faigin, Denise Farrar, Harriett Goldman, Peter Gouldmann, Richard Graubart, Jennifer Guild,\nSarbari Gupta, Peggy Himes, Bennett Hodge, Cynthia Irvina, Arnold Johnson, Roger Johnson, Lisa Kaiser,\nStu Katzke, Sharon Keller, Cass Kelly, Steve LaFountain, Steve Lipner, Bill MacGregor, Tom Macklin, Tom\nMadden, Erika McCallister, Tim McChesney, Michael McEvilley, John Mildner, Sandra Miravalle, Joji\nMontelibano, Doug Montgomery, George Moore, Harvey Newstrom, Robert Niemeyer, LouAnna\nNotargiacomo, Dorian Pappas, Tim Polk, Esten Porter, Karen Quigg, Steve Quinn, Ed Roback, George\nRogers, Scott Rose, Mike Rubin, Karen Scarfone, Roger Schell, Matt Scholl, Murugiah Souppaya, Kevin\nStine, Gary Stoneburner, Keith Stouffer, Marianne Swanson, Pat Toth, Glenda Turner, Joe Weiss, Richard\nWilsher, Mark Wilson, John Woodward, and Carol Woody. iv\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nNIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nDocument Conventions\n\nFor the purposes of this document, the term “security and privacy” is universally used since the\nguidance is applicable to both security and privacy control assessments. For certain systems,\nhowever, the guidance may only be relevant for security or privacy."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 require for Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\ncks. This guide addresses only adverse cybersecurity events . Additional analysis is often needed to determine whether adverse cybersecurity events indicate that a cybersecurity incident has occurred.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes R2: Tune the continuous monitoring |\n|---------------|------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| DE.CM-01 | Networks and network services are monitored to find potentially adverse events | High | false negatives to acceptable levels."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Assessing Enhanced Security Requirements for Controlled Unclassified Information support CMMC certification?"}, {"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 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 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 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 additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 17)"}, {"role": "assistant", "content": "rity risks to the organization, and compliance with the security requirements. The assessment procedures in this publication are based on and sourced to the assessment procedures in SP 800-53A [5].\nFor additional information and guidance on preparing for security assessments, developing assessment plans, conducting assessments, and analyzing assessment report results, consult SP 800-53A [5]. ## 3. The Procedures\n\nThis section provides assessment procedures for the security requirements defined in NIST SP 800-171 [3]. Organizations that conduct security requirement assessments can develop their security assessment plans by using the information provided in the assessment procedures and selecting the specific assessment methods and objects that meet the organization's needs. Organizations also have flexibility in defining the level of rigor and detail associated with the assessment based on the assurance requirements of the organization. ## 3.1. Access Control\n\n## 03.01.01 Account Management\n\n## ASSESSMENT OBJECTIVE\n\nDetermine if:\n\nA.03.01.01.ODP[01]: the time period for account inactivity before disabling is defined . A.03.01.01.ODP[02]: the time period within which to notify account managers and designated personnel or roles when accounts are no longer required is defined . A.03.01.01.ODP[03]: the time period within which to notify account managers and designated personnel or roles when users are terminated or transferred is defined . A.03.01.01.ODP[04]: the time period within which to notify account managers and designated personnel or roles when system usage or the need-to-know changes for an individual is defined . A.03.01.01.ODP[05]: the time period of expected inactivity requiring users to log out of the system is defined . A.03.01.01.ODP[06]: circumstances requiring users to log out of the system are defined . A.03.01.01.a[01]:\n\nA.03.01.01.a[02]:\n\nsystem account types allowed are defined. system account types prohibited are defined."}], "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": 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 does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| ...................................................................................................\n3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | ## 1 Introduction In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Maintenance?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nINCLUDES UPDATES AS OF 1 1 -01 -2024; SEE APPENDIX K\n\nBoyens J, Smith A, Bartol N, Winkler K, Holbrook A, Fallon M (2022) Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-161r1-upd1, Includes updates as of Novem ber 1, 2024. https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/161/r1/upd1/final, including related content, potential updates, and document history."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 9)"}, {"role": "assistant", "content": "ework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53].\nThe security control mappings can be useful to organizations that wish to demonstrate compliance to the security requirements in the context of their established information security programs when such programs have been built using the NIST security controls. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Control Baselines for Information Systems and Organizations provide? (Part 14)"}, {"role": "assistant", "content": "| PUBLICATIONORGANIZATION ..................................................................................................\n| 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 | CONTROLBASELINES ............................................................................................................... | 5 |\n| 2.2 | SELECTING CONTROLBASELINES ............................................................................................... | 6 |\n| 2.3 | CONTROLBASELINE ASSUMPTIONS ..........................................................................................."}], "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": 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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process.\nThe baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . A separate guideline, SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, provides specific guidelines that facilitate periodic assessment of security controls to ensure that controls have been implemented correctly, are operating as intended, and are meeting the organization's security requirements. ## 2 NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)\n\nNIST SP 800-39, Managing Information Security Risk , defines risk management as 'the program and supporting processes to manage information security risk to organizational operations (including mission, functions, and reputation), organizational assets, individuals, other organizations, and the Nation'. To integrate the risk management process throughout an organization and to address its mission and business concerns, a three-tiered approach is employed. The process is carried out across three tiers with the objective of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide?"}, {"role": "assistant", "content": "\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 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 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 additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 12)"}, {"role": "assistant", "content": "| SYSTEMANDINFORMATIONINTEGRITY.........................................................................................\n| 26 |\n| REFERENCES .................................................................................................................................. | REFERENCES .................................................................................................................................. | 32 |\n| APPENDIXA GLOSSARY................................................................................................................ | APPENDIXA GLOSSARY................................................................................................................ | 36 |\n| APPENDIX B ACRONYMS.............................................................................................................. | APPENDIX B ACRONYMS.............................................................................................................. | 44 |\n| APPENDIX C ASSESSMENT METHODS.......................................................................................... | APPENDIX C ASSESSMENT METHODS.......................................................................................... | 45 |\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Errata\n\nThis table contains changes that have been incorporated into Special Publication 800-172A. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. Any potential updates for this 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)."}], "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": 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 Security and Privacy Controls for Information Systems and Organizations:\n\nAssurance; availability; computer security; confidentiality; control; cybersecurity; FISMA;\ninformation security; information system; integrity; personally identifiable information; Privacy\nAct; privacy controls; privacy functions; privacy requirements; Risk Management Framework;\nsecurity controls; security functions; security requirements; system; system security. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ........................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Media Protection\n\nDescription: Protect system media, both paper and digital; limiting access to data on system media to authorized users; and sanitizing or destroying system media before disposal or release for reuse."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security Requirements for Controlled Unclassified Information provide? (Part 14)"}, {"role": "assistant", "content": "cedures: AC-06(02), AC-06(05)\n\nDetermination statements have alphanumeric identifiers. Each determination statement begins with the letter ' A ' to indicate that it is part of an assessment procedure.\nThe next sequence of numbers or letters (e.g., 03.01.01.e or 03.01.01.f.02) indicates the security requirement identifier from NIST SP 800-171 (and the specific control item if it is a multi-part requirement) that is the target of the assessment. Organization-defined parameters are indicated by the letters ' ODP .' If there are multiple ODPs in the determination statement, the ODP number is indicated in a square bracket (e.g., A.03.01.08.ODP[01]). Square brackets are also used to denote when an assessment procedure further decomposes a requirement into more granular determination statements (e.g., A.03.01.12.a[01], A.03.01.12.a[02], A.03.01.12.a[03]). The application of an assessment procedure to a security requirement produces assessment results or findings . The findings are compiled and used as evidence to determine whether the security requirement has been satisfied or other than satisfied . A finding of satisfied indicates that the assessment objective has been met, producing a fully acceptable result. A finding of other than satisfied indicates that there are potential anomalies that may need to be addressed by the organization. A finding of other than satisfied may also indicate that the assessor was unable to obtain sufficient information to make the determination called for in the determination statement. - 2.2. Assurance Cases\n\nBuilding an effective assurance case to determine compliance with security requirements involves compiling evidence from a variety of sources and conducting different types of activities during an assessment. An assurance case is a body of evidence organized into an argument demonstrating that some claim about a system is true."}], "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": 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 Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "..........................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5.\nAudit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Physical Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n................................................................................57 | |\n| Appendix A.\nC-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 8)"}, {"role": "assistant", "content": "e requirements also apply to services, including externally provided services, that process, store, or transmit CUI, or that provide security protections, for the system requiring enhanced protection.\nThe protection of a specific service to include CUI that is processed, stored or transmitted during the provision of that service, is achieved by implementing the enhanced security requirements for the service, or the system or system components responsible for providing that service. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. The term organizational system is used in many of the enhanced security requirements. It has a specific meaning regarding the applicability of the enhanced requirements as described above. Appropriate scoping considerations for the requirements are important factors in determining protection-related investment decisions and managing security risk for nonfederal organizations that have the responsibility of protecting CUI associated with critical programs and high value assets. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## FRAMEWORK FOR IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY\n\nOrganizations that have implemented or plan to implement the NIST Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 2 require for Access Control?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## 03.01.06 Least Privilege - Privileged Accounts\n\n[SELECT FROM: access control policy and procedures; procedures for least privilege; list of system-generated privileged accounts; list of system administration personnel; system audit records; system configuration settings; system security plan; list of system-generated security functions or security-relevant information assigned to system accounts or roles; other relevant documents or records]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n## A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Location Environments\n\n## A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Location Environments\n\nChandramouli R, Butcher Z (2023) A Zero-Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Location Environments. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-207A. https://doi.org/10.6028/NIST.SP.800-207A"}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 14)"}, {"role": "assistant", "content": "..................................................... 50 | APPENDIX C MAPPINGTABLES ....................................................................................................\n50 |\n| APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 | APPENDIXD ADVERSARY EFFECTS............................................................................................... 68 |\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Errata\n\nThis table contains changes that have been incorporated into Special Publication 800-172. Errata updates can include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature. Any potential updates for this 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 the SP 800-172 publication details. | DATE | TYPE | CHANGE | PAGE |\n|--------|--------|----------|--------|\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## CHAPTER ONE\n\n## INTRODUCTION\n\nTHE NEED TO PROTECT CONTROLLED UNCLASSIFIED INFORMATION\n\noday, 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."}], "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": 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 9)"}, {"role": "assistant", "content": "ework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53].\nThe security control mappings can be useful to organizations that wish to demonstrate compliance to the security requirements in the context of their established information security programs when such programs have been built using the NIST security controls. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 require for Access Control?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nare are authenticated | Medium | N1: See the notes for PR.\n|\n| PR.AA-04 | Identity assertions are protected, conveyed, and verified | Medium | N1: See the notes for PR. |\n| PR.AA-05 | Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties | Medium | N1: See the notes for PR. |\n| PR.AA-06 | Physical access to assets is managed, monitored, and enforced commensurate with risk | Medium | N1: See the notes for PR. |\n| PR.AT (Awareness and Training) | The organization's personnel are provided with cybersecurity awareness and training so that they can perform their cybersecurity-related tasks | Medium | N1: See the notes for PR. |\n| PR.AT-01 | Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind | Medium | N1: See the notes for PR."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | ## 1 Introduction In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 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 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- A business champion: Someone who is responsible for developing and maintaining the incident response plan.\n- Who to call: List all the individuals who may be part of the incident response efforts. Include their contact information, roles, and responsibilities.\n- What/when/how to report: List the business' communications/reporting responsibilities as required by laws, regulations, contracts, agreements, or policies.\n- Also, most federal contracts will include specific reporting and notification requirements that should be included in the Incident Response Plan\n\nDescription: Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of the systems; and employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 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 does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8.\nContingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 7)"}, {"role": "assistant", "content": "| 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_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 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n- Govern, Identify, and Protect help organizations prevent some incidents, prepare to handle incidents that do occur, reduce the impact of those incidents, and improve incident response and cybersecurity risk management practices based on lessons learned from those incidents. - Detect, Respond, and Recover help organizations discover, manage, prioritize, contain, eradicate, and recover from cybersecurity incidents, as well as perform incident reporting, notification, and other incident-related communications. - Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state\n\nAll six Functions have vital roles in incident response. Govern, Identify, and Protect help organizations prevent some incidents, prepare to handle incidents that do occur, reduce the impact of those incidents, and improve incident response and cybersecurity risk management practices based on lessons learned."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 2 require for Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nance. The decision to select a particular set of enhanced security requirements will be based on the mission and business needs of federal agencies and guided and informed by ongoing risk assessments.\nThe enhanced security requirements for nonfederal systems processing, storing, or transmitting CUI associated with critical programs or high value assets will be conveyed to nonfederal organizations by federal agencies in a contract, grant, or other agreement. The application of the enhanced security requirements to subcontractors will also be addressed by federal agencies in consultation with nonfederal organizations."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. All information systems process, store, or transmit some type of information. For example, information about the temperature in a remote facility collected and transmitted by a sensor to a monitoring station, location coordinates transmitted by radio to a controller on a weapons system, photographic images transmitted by a remote camera (land/satellite-based) to a server, or health IT devices transmitting patient information via a hospital network, require protection. This information can be protected by: categorizing the information to determine the impact of loss; assessing whether the processing of the information could impact individuals' privacy; and selecting and implementing controls that are applicable to the IT resources in use. Therefore, cloud-based systems, industrial/process control systems, weapons systems, cyber-physical systems, applications, IoT devices, or mobile devices/systems, do not require a separate risk management process but rather a tailored set of controls and specific implementation details determined by applying the existing RMF process."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and 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 10)"}, {"role": "assistant", "content": "parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.\nParameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nstomize assessments based on organizational policies and requirements, known threat and vulnerability information, system and platform dependencies, operational considerations, and tolerance for risk.\n1\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 10)"}, {"role": "assistant", "content": "| Shortcomings of Identity-Based Segmentation Policies for Enterprise ZTA ................\n| 9 |\n| | Multi-Tier Policies for Enterprise ZTA ........................................................................."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["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 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 additional guidance does Security and Privacy Controls for Information Systems and Organizations provide? (Part 15)"}, {"role": "assistant", "content": "_________\n\nUSE OF EXAMPLES IN THIS PUBLICATION\n\nThroughout this publication, examples are used to illustrate, clarify, or explain certain items in\nchapter sections, controls, and control enhancements.\nThese examples are illustrative in nature\nand are not intended to limit or constrain the application of controls or control enhancements\nby organizations. 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. xi\n\n\fNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nFEDERAL RECORDS MANAGEMENT COLLABORATION\n\nFederal records management processes have a nexus with certain information security and\nprivacy requirements and controls. For example, records officers may be managing records\nretention, including when records will be deleted. Collaborating with records officers on the\nselection and implementation of security and privacy controls related to records management\ncan support consistency and efficiency and ultimately strengthen the organization’s security and\nprivacy posture. 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\n. I\n\nxii\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 19)"}, {"role": "assistant", "content": "..................................................................................... 718\nAPPENDIX F ONGOING ASSESSMENT AND AUTOMATION .................................................................\n721\n\nix\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\n. I\n\nNIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nCHAPTER ONE\n\nINTRODUCTION\nTHE NEED TO ASSESS SECURITY AND PRIVACY CONTROL EFFECTIVENESS\n\nToday’s systems2 are complex assemblages of technology (i.e., hardware, software, and\nfirmware), processes, and people working together to provide organizations with the\ncapabilities to process, store, and transmit information in a timely manner in support of various\nmission and business functions. The degree to which organizations have come to depend upon\nsystems to conduct routine, important, and critical mission and business functions means that\nthe protection of the underlying systems and environments of operation is paramount to the\nsuccess of the organization. The selection of appropriate security and privacy controls for a\nsystem is an important task that can have significant implications on the operations and assets\nof an organization as well as the welfare of individuals. Security controls are the safeguards 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."}], "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": 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 Control Baselines for Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "rce 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.\nThis publication may be used by nongovernmental organizations on a voluntary basis, and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-53B Natl. Inst. Stand. Technol. Spec. Publ. 800-53B, 85 pages (October 2020)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the designated public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "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": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\net of cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users and resources. It is a set of security primitives rather than a particular set of technologies.\nZero trust assumes that there is no implicit trust granted to user accounts based solely on their physical or network location (i.e., local area networks versus the internet) or to endpoints (devices) based on their ownership (e.g., enterprise or personally owned). Zero trust focuses on protecting resources (e.g., devices, services, workflows, network accounts) rather than network segments, as the network location is no longer seen as the prime component to the security posture of the resource. - A zero trust architecture uses zero trust principles to plan industrial and enterprise infrastructures and workflows."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "...............................................................79 | |\n| A.2.6.\nFAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7. FAMILY: CONFIGURATION MANAGEMENT................................................................................87 | |\n| A.2.8. FAMILY: CONTINGENCY PLANNING ...........................................................................................98 | |\n| A.2.9. FAMILY: IDENTIFICATION AND AUTHENTICATION...................................................................102 | |\n| A.2.10. FAMILY: INCIDENT RESPONSE................................................................................................105 | |\n| A.2.11. FAMILY: MAINTENANCE.........................................................................................................110 | |\n| A.2.12. FAMILY: MEDIA PROTECTION ................................................................................................115 | |\n| A.2.13."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 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 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 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 does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1. C-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | 1 INTRODUCCIÓN..................................................................................................................................................10 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | HISTORIA DE LOS PROGRAMAS DE CONFIANZA CERO RELACIONADOS CON LAS AGENCIAS FEDERALES .................................11 | | | 1.2 | E STRUCTURA DEL DOCUMENTO .........................................................................................................................12 | | | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | CONCEPTOS BÁSICOS DE LA CONFIANZA CERO.................................................................................................13 | | | 2.1 | PRINCIPIOS DE LA CONFIANZA CERO ....................................................................................................................15 | | | 2.2 | VISIÓN DE CONFIANZA CERO DE UNA RED .............................................................................................................17 | | | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | COMPONENTES LÓGICOS DE LA ARQUITECTURA DE CONFIANZA CERO..........................................................19 | | | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | 3.1 VARIACIONES DE LOS ENFOQUES DE LA ARQUITECTURA DE CONFIANZA CERO ...............................................................21 | | | 3.1.1 | ZTA basada en una gobernanza de la identidad mejorada...................................................................22 | | | 3.1.2 | ZTA y el uso de la microsegmentación..................................................................................................23 | | | 3.1.3 | ZTA y el uso de una infraestructura de red y perímetros definidos a través de software....................23 | | | 3.2 | VARIANTES IMPLEMENTADAS DE LA ARQUITECTURA ABSTRACTA ...............................................................................24 | | | 3.2.1 | Despliegue basado en agentes y puertas de enlace de los dispositivos...............................................24"}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 18)"}, {"role": "assistant", "content": "rses, 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.\n## Related Resources:\n\n- View all SP 800-171 Awareness and Training Requirements and Assessment Procedures\n- NIST Free and Low-Cost Online Cybersecurity Learning Content\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n- NARA CUI training\n- Center for Development of Security Excellence Security Awareness Hub\n\n81&/$66,),('GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1)250$7,21GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1\n\n\n\n## Getting Started with Audit and Accountability\n\n## Family: Audit and Accountability\n\nDescription: Creating, protecting, and retaining system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity; and ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. ## Getting Started with Audit and Accountability\n\n\n\nUnderstand and track who is performing actions within business system(s), what those actions are, and when those actions are taken. Having the ability to review system activity and analyze records, generate reports, resolve audit log process failures, and protect audit data gives the business insight into potential unauthorized activity and improves the ability to respond quickly and appropriately. Consider automated tools for conducting audit and logging activities. Products range from free, open-source tools to commercially available ones. ## Define, maintain, and protect 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."}], "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": 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 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n....................................................................... 11\n2.4 SECURITY AND PRIVACY CONTROLS .........................................................................................\n13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................. 18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ...................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 Security and Privacy Controls for Information Systems and Organizations provide? (Part 9)"}, {"role": "assistant", "content": "Murugiah Souppaya, Gary Stoneburner, Keith\nStouffer, Marianne Swanson, Pat Toth, Glenda Turner, Patrick Viscuso, Joe Weiss, Richard\nWilsher, Mark Wilson, John Woodward, and Carol Woody.\niv\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\nI\n\n. NIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nPatent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent\nclaims whose use may be required for compliance with the guidance or requirements of this\npublication disclose such patent claims to ITL. However, holders of patents are not obligated to\nrespond to ITL calls for patents and ITL has not undertaken a patent search in order to identify\nwhich, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose\nuse may be required for compliance with the guidance or requirements of this publication, no\nsuch patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent\ninfringement in the use of this publication. v\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 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 Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 9)"}, {"role": "assistant", "content": "ework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53].\nThe security control mappings can be useful to organizations that wish to demonstrate compliance to the security requirements in the context of their established information security programs when such programs have been built using the NIST security controls. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Table of Contents\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 require for Planning?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Assessing Security Requirements for Controlled Unclassified Information provide?"}, {"role": "assistant", "content": "\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": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\nEnterprise Campus Network (red de las instalaciones de la empresa). Internal App Server (servidor de aplicaciones interno). Database (base de datos). Internet (Internet). Employees (empleados). Employee (empleado). Contractor Service Tech (técnico de servicio de contratistas ). Contracted HVAC (contratación de climatización). Conference Center (centro de conferencias). Visitors (visitantes)."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 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 does CMMC Level 3 require for Configuration Management?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- Based on NIST SP 800-53, Revision 5 and the NIST SP 800-53B moderate impact control baseline.\n- Applies updated tailoring criteria addressing stakeholder feedback (adding new, consolidating, and withdrawing requirements).\n- Includes increased specificity in security requirements.\n- Introduces organization-defined parameters (ODP) to increase flexibility to better manage organizationspecific risks.\n\nControl Baseline: A set of controls you can implement to meet strategic, legal, regulatory, or contractual security and privacy requirements and manage risk."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 8)"}, {"role": "assistant", "content": "| .........................................................................................................\n4 |\n| | Organization of This Document .................................................................................. | 4 |\n| | The Enterprise Cloud-Native Platform and its Components......................................... | 5 |\n| | Enterprise Infrastructure Layer ..................................................................................."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["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": "How does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\naft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["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 2 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n...................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7.\nConfiguration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to 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": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nNIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information.\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process.\nThe baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . A separate guideline, SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, provides specific guidelines that facilitate periodic assessment of security controls to ensure that controls have been implemented correctly, are operating as intended, and are meeting the organization's security requirements. ## 2 NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)\n\nNIST SP 800-39, Managing Information Security Risk , defines risk management as 'the program and supporting processes to manage information security risk to organizational operations (including mission, functions, and reputation), organizational assets, individuals, other organizations, and the Nation'. To integrate the risk management process throughout an organization and to address its mission and business concerns, a three-tiered approach is employed. The process is carried out across three tiers with the objective of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 2 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 11)"}, {"role": "assistant", "content": "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.\ncyber deterrence is urgently needed…'\n\nThere is an urgent need to further strengthen the underlying information systems, component products, and services that we depend on in every sector of the critical infrastructure-ensuring that the systems, products, and services are sufficiently trustworthy throughout the system development life cycle (SDLC) and can provide the necessary resilience to support the economic and national security interests of the United States. System modernization, the increased use of automation, and the consolidation, standardization, and optimization of federal systems and networks to strengthen the protection for high value assets [OMB M-19-03], are key objectives for the federal government. Executive Order (E.O.) 13800, Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure [EO 13800] recognizes the increasing interconnectedness of Federal information systems and requires heads of agencies to ensure appropriate risk management not only for the Federal agency's enterprise, but also for the Executive Branch as a whole. The E.O. states:\n\n- '…The executive branch operates its information technology (IT) on behalf of the American people."}], "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": 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 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 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n.......................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................\n7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................. 18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................"}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 7)"}, {"role": "assistant", "content": "|\n| Table 1. Previous incident response life cycle model's phases and corresponding CSF 2.0 Functions.....6 |\n| Table 2.\nCSF 2.0 Community Profile part 1: Preparation and Lessons Learned ....................................11 |\n| Table 3. CSF 2.0 Community Profile part 2: Incident Response...........................................................23 |\n| List of Figures |\n| Fig. 1. Previous incident response life cycle model ..............................................................................4 |\n| Fig. 2. Incident response life cycle model based on CSF 2.0 Functions ..................................................5 |\n\n## Executive Summary\n\nIncident response is a critical part of cybersecurity risk management and should be integrated across organizational operations. All six NIST Cybersecurity Framework (CSF) 2.0 Functions play vital roles in incident response:\n\n- Govern, Identify, and Protect help organizations prevent some incidents, prepare to handle incidents that do occur, reduce the impact of those incidents, and improve incident response and cybersecurity risk management practices based on lessons learned from those incidents. - Detect, Respond, and Recover help organizations discover, manage, prioritize, contain, eradicate, and recover from cybersecurity incidents, as well as perform incident reporting, notification, and other incident-related communications. Many individuals, teams, and third parties hold a wide variety of roles and responsibilities across all of the Functions that support an organization's incident response."}], "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": 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 Incident Response?"}, {"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": "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 Zero Trust Architecture provide? (Part 5)"}, {"role": "assistant", "content": "la empresa o personal). La autenticación y la autorización (tanto del sujeto como del dispositivo) son funciones discretas que se realizan antes de establecer una sesión con un recurso de la empresa.\nLa confianza cero es una respuesta a las tendencias de las redes empresariales que incluyen usuarios remotos, dispositivos personales (BYOD, por su nombre en inglés bring-your-owned-device ) y activos basados en la nube que no se encuentran dentro de los límites de una red propiedad de la empresa. La confianza cero se centra en proteger los recursos (activos, servicios, flujos de trabajo, cuentas de red, etc.), no los segmentos de red, ya que la ubicación de la red ya no se considera el componente principal de la postura de seguridad del recurso. Este documento contiene una definición abstracta de la arquitectura de confianza cero (ZTA) y ofrece modelos generales de despliegue y casos de uso en los que la confianza cero podría mejorar la postura global de seguridad de las tecnologías de la información de una empresa. ## Palabras claves\n\nArquitectura, ciberseguridad, empresa, seguridad de la red, confianza cero. ## Agradecimientos\n\nEste documento es fruto de la colaboración entre múltiples agencias federales y está supervisado por el Consejo Federal de CIO. El subgrupo de arquitectura es responsable del desarrollo de este documento, pero hay personas concretas que merecen reconocimiento. Entre ellas se encuentran Greg Holden, director del proyecto ZTA del Consejo Federal de CIO; Alper Kerman, director del proyecto ZTA del NIST/Centro Nacional de Ciberseguridad; y Douglas Montgomery."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["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 Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.01.06.ODP[01]: personnel or roles to which privileged accounts on the system are to be restricted are defined .\n\nA.03.01.06.a: privileged accounts on the system are restricted to <A.03.01.06.ODP[01]: personnel or roles> ."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 18)"}, {"role": "assistant", "content": "ty, privacy, system, network, cloud, and other technology architects, engineers, and administrators, as well as software developers, may be involved in incident response and recovery efforts. - Legal.\nLegal experts can review incident response plans, policies, and procedures to ensure compliance with applicable laws and regulations, including the right to privacy. Legal experts can also review contracts with technology suppliers and other third parties when there are incident response implications. In addition, incident responders can seek guidance from their organization's legal department if a particular incident may have legal ramifications, such as the prosecution of a suspect, lawsuits, or situations that require a memorandum of understanding (MOU) or other binding agreement. - Public affairs and media relations. Depending on the nature and impact of an incident, it may be necessary to inform the media and, by extension, the public. Sometimes, the media learns of incidents through alternate sources (i.e., not through public affairs personnel). Having a media engagement strategy in place can greatly aid in this situation. - Human resources. Certain human resources practices should consider cybersecurity risk management, including pre-employment screening and employee onboarding, offboarding, and position changes. Human resources may also be involved if an employee is suspected of intentionally causing an incident. - Physical security and facilities management. Some computer security incidents occur through physical security breaches or involve coordinated logical and physical attacks. The incident response team may also need access to facilities during incident handling (e.g., to access a compromised workstation in a locked office). - Asset owners. Asset owners (e.g., system owners, data owners, and business process owners) may have valuable insights on response and recovery priorities for their affected assets."}], "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": 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 Zero Trust Architecture provide? (Part 17)"}, {"role": "assistant", "content": "lo general, restringir el acceso a los recursos (como los datos, los medios informáticos y las aplicaciones o servicios) solo a aquellos sujetos y activos identificados como necesarios para el acceso.\nAdemás, consiste en autenticar y autorizar continuamente la identidad y la postura de seguridad de cada solicitud de acceso. Una arquitectura de confianza cero (ZTA, por su nombre en inglés zero trust architecture ) es una estrategia de ciberseguridad empresarial basada en los principios de la confianza cero y concebida para prevenir las violaciones de datos y limitar los movimientos laterales internos. Esta publicación analiza la ZTA, sus componentes lógicos, los posibles escenarios de implementación y las amenazas. Asimismo, presenta una guía general para las organizaciones que deseen migrar a un diseño de confianza cero y examina las políticas federales 1 pertinentes que pueden afectar o influir en una arquitectura de confianza cero. La ZT no es una simple arquitectura, sino un conjunto de principios orientativos para el flujo de trabajo, el diseño del sistema y las operaciones que pueden utilizarse para mejorar la postura de seguridad de cualquier clasificación o nivel de sensibilidad (FIPS199) 2 . La transición a la ZTA es\n\n1 N. del T.: en este ejemplo y cada vez que se mencionen las políticas o agencias federales, se estará haciendo referencia a entidades de Estados Unidos. 2 N. del T.: el FIPS199 es un documento publicado por NIST que presenta las normas para la categorización de la seguridad de la información federal y del sistema de información en Estados Unidos. https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.199.pdf\n\nun proceso en el que una organización evalúa el riesgo de esa misión y no puede lograrse simplemente con una sustitución masiva de la tecnología. Ahora bien, muchas organizaciones ya cuentan con elementos de la ZTA en su infraestructura empresarial."}], "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": 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 does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| Priority | Recommendations, Considerations, Notes making on when to escalate or elevate incident response activities.\n|\n|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| GV.RM-07 | Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions | Low | |\n| GV.RR (Roles, Responsibilities, and Authorities) | Cybersecurity roles, responsibilities, and authorities to foster accountability, performance assessment, and continuous improvement are established and communicated | Medium | R1: Cybersecurity roles, responsibilities, and authorities should include incident response."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "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 Risk Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nance. The decision to select a particular set of enhanced security requirements will be based on the mission and business needs of federal agencies and guided and informed by ongoing risk assessments.\nThe enhanced security requirements for nonfederal systems processing, storing, or transmitting CUI associated with critical programs or high value assets will be conveyed to nonfederal organizations by federal agencies in a contract, grant, or other agreement. The application of the enhanced security requirements to subcontractors will also be addressed by federal agencies in consultation with nonfederal organizations."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n........................................................................................ 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE ..................................................\n6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 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 2 require for Configuration 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": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 19)"}, {"role": "assistant", "content": "a locked office). - Asset owners. Asset owners (e.g., system owners, data owners, and business process owners) may have valuable insights on response and recovery priorities for their affected assets.\nThey also need to be kept up to date on the status of response and recovery efforts. Third parties may be under contract with an organization to help perform incident response activities. Some third parties may fill a primary role (e.g., an MSSP performing incident detection, response, and recovery activities), while other parties (e.g., cloud service providers [CSPs] and internet service providers [ISPs]) may be involved in certain incident response activities for particular types of incidents. This is a shared responsibility model in which the organization transfers some of its responsibilities to a provider. These responsibilities should be clearly defined in a contract, and the incident response team should be aware of the division of responsibilities, including information flows, coordination, and authority to act on behalf of the organization. This also includes restrictions on what the service provider can do, such as sharing sanitized incident information with other customers or making and implementing operational decisions (e.g., immediately deactivating certain services to contain an incident). A service provider may detect malicious activity sooner than individual organizations would because it can correlate events across its customers. In some situations, a service provider might be able to use knowledge of an incident with one customer to proactively prevent similar incidents with its other customers. Service providers often have privileged access to organizational systems and may also have access to sensitive organizational data. Accordingly, the risk of malicious insiders or the service provider being compromised should be considered and addressed."}], "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": 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 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 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 Incident Response?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\n## Family: Incident Response"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Media Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n17 The Audit and Accountability, Maintenance, Media Protection, and Physical Protection families do not contain enhanced security requirements at this time.\n\n## 3.8 MEDIA PROTECTION"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"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": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 18)"}, {"role": "assistant", "content": "rses, 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.\n## Related Resources:\n\n- View all SP 800-171 Awareness and Training Requirements and Assessment Procedures\n- NIST Free and Low-Cost Online Cybersecurity Learning Content\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n- NARA CUI training\n- Center for Development of Security Excellence Security Awareness Hub\n\n81&/$66,),('GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1)250$7,21GLYPH<c=3,font=/BCDOEE+Wingdings-Regular>,1\n\n\n\n## Getting Started with Audit and Accountability\n\n## Family: Audit and Accountability\n\nDescription: Creating, protecting, and retaining system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate system activity; and ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. ## Getting Started with Audit and Accountability\n\n\n\nUnderstand and track who is performing actions within business system(s), what those actions are, and when those actions are taken. Having the ability to review system activity and analyze records, generate reports, resolve audit log process failures, and protect audit data gives the business insight into potential unauthorized activity and improves the ability to respond quickly and appropriately. Consider automated tools for conducting audit and logging activities. Products range from free, open-source tools to commercially available ones. ## Define, maintain, and protect 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."}], "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": 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 Security and Privacy Controls for Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "oval of the appropriate federal officials exercising policy authority over such systems. This\nguideline is consistent with the requirements of the Office of Management and Budget (OMB)\nCircular A-130.\nNothing in this publication should be taken to contradict the standards and guidelines made\nmandatory and binding on federal agencies by the Secretary of Commerce under statutory\nauthority. Nor should these guidelines be interpreted as altering or superseding the existing\nauthorities of the Secretary of Commerce, OMB Director, or any other federal official. This\npublication may be used by nongovernmental organizations on a voluntary basis and is not\nsubject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-53, Revision 5\nNatl. Inst. Stand. Technol. Spec. Publ. 800-53, Rev. 5, 492 pages (September 2020)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53r5\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe\nan experimental procedure or concept adequately. Such identification is not intended to imply\nrecommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or\nequipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by\nNIST in accordance with its assigned statutory responsibilities. The information in this publication,\nincluding concepts, practices, and methodologies may be used by federal agencies even before the\ncompletion of such companion publications. Thus, until each publication is completed, current\nrequirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n- View all SP 800-171 Access Control Requirements and Assessment Procedures\n- NIST Identity and Access Management Resources\n\n- An understanding of the need for security (why is cybersecurity important to our business mission?).\n- Specific actions required of users to maintain security (required use of multi-factor authentication, not sharing passwords, etc.).\n- How to respond to confirmed or suspected incidents.\n- How to securely handle CUI (training should be provided to staff before authorizing access to the system or CUI).\n- How to recognize and report insider threats, social engineering, and social mining."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 8)"}, {"role": "assistant", "content": "ederal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui.\n- NIST is responsible for developing and publishing the security requirements for the protection of CUI. How requirements are mandated, and any compliance issues related to nonfederal implementation of SP 800-171, are the responsibility of the federal agency requiring its use , as expressed in a specific contract or agreement. ## Additional NIST Resources\n\n- NIST's Protecting CUI Frequently Asked Questions\n- Changes Between SP 800-171 Rev. 2 and Rev. 3 (.xlsx)\n- The NIST Cybersecurity and Privacy Reference Tool (CPRT) provides online, interactive versions of the updated security requirements in SP 800-171, Revision 3 and the updated assessment procedures in SP 800-171A, Revision 3\n- Event Recording: ' CUI Security Requirements Workshop ,' which provides a general overview of SP 800 -171 and SP 800-171A\n- NIST Small Business Cybersecurity Corner\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n## What to Expect\n\nThe following pages delve deeper into the SP 800-171 R3 publication to provide more details for those responsible for implementing the requirements 3 . The following pages cover:\n\n\n\nPage 8: Key differences between SP 800-171 R2 and R3. Pages 9-10: General tips for getting started. Pages 11-28: Tips for getting started, broken out by Control Family. 3 We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 require for Security Assessment?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n|\n| CA-3(1) | UNCLASSIFIED NATIONAL SECURITY SYSTEM CONNECTIONS | W: Moved to SC-7(25). | W: Moved to SC-7(25). | W: Moved to SC-7(25). | W: Moved to SC-7(25).\n|\n| CA-3(2) | CLASSIFIED NATIONAL SECURITY SYSTEM CONNECTIONS | W: Moved to SC-7(26). | W: Moved to SC-7(26). | W: Moved to SC-7(26). | W: Moved to SC-7(26). |\n| CA-3(3) | UNCLASSIFIED NON-NATIONAL SECURITY SYSTEM CONNECTIONS | W: Moved to SC-7(27). | W: Moved to SC-7(27). | W: Moved to SC-7(27). | W: Moved to SC-7(27). |\n| CA-3(4) | CONNECTIONS TO PUBLIC NETWORKS | W: Moved to SC-7(28). | W: Moved to SC-7(28). | W: Moved to SC-7(28). | W: Moved to SC-7(28). |\n| CA-3(5) | RESTRICTIONS ON EXTERNAL SYSTEM CONNECTIONS | W: | Incorporated into | SC-7(5). | |\n| CA-3(6) | TRANSFER AUTHORIZATIONS | | | | x |\n| CA-3(7) | TRANSITIVE INFORMATION EXCHANGES | | | | |\n| CA-4 | Security Certification | W: Incorporated into CA-2. | W: Incorporated into CA-2. | W: Incorporated into CA-2. | W: Incorporated into CA-2."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ORGANIZATIONOF THIS SPECIAL PUBLICATION.................................................................................\n| 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 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_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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 8)"}, {"role": "assistant", "content": "ident-related communications. Many individuals, teams, and third parties hold a wide variety of roles and responsibilities across all of the Functions that support an organization's incident response.\nOrganizations have no direct control over the tactics and techniques used by their adversaries, nor are they certain about the timing of a future incident other than knowing that another incident is inevitable. However, organizations can use an incident response life cycle framework or model that best suits them to develop strong cybersecurity risk management practices that reduce their risks to acceptable levels. This publication uses the CSF 2.0 Functions, Categories, and Subcategories to organize its recommendations, considerations, and other information regarding incident response as a CSF 2.0 Community Profile. Doing so provides a common taxonomy that is already widely used for communicating about incident response and cybersecurity risk management and governance. This also enables organizations to access a range of online resources mapped to each Function, Category, and Subcategory through the NIST Cybersecurity and Privacy Reference Tool (CPRT). These resources include mappings to other incident response and cybersecurity risk management standards and guidance, as well as sources of implementation guidance that organizations can choose to utilize as needed. Organizations should use the incident response life cycle framework or model that suits them best. The model in this document is based on CSF 2.0 to take advantage of the wealth of resources available for CSF 2.0 and aid organizations that are already using the CSF. Regardless of the incident response life cycle framework or model used, every organization should take incident response into consideration throughout their cybersecurity risk management activities. ## 1."}], "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": 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 Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.4.1. 3.4.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 Security and Privacy Controls for Information Systems and Organizations provide? (Part 14)"}, {"role": "assistant", "content": "t of Things (IoT) devices. Safeguarding measures include\nboth security and privacy controls to protect the critical and essential operations and assets of\norganizations and the privacy of individuals.\nThe objective is to make the systems we depend on\nmore penetration resistant to attacks, limit the damage from those attacks when they occur,\nand make the systems resilient, survivable, and protective of individuals’ privacy. ix\n\n\fNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nCONTROL BASELINES\n\nThe control baselines that have previously been included in NIST Special Publication 800-53 have\nbeen relocated to NIST Special Publication 800-53B. SP 800-53B contains security and privacy\ncontrol baselines for federal information systems and organizations. It provides guidance for\ntailoring control baselines and for developing overlays to support the security and privacy\nrequirements of stakeholders and their organizations. CNSS Instruction 1253 provides control\nbaselines and guidance for security categorization and security control selection for national\nsecurity systems. 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\n. I\n\nx\n\n\fNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nUSE OF EXAMPLES IN THIS PUBLICATION\n\nThroughout this publication, examples are used to illustrate, clarify, or explain certain items in\nchapter sections, controls, and control enhancements."}], "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": 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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-03-25 Supersedes NIST SP 800-61r2 (August 2012) https://doi.org/10.6028/NIST.SP.800-61r2\n\n## How to Cite this NIST Technical Series Publication\n\nNelson A, Rekhi S, Souppaya M, Scarfone K (2025) Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-61r3. https://doi.org/10.6028/NIST.SP.800-61r3\n\n## Author ORCID iDs\n\nAlex Nelson: 0000-0002-3771-570X\n\nSanjay Rekhi: 0009-0008-8711-4030\n\nMurugiah Souppaya: 0000-0002-8055-8527\n\nKaren Scarfone: 0000-0001-6334-9486\n\n## Contact Information\n\n800-61-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory\n\n100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/61/r3/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis publication seeks to assist organizations with incorporating cybersecurity incident response recommendations and considerations throughout their cybersecurity risk management activities as described by the NIST Cybersecurity Framework (CSF) 2.0."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["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": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 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 additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 4)"}, {"role": "assistant", "content": "cation security point of view, this requires authentication and authorization policies based on application and service identities in addition to the underlying network parameters and user identities.\nThis in turn requires a platform that consists of Application Programming Interface (API) gateways, sidecar proxies, and application identity infrastructures (e.g., Secure Production Identity Framework for Everyone [SPIFFE]) that can enforce those policies irrespective of the location of the services or applications, whether on-premises or on multiple clouds. The objective of this publication is to provide guidance for realizing an architecture that can enforce granular application-level policies while meeting the runtime requirements of ZTA for multicloud and hybrid environments. ## Keywords\n\negress gateway; identity-tier policies; ingress gateway; microservices; multi-cloud; network-tier policies; service mesh; sidecar proxy; SPIFFE; transit gateway; zero trust; zero trust architecture. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["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 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 additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 8)"}, {"role": "assistant", "content": "e requirements also apply to services, including externally provided services, that process, store, or transmit CUI, or that provide security protections, for the system requiring enhanced protection.\nThe protection of a specific service to include CUI that is processed, stored or transmitted during the provision of that service, is achieved by implementing the enhanced security requirements for the service, or the system or system components responsible for providing that service. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. The term organizational system is used in many of the enhanced security requirements. It has a specific meaning regarding the applicability of the enhanced requirements as described above. Appropriate scoping considerations for the requirements are important factors in determining protection-related investment decisions and managing security risk for nonfederal organizations that have the responsibility of protecting CUI associated with critical programs and high value assets. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## FRAMEWORK FOR IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY\n\nOrganizations that have implemented or plan to implement the NIST Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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 additional guidance does Assessing Enhanced Security Requirements for Controlled Unclassified Information provide? (Part 10)"}, {"role": "assistant", "content": "| AWARENESSANDTRAINING...............................................................................................................\n| 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT..................................................................................................... | 11 |\n| 3.5 | IDENTIFICATION ANDAUTHENTICATION.......................................................................................... | 13 |\n| 3.6 | INCIDENT RESPONSE......................................................................................................................... | 15 |\n| 3.7 | MAINTENANCE ................................................................................................................................. | 16 |\n| 3.8 | MEDIAPROTECTION........................................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["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 does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nfunction of the adverse impacts that arise if the circumstance or event occurs, and the likelihood of occurrence. Types security and privacy risk (including supply chain risk); project risk; reputational risk; safety risk; strategic planning risk. 6 [OMB A-130] defines PII as 'information that can be used to distinguish or trace an individual's identity, either alone\n\nThe authorization boundary defines the system 36 for RMF execution to facilitate risk management and accountability. The system may be supported by one or more enabling systems that provide support during the system life cycle. Enabling systems are not contained within the authorization boundary of the system and do not necessarily exist in the system's environment of operation. An enabling system may provide common (i.e., inherited) controls for the system or may include any type of service or functionality used by the system such as identification and authentication services, network services, or monitoring functionality. Finally, there are other systems the system interacts with in the operational environment. The other systems are also outside of the authorization boundary and may be the beneficiaries of services provided by the system or may simply have some general interaction. 37\n\nDiscussion: Common controls are controls that can be inherited by one or more information systems. 60 Common controls can include controls from any [SP 800-53] control family, for example, physical and environmental protection controls, system boundary and monitoring controls, personnel security controls, policies and procedures, acquisition controls, account and identity management controls, audit log and accountability controls, or complaint management controls for receiving privacy inquiries from the public. Organizations identify and select the set of common controls and allocate those controls to the organizational entities designated as common control providers."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 12)"}, {"role": "assistant", "content": "DE S EGURIDAD NACIONAL , NCPS)...........................................................47 | | | 6.6 | ZTA Y PROGRAMA DE DIAGNÓSTICO Y MITIGACIÓN CONTINUOS (CDM) DEL DHS......................................................48 | | | 6.7 | ZTA, CLOUD SMART Y LA E STRATEGIA F EDERAL DE DATOS .....................................................................................48 | | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| | 7 MIGRACIÓN HACIA UNA ARQUITECTURA DE CONFIANZA CERO......................................................................50 | 7 MIGRACIÓN HACIA UNA ARQUITECTURA DE CONFIANZA CERO......................................................................50 | | | 7.1 | ARQUITECTURA DE CONFIANZA CERO PURA ..........................................................................................................50 | | | 7.2 | ARQUITECTURA HÍBRIDA BASADA EN LA ZTA Y EN EL PERÍMETRO ..............................................................................51 | | | 7.3 | PASOS PARA INTRODUCIR LA ZTA EN UNA RED CON ARQUITECTURA BASADA EN EL PERÍMETRO .......................................51 | | | 7.3.1 | Identificación de los miembros de la empresa.....................................................................................52 | | | 7.3.2 | Identificación de los activos propiedad de la empresa.........................................................................53 | | | 7.3.3 | Identificación de los procesos claves y evaluación de los riesgos asociados a la ejecución del proceso | ."}], "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": 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 10)"}, {"role": "assistant", "content": "and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance.\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement. Tailoring: The process by which control baselines are modified to achieve certain organizational goals and objectives. Definitions provided are intended as plain language. Review the NIST Glossary for official NIST definitions. Determine if your business has CUI. ## General Tips for Getting Started with NIST SP 800-171\n\nEveryone will have different approaches to getting started, but here are a few tips to get you started down the right path:\n\nUnderstand current (or future) legal, regulatory, or contractual requirements for protecting CUI. The federal agency is responsible for communicating what CUI the business is responsible for protecting as part of the contractual arrangement. If there are questions, reach out to the contracting officer. The business may also have additional compliance requirements beyond SP 800-171. If so, an initial task might be to understand where the requirements overlap and where they differ. With that information, the business can begin addressing requirements that meet multiple compliance requirements. Understand how CUI flows into, within, and out of the business. \n\nInventorying what systems or components the business has, and how the data flows into, within, and out of those systems or components, helps practitioners understand the scope of applicability of SP 800-171 security requirements to business systems. \n\nScope and Applicability of SP 800-171."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["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 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 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 additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 19)"}, {"role": "assistant", "content": "security requirements are not formally established or assigned by a federal agency or a consortium of federal agencies, nonfederal organizations must assign those values to complete the requirements.\ncontrols 15 from SP 800-53 and a list of NIST Special Publications with additional information on the topic described in the security requirement. The structure and content of a typical security requirement is provided in the example below. ## 03.13.11 Cryptographic Protection\n\nImplement the following types of cryptography when used to protect the confidentiality of CUI: [ Assignment: organization-defined types of cryptography ]. ## DISCUSSION\n\nCryptography is implemented in accordance with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidelines. FIPS-validated cryptography is recommended for the protection of CUI. ## REFERENCES\n\nSource Control: SC-13\n\nSupporting Publications: FIPS 140-3 [38]\n\nThe term organization is used in many security requirements, and its meaning depends on context. For example, in a security requirement with an ODP, an organization can refer to either the federal agency or the nonfederal organization establishing the parameter values for the requirement. Appendix C describes the security control tailoring criteria used to develop the security requirements and the results of the tailoring process. The appendix provides a list of controls from SP 800-53 that support the requirements and the controls that have been eliminated from the moderate baseline in accordance with the tailoring criteria. ## ASSESSING SECURITY REQUIREMENTS\n\nSP 800-171A [84] provides a set of procedures to assess the security requirements described in this publication. The assessment procedures are based on the procedures described in SP 800-53A [57]."}], "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": 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 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 is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.2.3 | Despliegue basado en un portal de recursos... 3.2.3), ya que la identidad y el estado del dispositivo proporcionan datos de referencia secundarios para las decisiones de acceso. 3.2.3 Despliegue basado en un portal de recursos\n\nEn este tipo de implementación, el PEP es un componente único que actúa como puerta de enlace para las solicitudes de los sujetos."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nne or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control.\n- Applying scoping considerations - these, when applied in conjunction with risk management guidance, can eliminate unnecessary security controls from the initial security control baselines and help ensure that organizations select only those controls needed to provide the appropriate level of protection for information systems. When scoping considerations are applied, compensating controls may need to be selected to provide alternative means to achieve security requirements. - Supplementing baselines - additional security controls and control enhancements are selected if needed to address specific threats and vulnerabilities."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## Family: Access Control\n\n## Getting Started with Access Control"}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\n.......................................................................................... 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ...............................................\n19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ..............................................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["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"}}