{"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to 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 does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. 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. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 2)"}, {"role": "assistant", "content": "Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. ## NISTGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> TechnicalGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> SeriesGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> PoliciesGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold>\n\nCopyright, Fair Use, and Licensing Statements Technical Series Publication Identiifier Syntax\n\n## PublicationGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> HistoryGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold>\n\nApproved by the NIST Editorial Review Board on: 2023-01-03\n\n## How to cite this NIST Technical Series PublicationGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold>\n\nHaney, JM, Jacobs, JL, Furman, SM (2023) Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges (National Institute of Standards and Technology Gaithers b urg, MD) NIST Special Publication (SP) 1288. https://doi.org/10.6028/NIST.SP.1288\n\n## NISTGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> AuthorGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> ORCIDGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold> iDsGLYPH<c=2,font=/BAAAAA+HKGrotesk-SemiBold>\n\nJulie Haney: 0000-0002-6017-9693 Jody Jacobs: 0000-0002-6433-884X Susanne Furman: 0000-0002-7013-6603\n\n## Contact Information\n\nusability@nist.gov\n\n\n\n## ABSTRACTGLYPH<c=2,font=/EAAAAA+HKGrotesk-Bold>\n\nMost United States federal government organizations are required to conduct cybersecurity role-based training for federal government personnel and supporting contractors who are assigned roles having security and privacy responsibilities."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nUDIT AND EVALUATION\nOF COMPUTER SECURITY\n\nStandards Application and Analysis —• Electronic Technology — Center for Consumer Product Technology: Product\nSystems Analysis; Product Engineering — Center for Building Technology; Structures, Materials, and Safety; Building\nEnvironment; Technical Evaluation and Application — Center for Fire Research: Fire Science; Fire Safety Engineering.\nTHE INSTITUTE FOR COMPUTER SCIENCES AND TECHNOLOGY conducts research and provides technical services\ndesigned to aid Government agencies in improving cost effectiveness in the conduct of their programs through the selection,\nacquisition, and effective utilization of automatic data processing equipment: and serves as the principal focus wthin the exec-\nutive branch for the development of Federal standards for automatic data processing equipment, techniques, and computer\nlanguages. The Institute consist of the following divisions:\n\nAudit and Evaluation\nof Computer Security ^"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "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 Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nBelow is an example of the Incident Response Testing requirement, which is part of the Incident Response (IR) family. The structure and content of a typical security requirement includes:\n\nODPs support consistent security assessments in determining whether security requirements have been satisfied. If a federal agency or a consortium of agencies do not specify a particular value or range of values for an ODP, nonfederal organizations must assign the value or values to complete the security requirement."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\n.................................................................... 41 | APPENDIX C: REFERENCES.....................................................................................................\n41 |\n\nThe information system owner 6 is the agency official responsible for the overall procurement, development, integration, modification, or operation and maintenance of the information system. The information system owner has the following responsibilities related to system security plans:"}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n.............................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1.\nBaseline Security ........................................................................................................................11 |\n| 3.2.2. Controls for Interacting With SCM Systems...............................................................................12 |\n| 4. CI/CD Pipelines -Background, Security Goals, and Entities to be Trusted .....................................13 |\n| 5. Integrating SSC Security Into CI/CD Pipelines.................................................................................15 |\n| 5.1.1. Secure Build................................................................................................................................16 |\n| 5.1.2. Secure Pull-Push Operations on Repositories............................................................................17 |\n| 5.1.3. Integrity of Evidence Generation During Software Updates......................................................18 |\n| 5.1.4. Secure Code Commits ................................................................................................................19 |"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "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 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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 10)"}, {"role": "assistant", "content": "parameters that organizations define, providing them with the ability to tailor security controls based on specific security requirements, environments of operation, and organizational risk tolerance.\nParameters assigned and/or selected by organizations for a given base control also apply to all control enhancements associated with that control. The first security control in each family (referred to as the dash-1control) addresses policies and procedures needed for effective implementation of all the other controls within each family. Therefore, requirements to develop policies and procedures are not repeated in individual controls. Many security controls and enhancements include supplemental guidance. The supplemental guidance provides additional information about a control or enhancement to help organizations define, develop, and/or implement security controls but does not include any additional requirements. SP 800-53 Rev. 4 includes many changes from SP 800-53 Rev. 3 - 295 controls and control enhancements were added while approximately 100 controls and control enhancements were withdrawn or incorporated into others. Of the eighteen security control families in SP 800-53 Rev. 4, seventeen families are described in the security control catalog in Appendix F, and are closely aligned with the seventeen minimum security requirements for federal information and information systems in FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . One additional family, the Program Management (PM) family, provides controls for information security programs themselves. This family is described in Appendix G of SP 800-53 Rev. 4. While it is not specifically referenced in FIPS 200, the PM section provides security controls at the organization level rather than the information system level. The PM controls are typically implemented at the organization level and not directed at individual organizational information systems."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nCovered entities need to be cognizant of differentiating between best practices versus what the Security Rule requires. Vendor management and supply chain risks are important topics due to the potential they have to introduce new threats and risks to organizations. However, to the extent that such vendors and service providers are business associates, HIPAA treats them the same as covered entities with respect to Security Rule compliance. Covered entities and business associates are required to obtain written satisfactory assurances that PHI will be protected. Covered entities and business associates are permitted to require more of their business associates and even include more stringent cybersecurity requirements in a business associate agreement (BAA). These requirements would need to be agreed upon by both the covered entity and the business associate.\n\nCovered entities need to be cognizant of differentiating between best practices versus what the Security Rule requires. Vendor management and supply chain risks are important topics due to the potential they have to introduce new threats and risks to organizations. To the extent that such vendors and service providers are business associates, HIPAA treats them the same as covered entities with respect to Security Rule compliance. Covered entities and business associates are required to obtain written satisfactory assurances from business associates that PHI will be protected. Covered entities and business associates are permitted to require more of their business associates and even include more stringent cybersecurity requirements in a BAA. These requirements would need to be agreed upon by both the covered entity and the business associate.\n\nHealth Industry Cybersecurity Supply Chain Risk Management"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for 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 require for Physical Protection?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nAntwan Clark Laboratory for Physical Sciences\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. In addition to the management software that installs, boots, configures, and manages HPCrelated systems, HPC application codes rely on several layers of scientific and performanceenhancing libraries. The layers of software that are available to users are referred to as the software stack. The lower layers of this stack are typically focused on performance and include compilers, communication libraries, and user-space interfaces to HPC hardware components. The middle layer includes performance tools, math libraries, and data or computation abstraction layers. The top of the stack consists of end-user science or production applications. Each software product within this stack may require certain versions or variants of other products and have many dependencies. For example, Hierarchical Data Format Version 5 (HDF5) [20] is a scientific data formatting library with only seven dependencies, while Data Mining Classification and Regression Methods (rminer) [21] - an R-based data mining application - has 150 software dependencies."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 4)"}, {"role": "assistant", "content": ") 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.\nITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. 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................................................................................................................. | Executive Summary................................................................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nissions or access to other product components. - c. Maintain appropriate access control during initial connection (i.e., onboarding) and when reestablishing connectivity after disconnection or outage.\n| Vulnerability | Relevant Consumer Profile Capabilities |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Mirai Malware Variants Attacks - Use of weak authentication to enable the loading of malware onto the device and use that device in DDOS and other attacks. | Mirai Malware Variants Attacks - Use of weak authentication to enable the loading of malware onto the device and use that device in DDOS and other attacks. |\n| Unauthorized access to the IoT device | Asset Identification Interface Access Control Information Dissemination Education and Awareness |\n| Malicious code can be loaded on the IoT device | Software Update Cybersecurity State Awareness Education and Awareness |"}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. The security control baselines address the security needs of a broad and diverse set of constituencies, and are developed based on a number of general assumptions, including common environmental, operational, and functional considerations. The baselines also assume typical threats facing common information systems. Articulating the underlying assumptions is a key element in the initial risk framing step of the risk management process described in NIST SP 800-39. To ensure that an appropriate set of controls is identified to provide security commensurate with risk, organizations tailor the controls to align with specific security needs. Organizations may perform tailoring at the organization level for all information systems, in support of a particular line of business or mission/business process, at the individual information system level, or by using a combination of the above. The tailoring process is comprised of several steps, as described in SP 800-53 Rev. 4 Section 3.2. These actions include:\n\n- Identifying and designating common controls - controls that may be inherited by one or more information systems. If an information system inherits a common control, such as environmental controls within a data center, that system does not need to explicitly implement that control."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 3-8 |\n| Fig. | 1 | Responsibilities and Duties to Provide Security for Data Processing System ..\n| 3-5 |\n| PART | | SESSION 2 ~ MANAGERIAL AND ORGANIZATIONAL VULNERABILITIES AND CONTROLS ~ LINE LEVEL - DATA PROCESSING | |\n| | IV: | | 4-1 |\n| | | | 4-2 |\n| 1. | EDITOR'S | NOTE INTRODUCTION 4-3 | 4-3 4-3 |\n| | 1.1 1.2 1.3 | The Charge Intent of Paper | 4-3 4-3 |\n| 2. | 1.4 | Elements of Discussion Comments | 4-4 |\n| | DATA | PROCESSING \"."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "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 Overview and Considerations of Access Control Based on Attribute Encryption:\n\ntributes for permissions. This means that there is no choice but to trust the key issuer. Such accountability for user secret keys provides fine-grained access without flexibility or scalability [BS].\nThis makes it unsuitable for certain applications unless it is supported by re-encryption techniques [GOLIC] or integrated with legacy systems such that the key generation system does not manage permission by itself instead of receiving the entitlement data from other system components (e.g., a user permission database so data owners are able to verify such data)."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 6)"}, {"role": "assistant", "content": ".................................................................. | Introduction ......................................................................................................................\n|\n|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|\n| | Purpose and Scope.................................................................................................... | 1 |\n| | Audience .................................................................................................................... | 1 |\n| | Relevance to NIST SP 800-70 and the National Checklist Program ..........................."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Developing Security Plans for Federal Information Systems provide? (Part 4)"}, {"role": "assistant", "content": "|\n| 1.4 SYSTEMS INVENTORY AND FEDERAL INFORMATION PROCESSING STANDARDS (FIPS 199) | ......\n2 |\n| 1.5 MAJOR APPLICATIONS, GENERAL SUPPORT SYSTEMS, AND MINOR APPLICATIONS | .................. 2 |\n| 1.6 OTHER RELATED NIST PUBLICATIONS ..................................................................................... | 3 |\n| 1.7 SYSTEM SECURITY PLAN RESPONSIBILITIES .............................................................................. | 3 |\n| 1.7.1 Chief Information Officer ................................................................................................ | 4 |\n| 1.7.2 Information System Owner | ............................................................................................... 5 |\n| 1.7.3 Information Owner | ..........................................................................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Access Control?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nminimum, the IoT product component shall:\n- a. Use and have access only to interfaces necessary for the IoT product's operation. All other channels and access to channels are removed or secured. - b.\nFor all interfaces necessary for the IoT product's use, access control measures are in place (e.g., unique password-based multifactor authentication, physical interface ports inaccessible from the outside of a component). - c. For all interfaces, access and modification privileges are limited. 2. Some, but not necessarily all, IoT product components have the means to protect and maintain interface access control. At a minimum, the IoT product shall:\n- a. Validate that data shared among IoT product components match specified definitions of format and content. - b. Prevent unauthorized transmissions or access to other product components. - c. Maintain appropriate access control during initial connection (i.e., onboarding) and when reestablishing connectivity after disconnection or outage."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "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 Planning?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nTo aid in review activities, security planning, and risk assessments, organizations document the relevant decisions taken during the security control selection process, providing a sound rationale for those decisions. This documentation is essential when examining the security considerations for organizational information systems with respect to the potential impact on an organization's mission and business.\n\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3.\n\nFederal agencies are required to ensure that privacy protections are incorporated into information security planning. To that end, SP 800-53 Rev. 4 features eight new families of privacy controls that are based on the internationally accepted Fair Information Practice Principles (FIPPs). The proliferation of social media, Smart Grid, mobile, and cloud computing, as well as the transition from structured to unstructured data and metadata environments, have added significant complexities and challenges for federal organizations in safeguarding privacy. These challenges extend well beyond the traditional information technology security view of protecting privacy, which focused primarily on ensuring confidentiality."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 6)"}, {"role": "assistant", "content": "ents in SP 800-171. If you have questions regarding requirements to protect CUI or other regulatory requirements, please contact your prime contractor and/or federal point of contact for the contract.\n|\n|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| How do I know if I have CUI? | It is the responsibility of the federal agency to ensure that requirements to protect CUI are identified in applicable contracts or agreements, and CUI is marked by the federal agency. |\n| How do I get a 'NIST SP 800 -171 Assessment'? | The term 'NIST Assessment' and 'NIST SP 800 - 171 Assessment' is frequently used to describe the Department of Defense (DOD) proce ss used to complete its NIST SP 800-171 Assessment Module through the Supplier Performance Risk System (SPRS). NIST develops the underlying technical guidelines (SP 800-171, SP 800-171A, SP 800-172, and SP 800- 172A) on which the 'NIST Assessment' is based, but NIST does not have a role in DOD's implementation of its programs . For additional guidance on NIST's methodology to plan, prepare for, and conduct security requirement assessments, refer to SP 800-171A. |\n| What products, vendors, or solutions are 'NIST SP 800 -171 compliant' or 'CMMC - certified'? | NIST does not identify or track implementation of or compliance with the security requirements."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n.................. | 50 |\n| 5.3.3 | PR.AC-4: Access Permissions and Authorizations are Managed, Incorporating the Principles of Least Privilege and Separation of Duties .........................\n50 | |\n| 5.3.4 | PR.AC-7: Users, Devices, and Other Assets are Authenticated (e.g., single-factor, multi-factor) Commensurate with the Risk of the Transaction (e.g., Individual Security and Privacy Risks and Other Organizational Risks) | 50 |\n| 5.3.5 | PR.DS-1: Data-at-Rest is Protected......................................................................... | 51 |\n| 5.3.6 | PR.DS-6: Integrity Checking Mechanisms are Used to Verify Software, Firmware, and Information Integrity ..................................................................... | 51 |\n| 5.3.7 | PR.IP-4: Backups of Information are Conducted, Maintained, and Tested............ | 51 |\n| 5.3.8 | PR.MA-1: Maintenance and Repair of Organizational Assets are Performed and Logged, with Approved and Controlled Tools ...................................... | 51 |\n| 5.3.9 | PR.MA-2: Remote Maintenance of Organizational Assets is Approved, Logged, and Performed in a Manner that Prevents Unauthorized Access............... | 51 |\n| 5.3.10 | DE.AE-1: A Baseline of Network Operations and Expected Data Flows for Users Systems is Established and Managed................................................... | and 52 |\n| 5.3.11 | DE.AE-2: Detected Events are Analyzed to Understand Attack Targets And Methods | |"}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nld be action-based messages directed at consumers. For example, simplifying communication and facilitating customer outreach are ways to promote awareness and understanding of cybersecurity practices.\nGovernment-led programs for consumer education were seen as vital by the audience in driving consumer engagement and encouraging consumers to value secure products. It was noted that 'one size fits all communications' does not address the varying levels of knowledge in the general public."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "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 does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\n- [20] James M. Higdon, Gerald Oveson, Efficient Test of Configurations and Orders of Complex Operating Procedures Tech. Rpt., COLSA North Florida Ops, 96th Cyberspace Test Group, AFMC, Eglin AFB, FL, 4 Apr 2018. - [21] Duan F, Lei Y, Kacker RN, Kuhn DR. An Approach to T-Way Test Sequence Generation With Constraints. 2019 IEEE Intl Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2019 Apr 22 (pp. 241-250). IEEE. - [22] Garn B, Simos DE, Duan F, Lei Y, Bozic J, Wotawa F. Weighted Combinatorial Sequence Testing for the TLS Protocol. In2019 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2019 Apr 22 (pp. 46-51). IEEE. - [23] Oetsch J, Nieves JC. Stable-Ordered Models for Propositional Theories with Order Operators. InEuropean Conference on Logics in Artificial Intelligence 2019 May 7 (pp. 794-802). Springer, Cham. - [24] Yuster R. Perfect sequence covering arrays. Designs, Codes and Cryptography. 2020 Mar;88(3):585-93. - [25] Younis MI. MVSCA: Multi-Valued Sequence Covering Array. Journal of Engineering. 2019 Oct 29;25(11):8291. - [26] D.R. Kuhn, I. Dominguez, R.N. Kacker and Y. Lei. \"Combinatorial Coverage Measurement Concepts and Applications\", 2nd Intl Workshop on Combinatorial Testing , Luxembourg, IWCT2013, IEEE, Mar. 2013. - [27] Zamli KZ, Othman RR, Zabil MH. On sequence based interaction testing. In2011 IEEE Symposium on Computers & Informatics 2011 Mar 20 (pp. 662-667). IEEE. - [28] Kuhn DR, Higdon JM, Lawrence JF, Kacker RN, Lei Y. Efficient methods for interoperability testing using event sequences. FLIGHT TEST SQUADRON (46TH) EGLIN AFB FL; 2012 Aug 1. - [29] Yilmaz C, Fouche S, Cohen MB, Porter A, Demiroz G, Koc U. Moving forward with combinatorial interaction testing. Computer. 2013 Dec 11;47(2):37-45. - [30] Garn B, Simos DE, Zauner S, Kuhn R, Kacker R. Browser fingerprinting using combinatorial sequence testing."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "System and 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 Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 4)"}, {"role": "assistant", "content": "s recommendation provides a technical guideline to use Personal Identity Verification (PIV) Cards in facility access; enabling federal agencies to operate as government-wide interoperable enterprises.\nThese guidelines cover the risk-based strategy to select appropriate PIV authentication mechanisms as expressed within Federal Information Processing Standard (FIPS) 201. ## Keywords\n\ncredential; e-authentication; identity credential; issuance; personal identity verification (PIV); physical access control system (PACS); PIV authentication mechanisms; PIV cards; public key infrastructure (PKI); validation\n\n## Acknowledgements\n\nThe authors of SP 800-116 Revision 1 (Hildegard Ferraiolo of NIST; Nabil Ghadiali of the National Gallery of Art; and Jason Mohler, Vincent Johnson, and Steven Brady of Electrosoft Services, Inc.) wish to thank William MacGregor, Ketan Mehta, and Karen Scarfone for their substantial contribution towards the original version of this publication, and David Cooper for his substantial contribution towards both the original version of this publication and the draft version of this revision. The authors also gratefully acknowledge and appreciate the support and contributions by many others in the public and private sectors whose helpful and beneficial comments greatly enhance the utility of this publication. Special thanks to the Interagency Security Committee (ISC), the General Services Administration, the Department of Homeland Security, the Department of Defense, and the Office of Management and Budget for their review and contributions to this document. ## Audience\n\nThis document is intended for government officials responsible for implementing Homeland Security Presidential Directive-12 (HSPD-12) compliant physical access control systems (PACS). Information in this document is also useful to government contractors and physical security vendors that provide HSPD-12 systems, products, and integration services."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n| | 5.4 Specific Details ........................................................................................................... | 5.4 Specific Details ........................................................................................................... | 5.4 Specific Details ..........................................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "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 Guide for Developing Security Plans for Federal Information Systems:\n\n2 OMB Circular A-130, Appendix III, defines general support system as an interconnected set of information resources under the same direct management control that shares common functionality. It normally includes hardware, software, information, data, applications, communications, and people. system to the high watermark or highest impact level must be applied when grouping minor applications/subsystems with varying FIPS 199 impact levels into a single general support system or major application unless there is adequate boundary protection, e.g., firewalls and encryption, around those subsystems or applications with the highest impact level. Additionally, there must be assurance that the shared resources, i.e., networks, communications, and physical access within the whole general support system or major application, are protected adequately for the highest impact level. Having the ability to isolate the high impact systems will not only result in more secure systems, but will also reduce the amount of resources required to secure many applications/systems that do not require that level of security. NIST SP 800-53 provides three security control baselines, i.e., low, moderate, and high, that are associated with the three FIPS 199 impact levels; as the impact level increases, so do the minimum assurance requirements. For reporting purposes, i.e., FISMA annual report, when an information system has varying FIPS 199 impact levels, that system is categorized at the highest impact level on that information system. Major applications are systems that perform clearly defined functions for which there are readily identifiable security considerations and needs (e.g., an electronic funds transfer system). A major application might comprise many individual programs and hardware, software, and telecommunications components. These components can be a single software application or a combination of hardware/software focused on supporting a specific, mission-related function."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n1.3.3. Customer Experience . . . . . . . . . . . . . . . . . . . . . . .\n\n3.3.\n\n3.3.1. Assurance Levels . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 10)"}, {"role": "assistant", "content": "s in this Profile do not distinguish between human-written and AI-generated source code, because it is assumed that all source code should be evaluated for vulnerabilities and other issues before use.\n## Sources of Expertise\n\nThis document leverages and integrates numerous sources of expertise, including:\n\n- NIST research and publications on trustworthy and responsible AI, including the Artificial Intelligence Risk Management Framework (AI RMF 1.0) [2], Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations [3], Towards a Standard for Identifying and Managing Bias in Artificial Intelligence [4], and the Dioptra experimentation testbed for security evaluations of machine learning algorithms [5]. - NIST's Secure Software Development Framework (SSDF) Version 1.1 [6], which is a set of fundamental, sound, and secure software development practices. It provides a common language to help facilitate communications among stakeholders, including software producers and software acquirers. The SSDF has also been used in support of EO 14028, Improving the Nation's Cybersecurity [7], to enhance software supply chain security. - NIST general cybersecurity resources, including The NIST Cybersecurity Framework (CSF) 2.0 [8], Security and Privacy Controls for Information Systems and Organizations [9], and Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations [10]. - AI model developers, AI researchers, AI system developers, and secure software practitioners from industry and government with expertise in the unique security challenges of AI models and the practices for addressing those challenges. This expertise was primarily captured through NIST's January 2024 workshop, where speakers and attendees shared suggestions for adapting secure software development practices and tasks to accommodate the unique aspects of AI model development and the software leveraging them."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\nIn addition, seven out of 21 organizations commented that maintaining FIPS certification may, in some cases, weaken security and erode confidence by discouraging updates throughout the lifecycle of the product. Once a product undergoes a significant update (for example, a planned product revision or a bug or security vulnerability fix), it may lose its certification. Organizations are then put in a difficult position or may experience resource burdens to remedy the situation. 'The vulnerability is inside of-- let's say it's inside the FIPS module. This is the case where FIPS 140 is horrible because literally the way the rules are written now, fixing that vulnerability takes the FIPS 140 validation away. And theoretically, you should not be able to sell to a company now. So instead of fixing it, we put it in a queue. And then there's six months to a year to a year and a half to two years before it comes out. So the right thing to do is you fix it. So literally, the right thing to do is they fix it. They don't have FIPS 140 anymore, so why do they worry about FIPS 140 at all? They just lost it. The right thing to do from a security standpoint. So this ability to address vulnerabilities and to patch validated code is a real problem. It sends the wrong message if you do what you should do, which is patch it and live without it. Just live without the compliance until you're able to go through the FIPS process. In fact, the FIPS process takes so long, at some point they go, 'Why?' … I was at the CMVP conference three or four weeks ago, and…three or four people that program OpenSSL said their code was more secure without FIPS than with FIPS. The FIPS made it less secure. And I think one of the main reasons is this inability to quickly and agilely address vulnerabilities. So that needs to be fixed. They need to find some process.' (C19)\n\n'Now, certification is a problem there."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n| EXECUTIVE SUMMARY........................................................................................................III | EXECUTIVE SUMMARY........................................................................................................III | EXECUTIVE SUMMARY........................................................................................................III |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 INTRODUCTION................................................................................................................. 1 | 1 INTRODUCTION................................................................................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice 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 is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.3.2 KAS2-Party_V-confirmation | ... 3.3.2 and 8. 3.3.2 can be used to provide assurance to a key-pair owner, acting as party U, that both parties are in possession of the correct private key; i."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Data Structure for Integrity Protection with Erasure Capability provide? (Part 5)"}, {"role": "assistant", "content": "j and B = 1 , so the invariant holds, and for each iteration of the loop, the invariant is maintained. ̸\n\nTheorem 4 (Block dispersal) . No consecutive blocks appear in the same row or column.\nThat is, for any two blocks numbered a, b , where b = a +1 , in rows i a and i b , and columns j a and j b respectively, i a = i b and j a = j b . ̸\n\nProof. This can be shown by considering cases below. ̸\n\n1. If i < j , then block a will be written to cell ( i a , j a ) and then i and j swapped, so that in the next iteration, i > j , and block b written to cell ( i b , j b ) . Since i b = j a and j b = i a , and i = j , i a = i b and j a = j b . ̸\n\n̸\n\n2. If i > j , then block a will be written to cell ( i a , j a ) , j incremented, and then i and j swapped. Then either the relationship is unchanged, with i > j , or i = j . ̸\n\n2(a). If i = j , then no data block will be written in the next iteration, but i will be set to 0 and j will be incremented such that i < j , and the next data block written with i b = 0 and j b = j a +1 , ensuring that i a = i b and j a = j b . ̸\n\n̸\n\n2(b). if i > j , then on the next iteration, block b will be written with i b = j a and j b = i a , and i = j , so that i a = i b and j a = j b . ̸\n\n̸\n\n## IV. BLOCK LOCATION\n\nWith the relations above, one can derive expressions to locate a given block within the matrix. The following relations are clear (see Fig. 2 for example) where N = number of columns = number of rows; row and column indexes range from 0 to N -1 . - The total number of data blocks in the matrix is N 2 -N since the diagonal is null. Thus, the last\n- numbered block in a filled matrix of N rows and columns is number N 2 -N ."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 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 Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n...... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................\n5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ...................................................................................................... | 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| | 2.2.4 AIS Life Cycle Matrix | 2.2.4 AIS Life Cycle Matrix | 2.2.4 AIS Life Cycle Matrix | 24 | | 2.3 | LIFE CYCLE PHASES | LIFE CYCLE PHASES | LIFE CYCLE PHASES | 26 | | | 2.3.1 Initiation - Phase I | 2.3.1 Initiation - Phase I | 2.3.1 Initiation - Phase I | 27 | | | 2.3.2 Definition - Phase II | 2.3.2 Definition - Phase II | 2.3.2 Definition - Phase II | 27 | | | 2.3.3 System Design - Phase III | 2.3.3 System Design - Phase III | 2.3.3 System Design - Phase III | 27 | | | 2.3.4 Programming and Training - Phase IV | 2.3.4 Programming and Training - Phase IV | 2.3.4 Programming and Training - Phase IV | 28 | | | 2.3.5 Evaluation and Acceptance - Phase V | 2.3.5 Evaluation and Acceptance - Phase V | 2.3.5 Evaluation and Acceptance - Phase V | 28 | | | 2.3.6 Installation and Operation - Phase VI | 2.3.6 Installation and Operation - Phase VI | 2.3.6 Installation and Operation - Phase VI | 29 | | 2.4 | RESPONSIBLE PARTICIPANTS AND THEIR FUNCTION"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\n..................................................................... | 5.4 Specific Details ...........................................................................................................\n| 29 |\n|------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|\n| 6 | Functional Demonstrations...............................................................30 | Functional Demonstrations...............................................................30 | Functional Demonstrations...............................................................30 | |\n| | 6.1 | Usage Scenarios Supported ....................................................................................... | Usage Scenarios Supported ......................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nof network events that can be used to identify patterns of performance and security issues. - Access control functions: Access control functions enforce granular sophisticated access control policies.\n- Multiple locations and functions: Firewalls reside at different locations to perform different functions. Firewalls at the network edge perform the network perimeter protection function by filtering disallowed sources and destinations and blocking the packets of potential threats. Firewalls inside a data center can segment the internal network to prevent the lateral movement of traffic and isolate sensitive resources (e.g., services and data stores). Device-based firewalls prevent malicious traffic in and out of endpoints. - Open Application Programming Interfaces (APIs): These enable integration with many networking products that provide additional security capabilities. - Policy Composition Capabilities: Some firewalls can have the capabilities to merge policies at enforcement time so as to ensure that consistent policies are applied to different classes of users (e.g., those on-premises and on private and public clouds). - Web application firewalls (WAF): This class of firewalls has been used ever since web applications accessed through web protocols, such as Hypertext Transfer Protocol"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "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 Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide?"}, {"role": "assistant", "content": "## Risk Management Framework for Information Systems and Organizations\n\nA System Life Cycle Approach for Security and Privacy\n\nThis publication contains comprehensive updates to the Risk Management Framework . The updates include an alignment with the constructs in the NIST Cybersecurity Framework; the integration of privacy risk management processes; an alignment with system life cycle security engineering processes; and the incorporation of supply chain risk management processes. Organizations can use the frameworks and processes in a complementary manner within the RMF to effectively manage security and privacy risks to organizational operations and assets, individuals, other organizations, and the Nation. Revision 2 includes a set of organization-wide RMF tasks that are designed to prepare information system owners to conduct system-level risk management activities. The intent is to increase the effectiveness, efficiency, and cost-effectiveness of the RMF by establishing a closer connection to the organization's missions and business functions and improving the communications among senior leaders, managers, and operational personnel. ## JOINT TASK FORCE\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-37r2\n\n\n\n## NIST Special Publication 800-37\n\nRevision 2\n\n## Risk Management Framework for Information Systems and Organizations\n\n## A System Life Cycle Approach for Security and Privacy\n\n## JOINT TASK FORCE\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-37r2\n\n## December 2018\n\n\n\nU.S. Department of Commerce Wilbur L."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nA software development life cycle (SDLC) 1 is a formal or informal methodology for designing, creating, and maintaining software (including code built into hardware). There are many models for SDLCs, including waterfall, spiral, agile, and - in particular - agile combined with software development and IT operations (DevOps) practices. Few SDLC models explicitly address software security in detail, so secure software development practices usually need to be added to and integrated into each SDLC model. Regardless of which SDLC model is used, secure software development practices should be integrated throughout it for three reasons: to reduce the number of vulnerabilities in released software, to reduce the potential impact of the exploitation of undetected or unaddressed vulnerabilities, and to address the root causes of vulnerabilities to prevent recurrences. Vulnerabilities include not just bugs caused by coding flaws, but also weaknesses caused by security configuration settings, incorrect trust assumptions, and outdated risk analysis."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 9)"}, {"role": "assistant", "content": "and ISO/IEC 19790 Annex B apply and are required in the security policy as applicable. ISO/IEC 19790 Annex B uses the same section naming convention as ISO/IEC 19790 Section 7 -Security requirements .\nFor example, Annex B Section B.2.1 is named 'General,' and B.2.2 is named 'Cryptographic module specification,' which is the same as ISO/IEC 19790 Section 7.1 and Section 7.2, respectively. Therefore, the format of the security policy shall be presented in the same order as indicated in Annex B, starting with 'General' and ending with 'Mitigation of other attacks.' If sections are not applicable, they shall be marked as such in the security policy. ISO/IEC 24759 Section 6.14 Cryptographic module security policy requirements are modified as indicated below:\n\nNo change. ISO/IEC 19790 Annex B requirements are modified as indicated below:\n\n## · B.2.1 General\n\nNo change. ## · B.2.2 Cryptographic module specification\n\n- Illustrative diagram, schematic, or photograph of the module. A photograph included for hardware modules. If the security policy encompasses multiple versions of the module, each version is represented separately or annotated that the representation is illustrated for all versions. For a software or , firmware, hybrid, or sub-chip cryptographic module, the security policy includes a block diagram that illustrates:\n- o The location of the logical object of the software or firmware module with respect to the operating system, other supporting applications, and the cryptographic boundary so that all of the logical and physical layers between the logical object and the cryptographic boundary are clearly defined and\n- o The interactions of the logical object of the software or firmware module with the operating system and other supporting applications resident within the cryptographic boundary."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.3.1 | Variaciones del algoritmo de confianza... 3.3.1). 3.3.1)."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| 1 | Summary.............................................................................................1 | Summary.............................................................................................1 | Summary.............................................................................................1 | |-----|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | | 1.2 | Solution..........................................................................................................................3 | | | | 1.3 | Benefits..........................................................................................................................4 | | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | | 2.1 | Typographic Conventions..............................................................................................5 | | | 3 | Approach.............................................................................................6 | Approach.............................................................................................6 | | | | 3.1 | Audience........................................................................................................................6 | | | | 3.2 | Scope .............................................................................................................................6 | | | | | 3.2.1 Scenario 1: Creation of Verifiable Platform | Artifacts ..................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "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 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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.3.2 | Test Results... 3.3.2 Test Results\n\nFigure D-35 shows the remote connection being established through the Cisco AnyConnect VPN application, where a browser is used to access the ConsoleWorks web interface (Figure D-36). 3.3.2 eyeSight\n\nUsing the Forescout Console application, users may configure, monitor, and manage the eyeSight appliance and agents."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process.\nThe baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems . A separate guideline, SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations, provides specific guidelines that facilitate periodic assessment of security controls to ensure that controls have been implemented correctly, are operating as intended, and are meeting the organization's security requirements. ## 2 NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)\n\nNIST SP 800-39, Managing Information Security Risk , defines risk management as 'the program and supporting processes to manage information security risk to organizational operations (including mission, functions, and reputation), organizational assets, individuals, other organizations, and the Nation'. To integrate the risk management process throughout an organization and to address its mission and business concerns, a three-tiered approach is employed. The process is carried out across three tiers with the objective of continuous improvement in the organization's risk-related activities, with effective communication among tiers and stakeholders. Figure 1 illustrates the three-tiered approach to risk management."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer support CMMC certification?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 9)"}, {"role": "assistant", "content": "|\n| Table 1.\nExample Consumer IoT Vulnerabilities and the Relevant Capabilities from the Consumer Profile..........................................................................................................17 Table 2. Highlighted Insights and Key Takeaways from the Consumer Profiling Process. ........20 | Table 1. Example Consumer IoT Vulnerabilities and the Relevant Capabilities from the Consumer Profile..........................................................................................................17 Table 2. Highlighted Insights and Key Takeaways from the Consumer Profiling Process. ........20 | Table 1. Example Consumer IoT Vulnerabilities and the Relevant Capabilities from the Consumer Profile..........................................................................................................17 Table 2. Highlighted Insights and Key Takeaways from the Consumer Profiling Process."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 3)"}, {"role": "assistant", "content": "inh H, Van Wyk I (2023) Recommendations for Federal Vulnerability Disclosure Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST (Special Publication) NIST SP 800-216.\nhttps://doi.org/10.6028/NIST.SP.800-216\n\n## Author ORCID iDs\n\nKim Schaffer: 0000-0003-3073-2395\n\nPeter Mell: 0000-0003-2938-897X\n\nHung Trinh: 0000-0002-3323-0836\n\nIsabel Van Wyk: 0000-0001-8566-6829\n\n## Contact Information\n\nsp800-216-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\nReceiving reports on suspected security vulnerabilities in information systems is one of the best ways for developers and services to become aware of issues. Formalizing actions to accept, assess, and manage vulnerability disclosure reports can help reduce known security vulnerabilities. This document recommends guidance for establishing a federal vulnerability disclosure framework, properly handling vulnerability reports, and communicating the mitigation and/or remediation of vulnerabilities. The framework allows for local resolution support while providing federal oversight and should be applied to all software, hardware, and digital services under federal control. ## Keywords\n\nadvisory; Federal Coordination Body; findings report; source vulnerability report; vulnerability communication; Vulnerability Disclosure; Vulnerability Disclosure Policy; Vulnerability Disclosure Program Office; vulnerability processing; vulnerability tracking. ## 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."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n- The first column defines the capability. Note that Figure 1, which is located in Appendix A, indicates how the capability relates to the risk mitigation areas and challenges defined in NISTIR 8228, Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks [3]. - The second column provides a numbered list of common elements of that capability-elements an organization seeking to implement the core baseline often (but not always) would use in order to achieve the capability. (Note: the elements are not intended to be comprehensive, nor are they in any particular order.)\n- The third column explains the rationale for needing the capability and its common elements to be included in the core baseline. - The last column lists IoT reference examples that indicate existing sources of IoT device cybersecurity guidance specifying a similar or related capability. Because the table only covers the basics of the capabilities, the references can be invaluable for understanding each capability in more detail and learning how to implement each capability in a reasonable manner."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to 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 Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n........................................................................ | CHAPTERONE INTRODUCTION......................................................................................................\n| 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nThe profile builds on the NISTIR 8259 series by extending the IoT core baseline for consumer IoT products. NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers [IR8259], provides foundational guidance for IoT device manufacturers pertaining to developing IoT devices that can be used securely by customers. NISTIR 8259 does not target any specific IoT sector but discusses how manufacturers can approach cybersecurity for IoT devices in general. NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline [IR8259A] and NISTIR 8295B, IoT Non-Technical Supporting Capability Core Baseline [IR259B] define the IoT device cybersecurity capability core baseline (also referred to as the core baseline). The core baseline is a starting point for manufacturers to use in identifying the cybersecurity capabilities their customers may expect from the IoT devices they create. NISTIR 8259A discusses device cybersecurity capabilities, which are functions or features implemented by the device through its own hardware and software. For example, NISTIR 8259A discusses concepts such as data protection, access control, and software update, among others. NISTIR 8259B discusses non-technical supporting capabilities, which are actions taken by organizations to support the cybersecurity of the device. For example, NISTIR 8259B discusses concepts such as education and awareness, and information and query reception (e.g., by manufacturers/developers). 1. Each IoT product component controls access to and from all interfaces (e.g., local interfaces, whether externally accessible or not, network interfaces, protocols, and services) in order to limit access to only authorized entities. At a minimum, the IoT product component shall:\n- a. Use and have access only to interfaces necessary for the IoT product's operation. All other channels and access to channels are removed or secured. - b."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "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": "How does IoT Device Cybersecurity Capability Core Baseline support CMMC certification?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Karen Scarfone Matthew Smith\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\n\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Applied Cybersecurity Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nMatthew Smith Huntington Ingalls Industries Annapolis Junction, MD\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nMay 2020\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259A 23 pages (May 2020)\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.1 (NIST 3.6.1)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.6.1 Scenario\n\nThe following scenario was simulated to test the architecture's defense against malicious file and backup modification."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.6.1", "cmmc_practice_id": "IR.L2-3.6.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThis includes requirements from internal sources (e.g., the organization's policies, business objectives, and risk management strategy) and external sources (e.g., applicable laws and regulations). | PO.1.1 : Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. | Example 1 : Define policies for securing software development infrastructures and their components, including development endpoints, throughout the SDLC and maintaining that security. Example 2 : Define policies for securing software development processes throughout the SDLC and maintaining that security, including for open-source and other third-party software components utilized by software being developed. Example 3 : Review and update security requirements at least annually, or sooner if there are new requirements from internal or external sources, or a major security incident targeting software development infrastructure has occurred. Example 4 : Educate affected individuals on impending changes to requirements."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\ntouching the smart card's contact pad. The PIV contact interface is standardized by International Organization of Standards / International Electrotechnical Commission (ISO/IEC) 7816-3 [ISO/IEC7816].\n|\n|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Contactless Reader | A smart card reader that communicates with the integrated circuit chip in a smart card using radio frequency (RF) signaling. The PIV contactless interface is standardized by [ISO/IEC 14443]. |\n| Controller (or Control Panel, or Panel) | A device located within the secure area that communicates with multiple PIV Card readers and door actuators, and with the Head End System. The PIV Card readers provide cardholder information to the controller, which it uses to make access control decisions and release door-locking mechanisms. The controller communicates with the Head End System to receive changes in access permissions, report unauthorized access attempts and send audit records and other log information. Most modern controllers can continue to operate properly during periods of time in which communication with the Head End is disrupted and can journal transactions so that they can be reported to the Head End when communication is restored."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n## Multi-Factor Authentication for Criminal Justice Information Systems\n\n## Multi-Factor Authentication for Criminal Justice Information Systems\n\nFisher W, Ajmo J, Umarji S, Dog S, Russell M, Scarfone K (2025) Multi-Factor Authentication for Criminal Justice Information Systems: Implementation Considerations for Protecting Criminal Justice Information. (National Institute of Standards and Technology, Gaithersburg, MD), NIST internal Report (IR) NIST IR 8523. https://doi.org/10.6028/NIST.IR.8523"}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.5 (NIST 3.4.5)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.4.5 SP800161 : SA-8, SA-11(2), SA-11(6), SA-15(5) SP800181 : T0038, T0062; K0005, K0009, K0038, K0039, K0070, K0080, K0119, K0147, K0149, K0151, K0152, K0160, K0161, K0162, K0165, K0297, K0310, K0344, K0362, K0487, K0624; S0006, S0009, S0022, S0078, S0171, S0229, S0248; A0092, A0093, |\n| Design Software to Meet Security Requirements and Mitigate Security Risks (PW."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.4.5", "cmmc_practice_id": "CM.L2-3.4.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n.................. | 50 |\n| 5.3.3 | PR.AC-4: Access Permissions and Authorizations are Managed, Incorporating the Principles of Least Privilege and Separation of Duties .........................\n50 | |\n| 5.3.4 | PR.AC-7: Users, Devices, and Other Assets are Authenticated (e.g., single-factor, multi-factor) Commensurate with the Risk of the Transaction (e.g., Individual Security and Privacy Risks and Other Organizational Risks) | 50 |\n| 5.3.5 | PR.DS-1: Data-at-Rest is Protected......................................................................... | 51 |\n| 5.3.6 | PR.DS-6: Integrity Checking Mechanisms are Used to Verify Software, Firmware, and Information Integrity ..................................................................... | 51 |\n| 5.3.7 | PR.IP-4: Backups of Information are Conducted, Maintained, and Tested............ | 51 |\n| 5.3.8 | PR.MA-1: Maintenance and Repair of Organizational Assets are Performed and Logged, with Approved and Controlled Tools ...................................... | 51 |\n| 5.3.9 | PR.MA-2: Remote Maintenance of Organizational Assets is Approved, Logged, and Performed in a Manner that Prevents Unauthorized Access............... | 51 |\n| 5.3.10 | DE.AE-1: A Baseline of Network Operations and Expected Data Flows for Users Systems is Established and Managed................................................... | and 52 |\n| 5.3.11 | DE.AE-2: Detected Events are Analyzed to Understand Attack Targets And Methods | |"}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 5)"}, {"role": "assistant", "content": "## Table of Contents | | Introduction .........................................................................................................................1 | Introduction .........................................................................................................................1 | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | Consumer Profile of the IoT Core Baseline ......................................................................2 | Consumer Profile of the IoT Core Baseline ......................................................................2 | | 2.2.1."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 2 requirements?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171Ar3\n\n\n\n## NIST Special Publication\n\n## NIST SP 800-171Ar3\n\n## Assessing Security Requirements for Controlled Unclassified Information\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-171Ar3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 8)"}, {"role": "assistant", "content": "ties that have definitively been exploited in the past (e.g., [5] and [6]). However, such lists may not be comprehensive, and prior to this research, metrology did not exist to measure their coverage.\nThis work provides equations to measure probabilities that vulnerabilities have been observed to be exploited in the past. Lists of these probabilities for vulnerabilities are named Likely Exploited Vulnerabilities (LEV) lists. This name highlights such lists' probabilistic nature and to distinguish them from KEV lists (which they do not replace). The LEV probabilities have at least four use cases:\n\n1. measure the expected number and proportion of vulnerabilities, as identified by Common Vulnerability and Exposures (CVE) identifiers, that actors have exploited,\n2. estimate the comprehensiveness of KEV lists,\n3. augment KEV based vulnerability remediation prioritization by identifying higherprobability vulnerabilities that may be missing, and\n4. augment EPSS based vulnerability remediation prioritization by identifying vulnerabilities that may be underscored. LEV accuracy is dependent upon EPSS performance because LEV is calculated from historical EPSS scores. EPSS has published testing indicating that the latest version has a high performance in recall (i.e., coverage) and precision (i.e., efficiency), see Sec. 9. As EPSS performance improves over time (which it is has done significantly over the three versions), LEV performance will improve. While the derivation of the LEV metric is mathematically sound, it inevitably has a margin of error which is currently unknown. Publicly available vulnerability exploitation data is unavailable but necessary to thoroughly test the performance of the LEV metric. The EPSS performance results are not of a form that enables a direct calculation of LEV performance."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.2 (NIST 3.7.2)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.7.2 | by Data Base 3. 3.7.2 Global by Record ; In this scheme, each record is classified according to the highest classification level of the data it contains."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.7.2", "cmmc_practice_id": "MA.L2-3.7.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nRansomware, destructive malware, insider threats, and even honest mistakes present an ongoing threat to organizations that manage data in various forms. Database records and structure, system files, configurations, user files, application code, and customer data are all potential targets of data corruption and destruction.\n\nBased on key points expressed in NISTIR 8050: Executive Technical Workshop on Improving Cybersecurity and Consumer Privacy (2015), the NCCoE is pursuing a series of DI projects to map the Core Functions of the NIST Cybersecurity Framework. This project is centered on the Core Functions of Detect and Respond, which consist of detecting and responding to DI attacks. Compromise can come from malicious websites, targeted emails, insider threats, and honest mistakes. Monitoring solutions should be in place to detect these events. Once detected, swift response to a threat is critical to mitigate the need for recovery action after an event occurs. NCCoE engineers working with a Community of Interest (COI) defined the requirements for this DI project.\n\n- malware\n- insider threats\n- accidents caused by human error\n- compromise of trusted systems"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "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 CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.4.1. 3.4.1 focuses on local agency MFA and Sec. 3.4.1."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "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 AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n3.3.1 PR."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\nlluzzo R, Gupta S, LaSalle C, Lefkovitz N, Regenscheid A (2025) Digital Identity Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63-4.\nhttps://doi.org/10.6028/NIST.SP.800-63-4\n- [4] Temoshok D, Fenton JL, Choong YY, Lefkovitz N, Regenscheid A, Galluzzo R, Richer JP (2025) Digital Identity Guidelines: Authentication and Authenticator Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63B-4. https://doi.org/10.6028/NIST.SP.800-63B-4\n- [5] Regenscheid A, Galluzzo R (2023) Phishing Resistance -Protecting the Keys to Your Kingdom. https://www.nist.gov/blogs/cybersecurity-insights/phishing-resistanceprotecting-keys-your-kingdom\n- [6] Cybersecurity and Infrastructure Security Agency (2025) List of Federal Financial Assistance Programs Funding Emergency Communications. https://www.cisa.gov/safecom/emergency-comms-grants-list\n- [7] Weston D (2024) Microsoft's guidance to help mitigate Kerberoasting. (Microsoft Corporation, Redmond, WA.) Available at https://www.microsoft.com/enus/security/blog/2024/10/11/microsofts-guidance-to-help-mitigate-kerberoasting/\n- [8] Fisher W, Russell M, Umarji S, Scarfone K (2021) Background on Identity Federation Technologies for the Public Safety Community. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Internal Report 8336. https://doi.org/10.6028/NIST.IR.8336-draft\n- [9] Grassi PA, Nadeau EM, Richer JP, Squire SK, Fenton JL, Lefkovitz NB, Danker JM, Choong Y-Y, Greene KK, Theofanos MF (2017) Digital Identity Guidelines: Federation and Assertions. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63C, Includes updates as of March 02, 2020. https://doi.org/10.6028/NIST.SP.800-63C"}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nware development practices, express their secure software development requirements to third-party suppliers using SSDF conventions, and acquire software that meets the practices described in the SSDF.\nUsing the SSDF helps organizations to meet the following secure software development recommendations:\n\n- Can be used by organizations in any sector or community, regardless of size or cybersecurity sophistication\n- Can be applied to software developed to support information technology (IT), industrial control systems (ICS), cyber-physical systems (CPS), or the Internet of Things (IoT)\n- Can be integrated into any existing software development workflow and automated toolchain; should not negatively affect organizations that already have robust secure software development practices in place\n- Makes the practices broadly applicable, not specific to particular technologies, platforms, programming languages, SDLC models, development environments, operating environments, tools, etc. - Can help an organization document its secure software development practices today and define its future target practices as part of its continuous improvement process\n- Can assist an organization currently using a classic software development model in transitioning its secure software development practices for use with a modern software development model (e.g., agile, DevOps)\n- Can assist organizations that are procuring and using software to understand secure software development practices employed by their suppliers"}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to 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 is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.2.6 SP800161 : SA-8 SP800181 : OV-TEA-001, OV-TEA-002; T0030, T0073, T0320; K0204, K0208, K0220, K0226, K0243, K0245, K0252; S0100, S0101; A0004, A0057 |\n\n5 Provenance is 'the chronology of the origin, development, ownership, location, and changes to a system or system component and associated data."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.2.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 is CMMC practice IR.L2-3.6.2 (NIST 3.6.2)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.6.2 Kernelized Secure Data Management System | 3. 3.6.2 Kernelized Secure Data Management System; lb our knowledge, there has been relatively little research performed to date on the design of a kernelized secure data management system [1,2,7]."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.6.2", "cmmc_practice_id": "IR.L2-3.6.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| 1 | Summary.............................................................................................1 | Summary.............................................................................................1 | Summary.............................................................................................1 | |-----|---------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Challenge.......................................................................................................................2 | | | | 1.2 | Solution..........................................................................................................................3 | | | | 1.3 | Benefits..........................................................................................................................4 | | | 2 | How to Use This Guide.........................................................................4 | How to Use This Guide.........................................................................4 | | | | 2.1 | Typographic Conventions..............................................................................................5 | | | 3 | Approach.............................................................................................6 | Approach.............................................................................................6 | | | | 3.1 | Audience........................................................................................................................6 | | | | 3.2 | Scope .............................................................................................................................6 | | | | | 3.2.1 Scenario 1: Creation of Verifiable Platform | Artifacts ..................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Machine Learning for Access Control Policy Verification provide? (Part 2)"}, {"role": "assistant", "content": "and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Email: ir8360-comments@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nAccess control policy verification ensures that there are no faults within the policy that leak or block access privileges. As a software test, access control policy verification relies on methods such as model proof, data structure, system simulation, and test oracle to verify that the policy logic functions as expected."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 additional guidance does Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs provide? (Part 6)"}, {"role": "assistant", "content": "|\n| 5.2.2.\nChallenges ........................................................................................................... | 5.2.2. Challenges ........................................................................................................... | 16 |\n| 5.3. Education and Awareness ......................................................................................... | 5.3. Education and Awareness ......................................................................................... | 24 |\n| 5.4. Trust of NIST and Governments............................................................................... | 5.4. Trust of NIST and Governments............................................................................... | 27 |\n| Summary ........................................................................................................................ | Summary ........................................................................................................................"}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n- Participants frequently collaborated with other groups in the organization to augment and inform their programs, most commonly other cybersecurity and IT teams, but also with others such as human resources and communications.\n- Programs used a variety of government and non-government resources to inform security awareness topics and approaches, e.g., workforce feedback, organizational security incident trends, news stories, and security mailing lists.\n- While only 27% of survey participants expressed challenges collaborating or sharing information with other federal security awareness professionals, focus group participants frequently highlighted their desire for increased collaboration. For example, they suggested the creation of a central repository of awareness materials, ongoing working groups, or realtime online forums.\n\nOrganizations often held events or sent out additional communications during the month of October, which has been designated as Cybersecurity Awareness Month (previously called National Cybersecurity Awareness Month) [CISA].\n\n'Balancing communications to keep people aware without kind of coming off as spam by producing too much material, which can get to a point where nobody's even reading it anymore.' (D03)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nThe qualities and benefits of the complete PIV System can only be achieved if its implementation is supported by bi-directional communications infrastructure used in modern PACS. The following areas have significant influence on the rate at which the complete PIV System integration can be achieved by PACS, and should therefore be supported by PACS upgrades and new PACS procurements:\n\nWhen a PIV Card is presented to a contactless reader at an access point, the reader supplies power to the PIV Card through inductive coupling and a series of messages is exchanged between the PIV Card and reader using radio frequency (RF) communications. A sniffer is a passive receiver that does not supply power to the smart card. A sniffer can operate at greater distance than a skimmer (sniffing at a distance of about 10 m has been reported), because a legitimate reader powers the PIV Card at the nominal distance of a few centimeters, while the sniffer's RF receiver is farther away. Potentially, a sniffer could capture the entire message transaction between the contactless reader and the PIV Card.\n\nThe PIV Authentication key, as defined in [FIPS201], is a mandatory asymmetric key present on the PIV Card. A PACS that performs public key cryptography-based authentication with the PIV Authentication key uses the PKI-AUTH authentication mechanism. Use of PKI-AUTH provides two-factor authentication, since the cardholder must present the card (something you have) and either enter a PIN (something you know) or submit a fingerprint (something you are) to unlock the card in order to successfully authenticate."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n|\n| Federal Vulnerability Disclosure Coordination Body ....................................................\n| 6 | |\n| Preparation................................................................................................................. | 7 | |\n| 2.1.1. Create Source Vulnerability | Report Receipt Capability............................................. 7 | |\n| 2.1.2. Determine Scope and Obtain Contacts .................................................................... | 8 | |\n| 2.1.3. Develop Technical Analysis Capability ....................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "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 are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n3.1.4. 3.1.4."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "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 guidance does Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide?"}, {"role": "assistant", "content": "## NIST Cybersecurity White Paper NIST CSWP 41\n\n## Likely Exploited Vulnerabilities\n\nA Proposed Metric for Vulnerability Exploitation Probability\n\nPeter Mell*\n\nComputer Security Division Information Technology Laboratory *Former NIST employee; all work for this publication was done while at NIST. Jonathan Spring Cybersecurity Division C ybersecurity and Infrastructure Security Agency\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.CSWP.41\n\nMay 19, 2025\n\n\n\n\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements\n\nNIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-04-18\n\n## How to Cite this NIST Technical Series Publication:\n\nMell P, Spring J (2025) Likely Exploited Vulnerabilities: A Proposed Metric for Vulnerability Exploitation Probability. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 41. https://doi.org/10.6028/NIST.CSWP.41\n\n## Author ORCID iDs\n\nPeter Mell: 0000-0003-2938-897X Jonathan Spring: 0000-0001-9356-219X\n\n## Contact Information\n\nSecureByDesign@cisa.dhs.gov\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/publications/cswp, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA)."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Guidelines on Mobile Device Forensics:\n\nciencedirect.com>. - [Kat10] Eric Katz, A Field Test of Mobile Phone Shielding Devices, 2010, College of Technology Masters Thesis, Paper 33, <URL: http://docs.lib.purdue.eud/techmasters/33>.\n- [Kni10] Ronald van der Knijff, Chapter 8: Embedded Systems Analysis, Handbook of Digital Forensics and Investigation , Edited by Eoghan Casey, Elsevier Academic Press, 2010. - [Man08] Kevin Mansell, Darren Lole, Fiona Litchfield, Recovering Deleted Data From Fat Partitions Within Mobile Phone Handsets Using Traditional Imaging Techniques, F3 Annual Conference, November 11-13, 2008, <URL: http://www.controlf.net/content/uploads/MANSELL-Imaging-FAT-Partitions-onPhone-Handsets-Feb-09.pdf>. - [Mcc05] Paul McCarthy, Forensic Analysis of Mobile devices, BS CIS Thesis, University of South Australia, School of Computer and Information Science, Mawson Lakes, October 2005."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "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 Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.4.2. 3.4.2. 3.4.2), and configuration using the macOS Security Compliance Tool (Section 3."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\nVulnerabilities are discovered by a variety of sources. Developers of software may find security bugs in already deployed code. Security researchers and penetration testers may find vulnerabilities by scanning or manually testing software and accessible systems (following published rules of behavior). While identifying an issue, users of systems may stumble across a vulnerability. Malicious actors may seek out unknown or unpublished vulnerabilities and use them in malware. Evidence of these attacks may then be discovered and analyzed by security experts, resulting in an identified vulnerability being reported. Regardless of who finds these vulnerabilities, it is critical that they are reported so that the owners of vulnerable software and systems can resolve or identify ways to mitigate the reported vulnerabilities. In many cases, owners should issue advisories to notify users of any actions to be taken (e.g., patches to be installed) or of potential damage to systems (i.e., potential consequences of the vulnerability having existed). The internal policy governs the rules and procedures for handling, coordinating, and resolving received vulnerability reports; the mechanisms used to track the reports; and the expectations for communication with reporters and other stakeholders. Expected response and remediation timelines for handling vulnerability reports should be specified, as well as a procedure to follow when working with the FCB to publish advisories and distribute remediations (e.g., patches) to users of vulnerable agency software. The policy may also specify the levels of testing required for the remediation of agency systems and any remediation hurdles that may exist (e.g., for legacy systems). If a VDPO chooses to conduct its own vulnerability research and testing, it should forward all pertinent information to its FCB member for inclusion in an FCB vulnerability report database."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.1.2. 3.1.2): A secret determined by the claimant by looking up a\n\nprompted value in a list held by the subscriber\n\n• Out-of-band device (Sec. 3.1.2)\n\n• Out-of-band device (Sec."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "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 is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.2.2 | Identify Resource Requirements ... 3.2.2 Identify Resource Requirements\n\nRealistic recovery efforts require a thorough evaluation of the resources required to resume mission/business processes as quickly as possible."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.3.1. 3.3.1."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ordered t-way Combinations for Testing State-based Systems provide? (Part 4)"}, {"role": "assistant", "content": "coverage measures provide an effective method for quantifying the thoroughness of test input values [26] . A number of measures have been defined for the coverage of (static) input value combinations.\nFor example, with four binary variables, there are a total of 2 2 * C(4,2) = 24 possible settings of the four variables taken two at a time. If a test set includes tests that cover 19 of the 24, the simple combinatorial coverage is 19/24 = 0.79. These measures quantify the degree to which input values cover the potential space of parameter value combinations without regard for the order in which these inputs occur in a test set or in normal operations. However, if a system state is affected or determined by the order of inputs, even thorough coverage of the input space may not detect some failure conditions. Thus, it is desirable to supplement measures of input space coverage with measures of the input value combination ordering. ## 2 Related Work\n\nCombinatorial aspects of input ordering have been studied in the context of event sequences . Sequence covering arrays (SCAs) were introduced in [1] and [2] and further developed in [3] , [4] , [5] , [7] , [8] [9] , [10] , and [11] . Definition. A sequence covering array [2] , SCA( N, S, t ) is an N x S matrix where entries are from a finite set S of s symbols, such that every t -way permutation of symbols from S occurs in at least one row. The t symbols in the permutation are not required to be adjacent. For example, Fig. 1 shows an event sequence a *→ b *→ c in test 1 and an event sequence of d * → c * → a in test 3, where x *→ y denotes x is eventually followed by y , with possible interleaving. Note that the event sequence array has sequences of events in each row . Event sequences are made up of a value in a column followed by values in columns to the right. Fig. 1."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nquirements should include hardware and software specifications as well as interconnections and data flow documents that will assist the system owner in identifying the types of ISM used in the system.\nSome ISM support enhanced interface commands for sanitization, which may make sanitization easier, faster, and more effective. The decision may be even more fundamental because effective sanitization procedures may not yet have been determined for emerging ISM types. Without an effective command or interface-based sanitization technique, the ISM may have to be destroyed. In that event, the ISM cannot be reused by other organizations that could have benefited from receiving the repurposed ISM."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nThe NIST Internet of Things (IoT) Cybersecurity Program has defined an IoT cybersecurity baseline for both technical capabilities and non-technical capabilities. Technical capabilities are those provided by digital products using software and hardware, such as Over-The-Air software update mechanisms or data encryption. Non-technical capabilities are those provided by organizations in support of digital product cybersecurity. Cybersecurity education and awareness is an example of a non-technical cybersecurity capability. The term 'education and awareness' is defined as 'The ability for the manufacturer and/or supporting entity to create awareness of and educate customers and others in the IoT device ecosystem about cybersecurity related information, considerations, features, etc. of the IoT device.' [1] There are many ways this capability can be implemented, but some examples include:\n\nThis section presents observations and takeaways from the event and teams' designs that were generated after the event and can inform future research and standardization efforts. All three teams identified different approaches in their plans, showing the wide range of tools and concepts that can be used for cybersecurity education and awareness for IoT products. As teams discussed and identified their plans, they found that standardization of available approaches and selection of appropriate approaches could help increase the speed of material development. All teams deeply considered the expected customers of each product to ensure awareness and education approaches were adequately tailored. Teams indicated that any standardization effort should similarly be human-centric and consider the spectrum of potential users of a given application or product. Unlike some areas of cybersecurity (e.g., encryption) which require limited human interaction, particularly with users, education and awareness addresses the human-in-the-loop and so depends, in large part, on human-factors for efficacy."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n.............................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1.\nBaseline Security ........................................................................................................................11 |\n| 3.2.2. Controls for Interacting With SCM Systems...............................................................................12 |\n| 4. CI/CD Pipelines -Background, Security Goals, and Entities to be Trusted .....................................13 |\n| 5. Integrating SSC Security Into CI/CD Pipelines.................................................................................15 |\n| 5.1.1. Secure Build................................................................................................................................16 |\n| 5.1.2. Secure Pull-Push Operations on Repositories............................................................................17 |\n| 5.1.3. Integrity of Evidence Generation During Software Updates......................................................18 |\n| 5.1.4. Secure Code Commits ................................................................................................................19 |"}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IoT Device Cybersecurity Capability Core Baseline provide? (Part 6)"}, {"role": "assistant", "content": "s that protect devices as well as device data, systems, and ecosystems. The concept of a baseline in any context requires careful consideration; security capabilities for IoT devices are no exception.\nThe core baseline has been derived from researching common cybersecurity risk management approaches and commonly used capabilities for addressing cybersecurity risks to IoT devices, which were refined and validated using a collaborative public-private process to incorporate all viewpoints. Multiple requests for comment were issued, and multiple workshops and roundtables were held. NIST is committed to an open and transparent process that facilitates stakeholder feedback and iterative improvement. These capabilities were developed in the context of NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers [2], which discusses considerations for manufacturers to help guide them in choosing and implementing the device cybersecurity capabilities their IoT devices will provide. NISTIR 8259 also defines terminology and concepts that provide critical context for understanding device cybersecurity capabilities as one part of the entire IoT cybersecurity ecosystem. Thus, though both NISTIR 8259 and this publication have manufacturers as the intended audience, the considerations and capabilities discussed across the two publications can be used by manufacturers, integrators, or consumers. For more information on how these capabilities can be incorporated into a manufacturer's development processes, see NISTIR 8259. Other organizations can use the core baseline in the context that is available and appropriate to them. Regardless of an organization's role, this baseline is intended to give all organizations a starting point for IoT device cybersecurity risk management, but the implementation of all capabilities is not considered mandatory."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nGuide to Auditing for Controls and Security: A System Development Life Cycle Approach\n\nm T he National Bureau of Standards' was established by an act of Congress on March 3, 1901. The Bureau's overall goal is to strengthen and advance the nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research to assure international competitiveness and leadership of U.S. industry, science arid technology. NBS work involves development and transfer of measurements, standards and related science and technology, in support of continually improving U.S. productivity, product quality and reliability, innovation and underlying science and engineering. The Bureau's technical work is performed by the National Measurement Laboratory, the National Engineering Laboratory, the Institute for Computer Sciences and Technology, and the Institute for Materials Science and Engineering.\n\nConducts research and provides scientific and technical services to aid Federal agencies in the selection, acquisition, application, and use of computer technology to improve effectiveness and economy in Government operations in accordance with Public Law 89-306 (40 U.S.C. 759), relevant Executive Orders, and other directives; carries out this mission by managing the Federal Information Processing Standards Program, developing Federal ADP standards guidelines, cind managing Federal participation in ADP voluntary standardization activities; provides scientific and technological advisory services and assistance to Federal agencies; and provides the technical foundation for computer-related policies of the Federal Government. The Institute consists of the following divisions:"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n| Platform Manifest Correlation System.......................................................................\n| 27 |\n| | 4.3.4 | Eclypsium Analytic Platform....................................................................................... | 28 |\n| 4.4 | Computing Devices......................................................................................................31 | Computing Devices......................................................................................................31 | |\n| | 4.4.1 | HP Inc.......................................................................................................................... | 31 |\n| | 4.4.2 | Dell Technologies........................................................................................................ | 33 |\n| | 4.4.3 | Intel............................................................................................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 8)"}, {"role": "assistant", "content": "ederal Agencies\n\n- The National Archives and Records Administration (NARA) , per 32 CFR Part 2002 \"Controlled Unclassified Information,\" determines what CUI is and lists CUI types at archives.gov/cui.\n- NIST is responsible for developing and publishing the security requirements for the protection of CUI. How requirements are mandated, and any compliance issues related to nonfederal implementation of SP 800-171, are the responsibility of the federal agency requiring its use , as expressed in a specific contract or agreement. ## Additional NIST Resources\n\n- NIST's Protecting CUI Frequently Asked Questions\n- Changes Between SP 800-171 Rev. 2 and Rev. 3 (.xlsx)\n- The NIST Cybersecurity and Privacy Reference Tool (CPRT) provides online, interactive versions of the updated security requirements in SP 800-171, Revision 3 and the updated assessment procedures in SP 800-171A, Revision 3\n- Event Recording: ' CUI Security Requirements Workshop ,' which provides a general overview of SP 800 -171 and SP 800-171A\n- NIST Small Business Cybersecurity Corner\n\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n\n\n## What to Expect\n\nThe following pages delve deeper into the SP 800-171 R3 publication to provide more details for those responsible for implementing the requirements 3 . The following pages cover:\n\n\n\nPage 8: Key differences between SP 800-171 R2 and R3. Pages 9-10: General tips for getting started. Pages 11-28: Tips for getting started, broken out by Control Family. 3 We provide links to non-NIST sites throughout this publication because they may have information of interest to readers. NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n## Contingency Planning Guide for Federal Information Systems\n\n## Contingency Planning Guide for Federal Information Systems\n\nThere are references in this publication to documents currently under development by NIST in accordance with responsibilities assigned to NIST under the Federal Information Security Management Act of 2002. The methodologies in this document may be used even before the completion of such companion documents. Thus, until such time as each document is completed, current requirements, guidelines, and procedures (where they exist) remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new documents by NIST. Individuals are also encouraged to review the public draft documents and offer their comments to NIST."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\nThe verifier SHOULD determine the performance and integrity of the sensor and its\nassociated endpoint. This increases the likelihood of detecting injection attacks due to\ncompromised endpoints, sensor emulators, and similar threats. Acceptable methods for\nmaking this determination include:\n\n• The provenance (e.g., manufacturer or supplier certification), health, and integrity\n\nMalicious code on the endpoint\nproxies allows remote access to a\nconnected authenticator without\nthe subscriber’s consent."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to 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 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nAn internal audit finds multiple failures on the part of the purchasing department, the IT department, and the Information Security group to have in place measures to ensure the provenance of the equipment and the secure deployment of devices on the network. | Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | Cybersecurity Framework v1.1 | SP 800- | Security |\n|--------------------------------|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------------------|\n| Function | Category | Subcategory | 53 R5 | Characteristics Addressed |\n| Identify (ID) | Supply Chain Risk Management (ID.SC) | ID.SC-4: Suppliers and third-party partners are routinely assessed using audits, test results, or other forms of evaluations to confirm they are meeting their contractual obligations. | AU-6 | 5 |\n| | Asset Management (ID.AM) | ID.AM-1: Physical devices and systems within the organization are inventoried. | CM-8 | 4 |\n| Protect (PR) | Identity Management, Authentication and Access Control (PR.AC) | PR.AC-6: Identities are proofed and bound to credentials and asserted in interactions."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs:\n\n| | Introduction ..................................................................................................................... | Introduction ..................................................................................................................... |\n|------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology.......................................................................................................... 2 | Background: NIST Cryptographic Standards and Testing/Validation Programs ... 1 Methodology.........................................................................................................."}], "metadata": {"source": "Organizational Views of NIST Cryptographic Standards and Testing and Validation Programs", "cmmc_level": "all", "cmmc_domain": "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 Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| 3.4.5.1.1 Mission Impact/Strategic Value/Organization | 55 | | | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | (Business) Criticality and Sensitivity Factors 3.4.5.2 Level II: | | | | | | | 56 | | | 3.4.5.2.1 | 3.4.5.2.1 | System Size/Scale/Complexity | 56 | | | 3.4.5.2.2 | 3.4.5.2.2 | System Environment/Stability | 57 | | | 3.4.5.2.3 | 3.4.5.2.3 | Reliability/Integrity | 58 | | | 3.4.5.2.4 | 3.4.5.2.4 | Technology Integration | 59 | | 3.5 | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | RISK SCORING -- APPLICATION OF THE WORK PRIORITY SCHEME | 59 | | | 3.5.1 Implementation of the Scheme | 3.5.1 Implementation of the Scheme | 3.5.1 Implementation of the Scheme | 59 | | | 3.5.2 | A Simple Scoring Approach | A Simple Scoring Approach | 60 | | | 3.5.3 | A Detailed Scoring Approach | A Detailed Scoring Approach | 60 | | | 3.5.4 | Discretionary Audits | Discretionary Audits | 60 | | 3.6 | USES OF THE WORK PRIORITY SCHEME | USES"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "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 Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide? (Part 7)"}, {"role": "assistant", "content": "considerations among Information Technology (IT), Internet of Things (IoT), Operational Technology (OT), and Industrial Internet of Things (IIoT)\n- Identify insights, considerations, approaches, etc.\nfor IoT based on the NIST Privacy Framework, NIST Cyber Physical Systems/IoT Framework, NIST Cybersecurity Framework 2.0, and the NIST Secure Software Development Framework. - Incorporate lessons learned and techniques developed in the execution of several IoTrelated National Cybersecurity Center of Excellence (NCCoE) projects. - Address emerging connected product technologies more directly (i.e., Immersive Tech, Artificial Intelligence). - Discuss any relationship that may exist between the repairability of connected products and cybersecurity. - Provide guidelines on balancing cybersecurity with device support considerations, especially when there is a significant mismatch between the expected end of support of the IT components and the end of life of the mechanical components of the connected products. NIST held the publicly available hybrid workshop with virtual morning plenary sessions and afternoon in-person discussion sessions as detailed in the table below."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n. . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . .\n. . . | 14 |\n| 3.4. | SIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 16 |\n| 4. Conclusion . . | . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| References . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms | . | 26 |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | 2 |\n| Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | 4 |\n| Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | 6 |\n| Table 4. Performance of HQC in thousands of cycles on x86_64 [1] . . . | Table 4."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| Example 1 : Appoint a single leader or leadership team to be responsible for the entire secure software development process, including being accountable for releasing software to production and delegating responsibilities as appropriate. Example 2 : Increase authorizing officials' awareness of the risks of developing software without integrating security throughout the development life cycle and the risk mitigation provided by secure development practices. Example 3 : Assist upper management in incorporating secure development support into their communications with personnel with development-related roles and responsibilities. Example 4 : Educate all personnel with development-related roles and responsibilities on upper management's commitment to secure development and the importance of secure development to the organization. | BSIMM : SM1.3, SM2.7, CP2.5 EO14028 : 4e(ix) NISTCSF : ID.RM-1, ID.SC-1 OWASPSAMM : SM1.A PCISSLC : 1.1 SP800181 : T0001, T0004 |\n| Implement Supporting Toolchains (PO.3) : Use automation to reduce human effort and improve the accuracy, reproducibility, usability, and comprehensiveness of security practices throughout the SDLC, as well as provide a way to document and demonstrate the use of these practices."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| Chapter 1."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "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 Overview and Considerations of Access Control Based on Attribute Encryption provide?"}, {"role": "assistant", "content": "\n\n## NIST Internal Report NIST IR 8450-upd1\n\n## Overview and Considerations of Access Control Based on Attribute Encryption\n\nVincent C. Hu\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8450-upd1\n\n\n\n## NIST Internal Report NIST IR 8450-upd1\n\n## Overview and Considerations of Access Control Based on Attribute Encryption\n\nVincent C. Hu Computer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8450-upd1\n\nSeptember 2023 INCLUDES UPDATES AS OF 12-20-2023; SEE APPENDIX A\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nLaurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Security Assessment?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\nr example, the risk profile of the device can be obtained through an out-of-the-box posture check (risk of the device [28]) with or without integrating with an endpoint protection tool for the device.\nOther crucial information (provided by telemetry data) needed to assess the security status of the endpoint devices [29] include (a) device support label (the device is managed or corporate-owned) and (b) device posture information (whether it has been compromised). All of these factors go into a policy evaluation for determining the level of trust and must be channeled into authentication and monitoring decisions [30]. 3. Information about real-time contextual data - Date, time, and geolocation at which the access request occurs\n4. Information about IT services (e.g., app, data) being accessed\n5. Information about the security of the environment hosting the IT services being accessed"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide? (Part 5)"}, {"role": "assistant", "content": "ersecurity risk management. |\n| 7 | There is an increased awareness for evolving cybersecurity responsibilities across the players of the IoT ecosystem from manufacturers to users of the ecosystem.\n|\n\n## About the NIST Cybersecurity for the Internet of Things Program\n\nThe mission of the NIST Cybersecurity for the Internet of Things (IoT) program is to cultivate trust in the IoT and foster an environment that enables innovation on a global scale through standards, guidelines, and related tools. The Cybersecurity for IoT program supports the development and application of standards, guidelines, and related tools to improve the cybersecurity of connected devices and the environments in which they are deployed. The program collaborates with stakeholders across government, industry, international bodies, and academia. ## Background\n\nIn May 2020, NIST published Foundational Cybersecurity Activities for IoT Device Manufacturers (NIST IR 8259), which describes recommended cybersecurity activities that manufacturers should consider integrating into their product development and support lifecycle. These foundational cybersecurity activities can help manufacturers lessen the cybersecurity-related efforts needed by customers, which in turn can reduce the prevalence and severity of IoT device compromises and the attacks performed using compromised devices. Over time, the NIST volume of work has built upon the concepts introduced in the NIST IR 8259 series to introduce technical, IoT Device Cybersecurity Capability Core Baseline (NIST IR 8259A) and nontechnical, IoT Non-Technical Supporting Capability Core Baseline (NIST IR 8259B) concepts to help manufacturers and customers consider the cybersecurity of IoT devices."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 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 Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 4)"}, {"role": "assistant", "content": "DF) version 1.1 by adding practices, tasks, recommendations, considerations, notes, and informative references that are specific to AI model development throughout the software development life cycle.\nThese additions are documented in the form of an SSDF Community Profile to support Executive Order (EO) 14110, Safe, Secure, and Trustworthy Development and Use of Artificial Intelligence , which tasked NIST with 'developing a companion resource to the [SSDF] to incorporate secure development practices for generative AI and for dual-use foundation models.' This Community Profile is intended to be useful to the producers of AI models, the producers of AI systems that use those models, and the acquirers of those AI systems. This Profile should be used in conjunction with NIST Special Publication (SP) 800-218, Secure Software Development Framework (SSDF) Version 1.1: Recommendations for Mitigating the Risk of Software Vulnerabilities. ## Keywords\n\nartificial intelligence; artificial intelligence model; cybersecurity risk management; generative artificial intelligence; secure software development; Secure Software Development Framework (SSDF); software acquisition; software development; software 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. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Ordered t-way Combinations for Testing State-based Systems provide? (Part 2)"}, {"role": "assistant", "content": "lication of the results to verify and test state-based systems. ## Keywords\n\ncombinatorial coverage; combinatorial methods; combinatorial testing; software testing; structural coverage; test coverage.\n## Disclaimer\n\nAny mention of commercial products or reference to commercial organizations is for information only; it does not imply recommendation or endorsement by NIST, nor does it imply that the products mentioned are necessarily the best available for the purpose. ## Additional Information\n\nFor additional information on NIST's Cybersecurity programs, projects and publications, visit the Computer Security Resource Center. Information on other efforts at NIST and in the Information Technology Laboratory (ITL) is also available. cfdwp@nist.gov\n\nSubmit comments on this publication 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\n## 1 Introduction\n\nVulnerability and fault detection often depend on the specific order of inputs that establish states which eventually lead to a failure. That is, many software processes are not deterministic functions where an input produces the same output whenever the process is invoked irrespective of previous invocations. This is particularly true of real-time systems, which are designed to run continuously, maintain states, and respond to a changing series of inputs. Such systems are typically driven by a loop function that accepts input values, processes and responds to those inputs, and updates its current state. Examples include network protocols and data servers. The system state may change, depending on input, and the system may subsequently respond differently to the same input. That is, the response of the process to a particular set of input values may depend on its current state, such as whether a communication protocol is in a listen or connection-open state."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/66/r2/final, including related content, potential updates, and document history. NIST Special Publication (SP) 800-66 aims to help educate readers about the security standards included in the HIPAA Security Rule and assist regulated entities in their implementation of the Security Rule. It includes a brief overview of the HIPAA Security Rule, provides guidance for regulated entities in assessing and managing risk to ePHI, identifies typical activities that a additional resources that regulated entities may find useful when implementing the Security regulated entity should consider when implementing an information security program, and lists Rule. This publication is intended to aid understanding of the HIPAA Security Rule and does not supplement, replace, modify, or supersede the Security Rule itself. Anyone seeking clarifications on the HIPAA Security Rule should contact the U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR). For general HIPAA Security Rule information, visit the HHS Security Rule website. 4 The NIST publications available as of the publication date of SP 800-66r2 (Revision 2) were used in preparing this document. NIST frequently publishes new standards and guidelines or updates existing publications that may also serve as useful references. To remain current with the latest\n\n1. Security Standards: General Rules - Includes the general requirements that all regulated entities must meet, establishes flexibility of approach, identifies standards and implementation specifications (both required and addressable), outlines decisions that a regulated entity must make regarding addressable implementation specifications, and requires the maintenance of security measures to continue reasonable and appropriate protection of ePHI\n2."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "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 Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide?"}, {"role": "assistant", "content": "\n\n## NIST Internal Report NIST IR 8558\n\n## Report on the Design-A-Thon: Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness\n\nMichael Fagan Julie Haney Daniel Eliot Barbara Cuthill Kristina Rigopoulos\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8558\n\n\n\n## NIST Internal Report NIST IR 8558\n\n## Report on the Design-A-Thon: Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness\n\nMichael Fagan Daniel Eliot Barbara Cuthill Kristina Rigopoulos\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nJulie Haney Information Access Division Information Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8558\n\nSeptember 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Guide for Developing Security Plans for Federal Information Systems:\n\nrisk and local conditions including organization-specific security requirements, specific threat information, costbenefit analyses, the availability of compensating controls, or special circumstances.\nCommon security controls, which is one of the tailoring considerations, must be identified prior to system security plan preparation in order to identity those controls covered at the agency level, which are not system-specific. These common security controls can then be incorporated into the system security plan by reference."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "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 Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 7)"}, {"role": "assistant", "content": ".........................31 |\n| Appendix A. Technology Components Relevant to MFA for CJIS Access .............................................32 |\n\n| Appendix B.\nFederated Identity Architectures...................................................................................33 |\n|------------------------------------------------------------------------------------------------------------------------------------------------|\n| B.4.1. Both CAD/RMS Web App& IdP at the State Agency .................................................................37 |\n| B.4.2. CAD Thick Client at the County with the IdP at the State Agency .............................................41 |\n| B.4.3. Both the CAD/RMS Web App and IdP at a County Agency........................................................45 |\n| B.4.4. Integrations with OAuth 2.0 and OIDC.......................................................................................46 |\n| B.5.1. VPN Integration with Kerberos but without Federation............................................................50 |\n| B.5.2. VPN Integration with an Identity Provider.................................................................................51 |\n| Appendix C. Questions to Ask Your Technology Vendors...................................................................53 |\n| Appendix D. List of Symbols, Abbreviations, and Acronyms...............................................................61 |\n| List of Tables |\n| Table 1."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\nThe authoritative source of information regarding the provenance and integrity of the components provides a strong basis for trust in a computing device. Hardware roots of trust are the foundation upon which the computing system's trust model is built, forming the basis in hardware for providing one or more security-specific functions for the system. Incorporating hardware roots of trust into acquisition and lifecycle management processes enables organizations to achieve better visibility into supply chain attacks and to detect advanced persistent threats and other attacks. By leveraging hardware roots of trust capabilities as a computing device traverses the supply chain, we can maintain trust in the computing device throughout its operational lifecycle."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector provide?"}, {"role": "assistant", "content": "## NIST SPECIAL PUBLICATION 1800-10\n\n## Protecting Information and System Integrity in Industrial Control System Environments: Cybersecurity for the Manufacturing Sector\n\nIncludes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C)\n\nMichael Powell Joseph Brule Michael Pease Keith Stouffer CheeYee Tang Timothy Zimmerman Chelsea Deane John Hoyt Mary Raguso Aslam Sherule Kangmin Zheng Matthew Zopf\n\nFINAL\n\nMarch 2022\n\nThis publication is available free of charge from https://doi.org/10.6028/NIST.SP.1800-10\n\nThe first draft of this publication is available free of charge from https://www.nccoe.nist.gov/publications/practice-guide/protecting-information-and-systemintegrity-industrial-control-system-draft\n\n\n\n## NIST SPECIAL PUBLICATION 1800-10\n\n## Protecting Information and System Integrity in Industrial Control System Environments: Cybersecurity for the Manufacturing Sector\n\nIncludes Executive Summary (A); Approach, Architecture, and Security Characteristics (B); and How-To Guides (C)\n\nMichael Powell National Cybersecurity Center of Excellence National Institute of Standards and Technology\n\nMichael Pease Keith Stouffer CheeYee Tang Timothy Zimmerman Engineering Laboratory National Institute of Standards and Technology\n\nJoe Brule Chelsea Deane John Hoyt Mary Raguso Aslam Sherule Kangmin Zheng The MITRE Corporation McLean, Virginia\n\nMatthew Zopf Strativia Largo, Maryland\n\nFINAL\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nJames K."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n4. Ineffective Security Practices for the AppHcation - Inadequate manual checks and controls to ensure correct processing by the ADP system, or negligence by those responsible for carrying out these checks, result in many vulnerabilities. 5. Procedural Errors Within the ADP Facility - Both errors and intentional acts committed by the ADP operations staff may result in improper operational procedures, lapsed controls, and losses in storage media and output. 6. Program Errors - Applications programs should be developed in an environment that requires and supports complete, correct, and consistent program design, good programming practices, adequate testing, review, and documentation, and proper maintenance procedures. Although programs developed in such an environment may still contain undetected errors, programs not developed in this manner will probably be rife with errors. Additionally, programmers can deliberately modify programs to produce undesirable side effects or they can misuse the programs they are in charge of. 7. Operating System Flaws - Design and implementation errors, system generation and maintenance problems, and deliberate penetrations resulting in modifications to the operating system can produce undesirable effects in the application system. Flaws in the operating system are often difficult to prevent and detect. 8. Communications System Failure - Information being routed from one location to another over communication lines is vulnerable to accidental failures and to intentional interception and modification by unauthorized parties. 8 Development Phase-The Institute for Computer Sciences and Technology at the National Bureau of Standards (ICST/NBS), in structuring a framework within which the development of software could be discussed, identified a Development Phase including four stages -definition, design, programming, and testing. These are represented by Phases II-V described above."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "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 Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 9)"}, {"role": "assistant", "content": "....................20 |\n| Fig. 11. Common architecture for implementing MFA directly with state portal.................................22 |\n| Fig. 12.\nCommon architecture for implementing MFA at state agency identity service. ......................23 |\n\n| Fig. 13. State application dashboard. ................................................................................................24 |\n|----------------------------------------------------------------------------------------------------------------------------------------------|\n| Fig. 14. VPN with MFA is not integrated with the CJIS application......................................................25 |\n| Fig. 15. Integrating MFA for a VPN with Kerberos..............................................................................26 |\n| Fig. 16. Integrating MFA for a VPN with federation. ..........................................................................28 |\n| Fig. 17. Federation in a message switch use case...............................................................................34 |\n| Fig. 18. Web app and IdP at state (SAML proxy). ...............................................................................38 |\n| Fig. 19. Web app and IdP at state (WS-Trust). ...................................................................................40 |\n| Fig. 20. Thick client CAD/RMS and Proxy IdP at county, state IdP.......................................................42 |\n| Fig. 21. Thick client CAD/RMS at county, state IdP (WS-Trust). ..........................................................44 |\n| Fig. 22. CAD/RMS web app and IdP at county (SAML proxy). .............................................................45 |\n| Fig. 23. CAD/RMS web app and IdP at state - OIDC and OAuth 2.0."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\nAlthough the integration of IT and OT networks is helping manufacturers boost productivity and gain efficiencies, it has also provided malicious actors, including nation states, common criminals, and insider threats a fertile landscape where they can exploit cybersecurity vulnerabilities to compromise the integrity of ICS and ICS data to reach their end goal. The motivations behind these attacks can range from degrading manufacturing capabilities to financial gain, and causing reputational harm.\n\nOnce malicious actors gain access, they can harm an organization by compromising data or system integrity, hold ICS and/or OT systems ransom, damage ICS machinery, or cause physical injury to workers. The statistics bear this out. The X-Force Threat Intelligence Index 2021 (ibm.com) stated that manufacturing was the second-most-attacked industry in 2020, up from eighth place in 2019.\n\nThe NCCoE, in conjunction with the NIST EL, collaborated with cybersecurity technology providers to develop and implement example solutions that demonstrate how manufacturing organizations can protect the integrity of their data from destructive malware, insider threats, and unauthorized software within manufacturing environments that rely on ICS."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "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 Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 9)"}, {"role": "assistant", "content": ".............................................................79 |\n| 5.5.1.\nPolicies and Procedures (§ 164.316(a))......................................................................................81 |\n| 5.5.2. Documentation (§ 164.316(b))...................................................................................................83 |\n| References.......................................................................................................................................85 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................87 |\n| Appendix B. Glossary .......................................................................................................................91 |\n| Appendix C. Risk Assessment Tables.................................................................................................96 |\n| Appendix D. Security Rule Standards and Implementation Specifications Crosswalk........................105 |\n| Appendix E."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\n- RBT assignment: There is no standard way that organizations determine which employees should be assigned RBT. Some use the National Initiative for Cybersecurity Education (NICE) Workforce Framework for Cybersecurity (NICE Framework) as a guide, but others leave decisions up to the office of the Chief Information Officer (CIO) or even individual supervisors. - RBT content: About two-thirds of surveyed participants said that their organizations create at least some RBT content on their own, which could be resource-intensive. Those who purchase training may find the cost to obtain content for many cybersecurity roles to be prohibitive. Indeed, over 40% of survey participants rated finding RBT materials and updating RBT as moderately or very challenging. On the upside, the majority (about 60%) said that their RBT content is tailored to their organizational mission and current security threats. - RBT approaches: Almost all survey participants (95%) said their organizations offered at least some online training, while over half also allow live training options. Almost half utilize industry-recognized certifications to fulfill RBT requirements. NIST Special Publication (SP) 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations , provides guidance for organizations in protecting their operations, assets, and personnel from security threats and risks [SP800-53]. Within the document, Awareness and Training Control (AT-3) 'Role-based Training' addresses training for personnel with 'responsibilities related to operations and supply chain risk management within the context of organizational security and privacy programs.' Furthermore, organizations are instructed to document, monitor, and retain records for their training activities. In addition to federal personnel, RBT applies to contractors providing services to federal organizations. 'Training for a 'new in role' and 'refresher training' needs are quite different."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| 5.2.4. Device and Media Controls (§ 164.310(d)).................................................................................63 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 5.3.1. Access Control (§ 164.312(a)).....................................................................................................65 |\n| 5.3.2. Audit Controls (§ 164.312(b)).....................................................................................................69 |\n| 5.3.3. Integrity (§ 164.312(c))...............................................................................................................71 |\n| 5.3.4. Person or Entity Authentication (§ 164.312(d)).........................................................................73 |\n| 5.3.5. Transmission Security (§ 164.312(e)(1)).....................................................................................75 |\n| 5.4.1."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.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 does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nArchitecture, Threat Analysis, and Security Posture\n\nArchitecture, Threat Analysis, and Security Posture\n\nGuo Y, Chandramouli R, Wofford L, Gregg R, Key G, Clark A, Hinton C, Prout A, Reuther A, Adamson R, Warren A, Bangalore P, Deumens E, Farkas C (2024) High-Performance Computing Security: Architecture, Threat Analysis, and Security Posture. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-223. https://doi.org/10.6028/NIST.SP.800-223"}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in federal computer systems. This Special Publication 800-series reports on ITL's research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. - ƒ Restoring information systems using alternate equipment;\n- ƒ Performing some or all of the affected business processes using alternate processing (manual) means (typically acceptable for only short-term disruptions);\n- ƒ Recovering information systems operations at an alternate location (typically acceptable for only long-term disruptions or those physically impacting the facility); and\n- ƒ Implementing of appropriate contingency planning controls based on the information system's security impact level. This document does not address facility-level information system planning (commonly referred to as a disaster recovery plan) or organizational mission continuity (commonly referred to as a continuity of operations [COOP] plan) except where it is required to restore information systems and their processing capabilities. Nor does this document address continuity of mission/business processes. Although information systems typically support mission/business processes, the processes also depend on a variety of other resources and capabilities not associated with information systems."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n| 1 | | 1.1 | | Purpose and Scope...................................................................................................1 | | | | 1.2 | Audience ...................................................................................................................1 | | | | 1.3 | Document Structure | ..................................................................................................1 | | 2."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Developing Security Plans for Federal Information Systems provide? (Part 6)"}, {"role": "assistant", "content": ".................. 9 |\n| 2.1 SYSTEM BOUNDARIES................................................................................................................\n| 9 |\n| 2.2 MAJOR APPLICATIONS ............................................................................................................. | 11 |\n| 2.3 GENERAL SUPPORT SYSTEMS .................................................................................................. | 12 |\n| 2.4 MINOR APPLICATIONS ............................................................................................................. | 12 |\n| 2.5 SECURITY CONTROLS .............................................................................................................. | 13 |\n| 2.5.1 Scoping Guidance ........................................................................................................... | 13 |\n| 2.5.2 Compensating Controls .................................................................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\n...............................11 |\n| 2.5.1. Speaker Viewpoints....................................................................................................................11 |\n| 2.5.2.\nKey Highlights .............................................................................................................................13 |\n| 3. Summary and Road Ahead ...........................................................................................................15 |\n| Appendix A. Workshop Agenda........................................................................................................16 |\n| List of Figures |\n| Fig. 1. Components for securing microelectronics................................................................................1 |\n| Fig. 2. Distribution of workshop participants.......................................................................................2 |"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to 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 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 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 does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nPersonnel within the following Workforce Categories and Specialty Areas from the National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework [SP800181] are most likely to find this publication of interest: | Practices | Tasks | Notional Implementation Examples | References | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | Example 4 : Require third parties to provide provenance 5 data and integrity verification mechanisms for all components of their software."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "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 5)"}, {"role": "assistant", "content": "quirements in NIST Special Publication 800-171 and are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.\n## Keywords\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors also wish to recognize the scientists, engineers, and research staff from the NIST Computer Security and the Applied Cybersecurity Divisions for their exceptional contributions in helping to improve the content of the publication. A special note of thanks to Pat O'Reilly, Jim Foti, Jeff Brewer, Chris Enloe, Ned Goren, and the entire NIST web team for their outstanding administrative support. Finally, the authors also gratefully acknowledge the contributions from individuals and organizations in the public and private sectors, nationally and internationally, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n## Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls\n\n## Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls NATIOIVAX.\n\nThe use of computers by Government and private organizations for the storage and manipulation of records of all kinds has continued to Increase at a rapid rate in the three years since the first NBS-sponsored/ GAO-supported Invitational workshop on audit of computer security in March of 1977. The needs of the Individual as well as Government and private organizations for the security of sensitive data and its processing -Including accuracy, reliability, timeliness, and confidentiality -have therefore continued to remain a major concern to the public at large during this time Interval."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Machine Learning for Access Control Policy Verification:\n\nng data . Hence, in order to include all policy rules in training data, the ratio of test set data to training data must be kept to a minimum. However, the algorithm may require no empty test data.\nIn such cases, if the algorithm allowed, some training data can be duplicated to test data. The data table can then be processed by the RFC algorithm to render an RFC subtrees model (Figure 1), whose subtree branches may be rendered to zero or more model policy rules from paths linked by the tree nodes of attributes, actions, and tree leaves of permissions."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nWhile NIST and the NCCoE address goals of improving management of cybersecurity and privacy risk through outreach and applica�on of standards and best prac�ces, it is the stakeholder's responsibility to fully perform a risk assessment to include the current threat, vulnerabili�es, likelihood of a compromise , and the impact should the threat be realized before adop�ng cybersecurity measures such as this recommenda�on. | | 5.4 Specific Details ........................................................................................................... | 5.4 Specific Details ........................................................................................................... | 5.4 Specific Details ..........................................................................................................."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions 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\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the ORCID, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-07-09\n\n## How to cite this NIST Technical Series Publication:\n\nMeltem Sönmez Turan, Kerry A."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\no trust context is a connection to one resource utilizing one network identity and one privilege for that identity (e.g. read, write, delete, etc.) or even a single operation (similar to an API call).\nThis would be the ideal case, but implementations may not allow this fine grain of control and may define sessions as broadly as 'connection to a resource by a network identity with set privileges for a period of time' with reauthentication and reauthorization needed for increased privilege, after a set time period, or an operational change is detected."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 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 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document:\n\nWhen adopting any visibility solution, it's imperative to protect stored session keys from being accessed by external entities to the data center . This requires implementing access controls that enforce least privilege within the data center. Consequently, management's risk assessment involves trading off the relative consequences of delaying TLS 1.3 implementation or replacing enterprise data centers against the cost of protecting stored session keys from access by processes other than those that require or are approved for specific continuous monitoring or forensics functions. While implementing visibility solutions, enterprises must focus on supporting least privilege principles, compliance with zero trust , and supply chain security requirements. See NIST SP 800 -207 [19] . Ideally, implementations will provide network owners with control over what information is actually shared with monitoring systems. Cryptographic protection of all keys, whether at rest or in transit, is essential except where the keys are being employed in a cryptographic process or approved compensating controls are employed."}], "metadata": {"source": "Addressing Visibility Challenges with TLS 1.3 within the Enterprise_ High-Level Document", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to 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 require for Planning?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n| Executive Summary..................................................................................................... | Executive Summary..................................................................................................... | Executive Summary..................................................................................................... | iv |\n|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|\n| 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | |\n| | 1.1 | Purpose and Scope ........................................................................................"}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "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 High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nta and perform complex calculations at high speeds is a key part of the Nation's vision for maintaining its global competitive edge. Security is essential to achieving the anticipated benefits of HPC.\nHPC systems bear some resemblance to enterprise IT computing, which allows for the effective application of traditional IT security solutions. However, they also have significant differences. An HPC system is designed to maximize performance, so its architecture, hardware components, software stacks, and working environment are very different from enterprise IT. Additionally, most HPC systems serve multiple projects and user communities, leading to more complex security concerns than those encountered in enterprise systems. As such, security solutions must be tailored to the HPC system's requirements. Furthermore, HPC systems are often different from one another due to the evolution of their system designs, the applications they run, and the missions they support. An HPC system frequently has its own unique method of applying security requirements and may follow different security guidance, which can impede the sharing of security solutions and knowledge. This NIST Special Publication aims to standardize and facilitate the sharing of HPC security information and knowledge through the development of an HPC system reference architecture and key components, which are introduced as the basics of the HPC system lexicon. The reference architecture divides an HPC system into four function zones. A zone-based HPC reference architecture captures the most common features across the majority of HPC systems and segues into HPC system threat analysis. Key HPC security characteristics and use requirements are laid out alongside the major threats faced by the system and individual function zones. HPC security postures, challenges, recommendations, and some currently recognized variants are also included."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to 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": "What guidance does Recommendations for Federal Vulnerability Disclosure Guidelines provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication NIST SP 800-216\n\n## Recommendations for Federal Vulnerability Disclosure Guidelines\n\nKim Schaffer Peter Mell Hung Trinh Isabel Van Wyk\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-216\n\n\n\n## NIST Special Publication NIST SP 800-216\n\n## Recommendations for Federal Vulnerability Disclosure Guidelines\n\nKim Schaffer Peter Mell Hung Trinh Isabel Van Wyk\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-216\n\nMay 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 2)"}, {"role": "assistant", "content": "er statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official.\nThis publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-56B Revision 2 Natl. Inst. Stand. Technol. Spec. Publ. 800-56B Rev. 2, 131 pages (March 2019) CODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-56Br2\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines 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-01-31\n\n## How to Cite this NIST Technical Series Publication:\n\nChandramouli R, Kautz F, Torres-Arias S (2024) Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-204D. https://doi.org/10.6028/NIST.SP.800-204D\n\n## Author ORCID iDs\n\nRamaswamy Chandramouli: 0000-0002-7387-5858\n\n## Contact Information\n\nsp800-204d-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/204/d/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 predominant application architecture for cloud-native applications consists of multiple microservices, accompanied in some instances by a centralized application infrastructure, such as a service mesh, that provides all application services. This class of applications is generally developed using a flexible and agile software development paradigm called DevSecOps."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\nThe Co-Chairpersons of this workshop were Robert G. McKenzle, an Audit Manager with the GAO [now Eastern Region Director of Audit for the National Aeronautics and Space Administration] , and Zella G. Ruthberg, a Computer Scientist with fIBS. The GAO again gave their generous support to this important undertaking by allowing Mr. McKenzle to devote time to the planning and execution of the workshop, by sending several vital attendees, and by providing us with Mr. Donald L. Scantlebury, Director of the Financial and General Management Studies Division, as Keynote speaker and Chairperson of the session in \"Managerial and Organizational Vulnerabilities and Controls -Staff Level.\"\n\n| 4.2 | Access Policies | 4-12 |\n|-------------|------------------------------------------------------------------------------------------------|-----------|\n| 4.3 | Unauthorized Statistical Disclosure | 4-12 |\n| 4.4 | Transaction Trail | 4-13 |\n| | 4.4.1 Automated Journals | 4-13 |\n| 4.5 | Data Checks and Integrity | 4-13 |\n| 5."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "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 Validating the Integrity of Computing Devices:\n\nguish trustworthy products from others, meaning they are genuine and have not been inappropriately altered. Having this ability is a critical foundation of cyber supply chain risk management (C-SCRM).\nC-SCRM is the process of identifying, assessing, and mitigating risks associated with the distributed and interconnected nature of supply chains. C-SCRM presents challenges to many industries and sectors, requiring a coordinated set of technical and procedural controls to mitigate risks throughout the design, manufacturing, acquisition, provisioning, operations, and decommissioning stages of a product's life."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nVendors may be able to upgrade their PACS software to minimize the hardware changes needed for a legacy PACS to accept PIV Cards. Software or firmware upgrades to controllers or door readers may be available to agencies. PACS suppliers should be asked if software or firmware upgrades supporting PIV Cards are a possibility. If available, the agency should ensure that the"}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "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 NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide?"}, {"role": "assistant", "content": "## NISTIR 8420\n\n## Federal Cybersecurity Awareness Programs\n\nA Mixed Methods Research Study\n\nJulie Haney Jody Jacobs Susanne Furman Fernando Barrientos\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8420\n\n\n\n## NISTIR 8420\n\n## Federal Cybersecurity Awareness Programs\n\nA Mixed Methods Research Study\n\nJulie Haney Jody Jacobs Susanne Furman Fernando Barrientos Information Access Division Information Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8420\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8420 48 pages (March 2022)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8420\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 Planning?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n- [PKCS 1] Moriarty K (ed.), Kaliski B, Jonsson J, Rush A (2016) PKCS #1: RSA Cryptography Specifications Version 2.2 . (Internet Engineering Task Force), IETF Request for Comments (RFC) 8017. https://doi.org/10.17487/RFC8017\n- [SP 800-38B] Dworkin MJ (2016) Recommendation for Block Cipher Modes of Operation: the CMAC Mode for Authentication . (National Institute of Standards and Technology, Gaithersburg, Maryland), NIST Special Publication (SP) 800-38B, May 2005 (includes updates as of 10/06/2016). https://doi.org/10.6028/NIST.SP.800-38B\n- [SP 800-38C] Dworkin MJ (2007) Recommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentiality . (National Institute of Standards and Technology, Gaithersburg, Maryland), NIST Special Publication (SP) 80038C, May 2004 (includes updates as of 07/20/2007). https://doi.org/10.6028/NIST.SP.800-38C\n- [SP 800-38F] Dworkin MJ (2012) Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping . (National Institute of Standards and Technology, Gaithersburg, Maryland), NIST Special Publication (SP) 800-38F, December 2012. https://doi.org/10.6028/NIST.SP.800-38F\n- [SP 800-56A] Barker EB, Chen L, Roginsky A, Vassilev A, Davis R (2018) Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography . (National Institute of Standards and Technology, Gaithersburg, Maryland), NIST Special Publication (SP) 800-56A, Rev. 3, April 2018. https://doi.org/10.6028/NIST.SP.800-56Ar3\n- [SP 800-56C] Barker EB, Chen L, Davis R (2018) Recommendation for Key-Derivation Methods in Key-Establishment Schemes . (National Institute of Standards and Technology, Gaithersburg, Maryland), NIST Special Publication (SP) 800-56C, Rev. 1, April 2018. https://doi.org/10.6028/NIST.SP.800-56Cr1\n- [SP 800-57] Barker EB (2016) Recommendation for Key Management, Part 1: General ."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 is CMMC practice PL.L2-3.15.2 (NIST 3.15.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.15.2. 3.15.2."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.15.2", "cmmc_practice_id": "PL.L2-3.15.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\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- Subscription to multiple cloud services, such as Infrastructure as a Service (IaaS) for computing, Software as a Service (SaaS) for applications, Platform as a Service (PaaS) for an application development platform, and other cloud services (e.g., identity as a service [IDaaS] for authentication)\n- Enterprise IT applications (on-premises) that are located at corporate headquarters and geographically distributed branch offices and data centers\n- IT applications that range from being monolithic to being made up of loosely coupled microservices, each hosted on heterogeneous platforms\n- Presence of edge computing devices, including the Internet of Things (IoT), in some environments"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Access Control on NoSQL Databases provide? (Part 5)"}, {"role": "assistant", "content": ".............................6 |\n| 2.2.3. Fast Queries..................................................................................................................................6 |\n| 2.2.4.\nSecurity Deficiencies.....................................................................................................................7 |\n| 3. Access Control Model on NoSQL Database Systems.........................................................................8 |\n| 3.2.1. Key-Value Model ........................................................................................................................10 |\n| 3.2.2. Wide-Column and Document Models........................................................................................10 |\n| 3.2.3. Graph Model...............................................................................................................................12 |\n| 4. Considerations of Access Control for NoSQL Systems.....................................................................15 |\n| 5."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\n- analysis and testing. FIPS 140-3 and the Common Criteria are useful for analyzing testing and assurance approaches for deterring particular attack classes and vulnerabilities.\n- Better design obfuscation techniques, as well as vulnerability and detectability analysis of malicious insertions in fabricated designs. Among the most significant risks in today's offshoring environment are the loss of intellectual property and the potential for adversaries to compromise chips with hardware trojans. Given the limitations of detecting such vulnerabilities through testing alone, hardware analyses that include power and performance overheads are essential for identifying trojans and other chip malware."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to 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 additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 2)"}, {"role": "assistant", "content": "signed statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications.\nThus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment\nperiods and provide feedback to NIST. Many NIST cybersecurity publications, other than\nthe ones noted above, are available at https://csrc.nist.gov/publications. Authority\n\nThis publication has been developed by NIST in accordance with its statutory\nresponsibilities under the Federal Information Security Modernization Act (FISMA)\nof 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible\nfor developing information security standards and guidelines, including minimum\nrequirements for federal information systems, but such standards and guidelines shall\nnot apply to national security systems without the express approval of appropriate\nfederal officials exercising policy authority over such systems. This guideline is consistent\nwith the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines\nmade mandatory and binding on federal agencies by the Secretary of Commerce\nunder statutory authority. Nor should these guidelines be interpreted as altering or\nsuperseding the existing authorities of the Secretary of Commerce, Director of the\nOMB, or any other federal official. This publication may be used by nongovernmental\norganizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 8)"}, {"role": "assistant", "content": "rollment\n\n. . . . . . . . . . . . . . . . . . . . . . . 4.1.2. Post-Enrollment Binding . . . . . . . . . . . . . . . . . . . . . . 4.1.3. Binding to a Subscriber-Provided Authenticator . . . . . . . .\n. . 4.1.4. Renewal\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2. Account Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1. Account Recovery Methods . . . . . . . . . . . . . . . . . . . . 4.2.2. Recovery Requirements by IAL/AAL . . . . . . . . . . . . . . . . 4.2.3. Account Recovery Notification . . . . . . . . . . . . . . . . . . . 4.3. 4.4. 4.5. Loss, Theft, Damage, and Compromise . . . . . . . . . . . . . . . . . . Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invalidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6. Account Notifications\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . 26\n\n27\n\n30\n\n30\n\n30\n\n31\n\n34\n\n35\n\n36\n\n36\n\n37\n\n37\n\n38\n\n39\n\n41\n\n41\n\n43\n\n43\n\n44\n\n44\n\n46\n\n46\n\n47\n\n47\n\n49\n\n50\n\n50\n\n51\n\n51\n\n51\n\niv\n\n\fNIST SP 800-63B-4\nJuly 2025\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\n5. Session Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1. Session Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.1. Browser Cookies . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.2. Access Tokens\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2. 5.3. Reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Session Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6. Threats and Security Considerations . . . . . . . . . . . . . . . . . . . . . . . 6.1. Authenticator Threats . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2. Threat Mitigation Strategies . . . . . . . . . . . . . . . . . . . . . . . . 6.3. Authenticator Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4. Session Attacks . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 5)"}, {"role": "assistant", "content": ".......................................................................................16 |\n| Appendix A.\nCall for Participants........................................................................................................18 |\n| Appendix B. Mock Product Data Cards............................................................................................... 19 |\n| Appendix C. NIST Introductory Presentation Slides ............................................................................ 24 |\n| List of Figures |\n| Fig. 1. Hand-drawn concept of the storybook manual for children. ......................................................6 |\n| Fig. 2. Sample pages for the storybook manual for children. ................................................................7 |\n| Fig. 3. Cybersecurity-related song created for the toy's cybersecurity education and awareness plan..7 |\n| Fig. 4."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\nVulnerability and fault detection often depend on the specific order of inputs that establish states which eventually lead to a failure. That is, many software processes are not deterministic functions where an input produces the same output whenever the process is invoked irrespective of previous invocations. This is particularly true of real-time systems, which are designed to run continuously, maintain states, and respond to a changing series of inputs. Such systems are typically driven by a loop function that accepts input values, processes and responds to those inputs, and updates its current state. Examples include network protocols and data servers. The system state may change, depending on input, and the system may subsequently respond differently to the same input. That is, the response of the process to a particular set of input values may depend on its current state, such as whether a communication protocol is in a listen or connection-open state. The current state depends on the order of input values that were contained in previously received packets. The same sort of statedependent behavior occurs in many other types of systems as well."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.4.4. 3.4.4. 3.4.4 - Changed from OVAL generation script to SCAP generation script\n- Section 3."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "nist_control": "3.4.4", "cmmc_practice_id": "CM.L2-3.4.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/\nsp/800/63/B/4/final, including related content, potential updates, and document history.\n\nThis guideline provides recommendations on types of authentication processes,\nincluding choices of authenticators, that may be used at various authentication\nassurance levels (AALs). It also provides recommendations on events that may occur\nduring the lifetime of authenticators, including initial issuance, maintenance, and\ninvalidation in the event of loss or theft of the authenticator.\n\nPossession and control of a physical authenticator are based on proof of possession\nof a secret associated with the authenticator. When an embedded secret (typically a\ncertificate and associated private key) is in the endpoint, its “device identity” can be\nconsidered a physical authenticator. However, this requires a secure authentication\nprotocol that is appropriate for the AAL being authenticated. Browser cookies do not\nsatisfy this requirement except as short-term secrets for session maintenance (not\nauthentication), as described in Sec. 5.1.1."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "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 Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls provide?"}, {"role": "assistant", "content": "P\n\nA11103 DTDIDI\n\n\n\n## NCE & TECHNOLOGY:\n\n## Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls\n\n\n\nNBS Special Publication 500-57\n\nU.S. DEPARTMENT OF COMMERCE National Bureau of Standards\n\n## NATIONAL BUREAU OF STANDARDS\n\nThe National Bureau of Standards' was established by an act ot Congress on March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to promote public safety. The Bureau's technical work is performed by the National Measurement Laboratory, the National Engineering Laboratory, and the Institute for Computer Sciences and Technology. THE NATIONAL MEASUREMENT LABORATORY provides the national system of physical and chemical and materials measurement; coordinates the system with measurement systems of other nations and furnishes essential services leading to accurate and uniform physical and chemical measurement throughout the Nation's scientific community, industry, and commerce; conducts materials research leading to improved methods of measurement, standards, and data on the properties of materials needed by industry, commerce, educational institutions, and Government; provides advisory and research services to other Government agencies; develops, produces, and distributes Standard Reference Materials; and provides calibration services. The Laboratory consists of the following centers:\n\nAbsolute Physical Quantities' - Radiation Research - Thermodynamics and Molecular Science - Analytical Chemistry - Materials Science."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 3)"}, {"role": "assistant", "content": "tions during public comment periods and provide feedback to NIST. All NIST Computer Security Division publications, other than the ones noted above, are available at http://csrc.nist.gov/publications.\n## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nMalware, also known as malicious code, refers to a program that is covertly inserted into another program with the intent to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Malware is the most common external threat to most hosts, causing widespread damage and disruption and necessitating extensive recovery efforts within most organizations. This publication provides recommendations for improving an organization's malware incident prevention measures."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 8)"}, {"role": "assistant", "content": "ow businesses apply NCCoE reference designs in the real world. If you have implemented the reference design, or have questions about applying it in your environment, please email us ds-nccoe@nist.gov.\nAll comments are subject to release under the Freedom of Information Act. National Cybersecurity Center of Excellence 100 Bureau Drive Mailstop 2002\n\nNational Institute of Standards and Technology Gaithersburg, MD 20899 Email: nccoe@nist.gov\n\n## NATIONAL CYBERSECURITY CENTER OF EXCELLENCE\n\nThe National Cybersecurity Center of Excellence (NCCoE), a part of the National Institute of Standards and Technology (NIST), is a collaborative hub where industry organizations, government agencies, and academic institutions work together to address businesses' most pressing cybersecurity issues. This public-private partnership enables the creation of practical cybersecurity solutions for specific industries, as well as for broad, cross-sector technology challenges. Through consortia under Cooperative Research and Development Agreements (CRADAs), including technology partners-from Fortune 50 market leaders to smaller companies specializing in information technology security-the NCCoE applies standards and best practices to develop modular, adaptable example cybersecurity solutions using commercially available technology. The NCCoE documents these example solutions in the NIST Special Publication 1800 series, which maps capabilities to the NIST Cybersecurity Framework and details the steps needed for another entity to re-create the example solution. The NCCoE was established in 2012 by NIST in partnership with the State of Maryland and Montgomery County, Maryland. To learn more about the NCCoE, visit https://www.nccoe.nist.gov/. To learn more about NIST, visit https://www.nist.gov. ## NIST CYBERSECURITY PRACTICE GUIDES\n\nNIST Cybersecurity Practice Guides (Special Publication 1800 series) target specific cybersecurity challenges in the public and private sectors."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.5 (NIST 3.5.5)?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n3.5.5 Exceptions to Maintenance Plans | ... 3.5.5 Exceptions to Maintenance Plans\n\nOrganizations should closely track and monitor all exceptions to maintenance plans."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "nist_control": "3.5.5", "cmmc_practice_id": "IA.L2-3.5.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 Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## 3.5. Identify Security-Critical Stages for the Respective Threat"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.7 (NIST 3.3.7)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.3.7 SP800161 : SA-15, SA-15(1), SA-15(11) |\n| Implement and Maintain Secure Environments for Software Development (PO."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.3.7", "cmmc_practice_id": "AU.L2-3.3.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 7)"}, {"role": "assistant", "content": "e most common way programs try to determine their effectiveness (84%). Behavior based measures (e.g., phishing click rates, reporting of phishing emails or other incidents) were utilized by over half.\n- Over half (56%) of survey participants thought their leadership viewed compliance metrics as the most important indicator of program success, with slightly fewer (47%) having the same opinion themselves. However, in qualitative remarks, many focus group and survey participants disagreed with this compliance focus, instead emphasizing that the real purpose of security awareness is to affect employees' security behaviors; therefore, success should be measured in ways beyond training completion rates. - 77% rated their security awareness programs as moderately or very successful. However, 44% of survey participants expressed challenges determining how to measure program effectiveness. Survey and focus group participants desired more guidance on appropriate metrics and government-specific data for benchmarking their own program. - 48% of survey participants indicated that correlating security incident data with behaviors targeted by the security awareness program was challenging. Yet managers taking the survey listed security incident data as the measure of effectiveness most preferred for helping them\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\nmake decisions about the security awareness program, while training completion and phishing click rates were mentioned by much fewer. - Large majorities (70% and greater) thought that security was a priority for the organization, that security was understood by leadership and employees as important, and that leadership and employees supported the security awareness program."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy provide? (Part 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.....28 |\n| 5.1.2. Assigned Security Responsibility (§ 164.308(a)(2)) ....................................................................35 |\n| 5.1.3.\nWorkforce Security (§ 164.308(a)(3)).........................................................................................36 |\n| 5.1.4. Information Access Management (§ 164.308(a)(4)) ..................................................................38 |\n| 5.1.5. Security Awareness and Training (§ 164.308(a)(5)) ...................................................................41 |\n| 5.1.6. Security Incident Procedures (§ 164.308(a)(6)) .........................................................................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8. Evaluation (§ 164.308(a)(8)).......................................................................................................51 |\n| 5.2.1. Facility Access Controls (§ 164.310(a)).......................................................................................56 |\n| 5.1.9. Business Associate Contracts and Other Arrangements (§ 164.308(b)(1))................................54 |\n| 5.2.2. Workstation Use (§ 164.310(b)).................................................................................................59 |\n| 5.2.3. Workstation Security (§ 164.310(c)) ..........................................................................................61 |"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "0-series reports on ITL’s research, guidelines, and outreach\nefforts in information systems security and privacy and its collaborative activities with industry,\ngovernment, and academic organizations.\nAbstract\n\nThis publication provides a methodology and set of procedures for conducting assessments of\nsecurity and privacy controls employed within systems and organizations within an effective risk\nmanagement framework. The assessment procedures, executed at various phases of the system\ndevelopment life cycle, are consistent with the security and privacy controls in NIST Special\nPublication 800-53, Revision 5. The procedures are customizable and can be easily tailored to\nprovide organizations with the needed flexibility to conduct security and privacy control\nassessments that support organizational risk management processes and are aligned with the\nstated risk tolerance of the organization. Information on building effective security and privacy\nassessment plans is also provided with guidance on analyzing assessment results. Keywords\n\nAssessment; assessment plan; assurance; control assessment; FISMA; Privacy Act; privacy\ncontrols; Open Security Controls Assessment Language; OSCAL; privacy requirements; Risk\nManagement Framework; security controls; security requirements. ii\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nA\nr\n5\n\nI\n\n. NIST SP 800-53A REV. 5\nASSESSING SECURITY AND PRIVACY CONTROLS IN INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nAcknowledgments\n\nThis publication was developed by the Joint Task Force Interagency Working Group. The group\nincludes representatives from the civil, defense, and intelligence communities."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\n## Planning for a Zero Trust Architecture:\n\nA Planning Guide for Federal Administrators\n\nNIST Special Publication 800-207 defines zero trust as a set of cybersecurity principles used when planning and implementing an enterprise architecture. These principles apply to endpoints, services, and data flows. Input and cooperation from various stakeholders in an enterprise is needed for a zero trust architecture to succeed in improving the enterprise security posture. Some of these stakeholders may not be familiar with risk analysis and management. This document provides an overview of the NIST Risk Management Framework (NIST RMF) and how the NIST RMF can be applied when developing and implementing a zero trust architecture."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nre, software, and telecommunications components. These components can be a single software application or a combination of hardware/software focused on supporting a specific, mission-related function.\nA major application may also consist of multiple individual applications if all are related to a single mission function (e.g., payroll or personnel). If a system is defined as a major application and the application is run on another organization's general support system, the major application owner is responsible for acceptance of risk and in addition:"}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\n| Background - Zero Trust Principles and Zero Trust Architecture................................\n| 2 |\n| | Relationship to Other NIST Guidance Documents...................................................... | 3 |\n| | Scope......................................................................................................................... | 3 |\n| | Target Audience | ........................................................................................................."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n13 The SDLC refers to the scope of activities associated with a system, encompassing the system's initiation, development and acquisition, implementation, operation, and maintenance, and ultimately its disposal that instigates another system initiation. The SDLC approach is discussed in depth in NIST SP 800-64, Security Considerations in the Information System Development Life Cycle . An overview of contingency planning and the SDLC is provided in Appendix F.\n\nAlthough some changes may be quite visible, others will require additional analysis. When a significant change occurs, the BIA should be updated with the new information to identify new contingency requirements or priorities. As new technologies become available, preventive controls may be enhanced and recovery strategies may be modified. Finally, plan maintenance should be continued as the information system passes through the Disposal phase of its life cycle to ensure that the plan accurately reflects recovery priorities and concurrent processing changes.\n\nDisposal Phase . Contingency considerations should not be neglected because an information system is retired and another system replaces it. Until the new system is operational and fully tested (including its contingency capabilities), the original system's ISCP should be maintained in a ready state for implementation. As legacy systems are replaced, they may provide a valuable capability as a redundant system if a loss or failure of the new information system should occur. In some cases, equipment parts (e.g., hard drives, power supplies, memory chips, or network cards) from hardware that has been replaced can be used as spare parts for new operational equipment. In addition, legacy information systems can be used as test systems for new applications, allowing potentially disruptive system flaws to be identified and corrected in a nonproduction environment."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n|\n| 1. HOST WELCOIING ADDRESS | 1. HOST WELCOIING ADDRESS | 1.\nHOST WELCOIING ADDRESS | 1-1 1-3 |\n| 2. | THE CHARGE TO ALL THE SESSIONS COMMENTS ON THE SESSIONS AND THE REPORTS | THE CHARGE TO ALL THE SESSIONS COMMENTS ON THE SESSIONS AND THE REPORTS | 1-10 |\n| 3. EDITOR'S | 3. EDITOR'S | 3. EDITOR'S | |\n| | | | 1-10 |\n| 3.1 Definitions of Terms | 3.1 Definitions of Terms | 3.1 Definitions of Terms | T-11 |\n| 3.2 Materials Distributed at the Workshop 3.3 Reading the Report 3.4 References | 3.2 Materials Distributed at the Workshop 3.3 Reading the Report 3.4 References | 3.2 Materials Distributed at the Workshop 3.3 Reading the Report 3.4 References | |\n| PART II: 1. | INTRODUCTION CaiPUTERS HAVE BROUGHT NEED FOR SECURITY CONTROLS | KEYNOTE ADDRESS 7 | 2-1 2-2 |\n| 2."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "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 Profile of the IoT Core Baseline for Consumer IoT Products provide? (Part 2)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2022-09-08\n\n## How to Cite this NIST Technical Series Publication:\n\nFagan M, Megas KN, Watrobski P, Marron J, Cuthill B (2022) Profile of the IoT Core Baseline for Consumer IoT Products. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8425. https://doi.org/10.6028/NIST.IR.8425\n\n## Author ORCID iDs\n\nMichael Fagan: 0000-0002-1861-2609\n\nKaterina N. Megas: 0000-0002-2815-5448\n\nPaul Watrobski: 0000-0002-6449-3030\n\nJeffrey Marron: 0000-0002-7871-683X\n\nBarbara B. Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecuirty@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to 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 Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 2)"}, {"role": "assistant", "content": "signed statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements\n\nNIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-12-20\n\n## How to Cite this NIST Technical Series Publication\n\nRekhi S, Kuhn DR, Schaffer K, Souppaya M, Stein AJ, Waller N, Hastings N, Ogata M, Barker WC (2025) Workshop on Enhancing Security of Devices and Components Across the Supply Chain. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8532. https://doi.org/10.6028/NIST.IR.8532\n\n## Author ORCID iDs\n\nWilliam C. Barker: 0000-0002-4113-8861\n\nNelson Hastings: 0000-0003-2444-6413\n\nD. Richard Kuhn: 0000-0003-0050-1596\n\nMichael Ogata: 0000-0002-8457-2430\n\nSanjay (Jay) Rekhi: 0009-0008-8711-4030\n\nKim Schaffer: 0000-0003-3073-2395\n\nMurugiah Souppaya: 0000-0002-8055-8527\n\nA.J."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nWe asked participants in what ways their organizations try to measure or determine the effectiveness of their security awareness program (Figure 24). Security awareness training completion rates (84%) and phishing simulation click rates (72%) were the most popular measures of effectiveness, followed by program audits/evaluations with 67% of participants. Less than 30% selected attendance at security awareness events, employee surveys, and online views of security awareness materials. Four percent said that they do not attempt to measure program effectiveness.\n\n'First is FISMA evaluation from IG. Normally, they'll tell us that they think we did a good job with training awareness or not.' (N06)\n\n'Audits are not tying training to outcomes, so leadership is focused on what the auditors are measuring and making recommendations to improve (e.g. did everyone take training?). Auditors rarely comment on the quality or likely effectiveness of training content, or use their own testing (e.g. phishing, knowledge testing of sample of users) to find out what is really going on (actual effectiveness/outcomes, versus presence of checklist items that might or might not be achieving the desired outcomes).' (Q43)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. When planning an approach to malware prevention, organizations should be mindful of the attack vectors that are most likely to be used currently and in the near future. 4 They should also consider how wellcontrolled their hosts are (e.g., managed environment, non-managed environment); this has significant bearing on the effectiveness of various preventive approaches. In addition, organizations should incorporate existing capabilities, such as antivirus software deployments and patch management programs, into their malware prevention efforts. However, organizations should be aware that no matter how much effort they put into malware incident prevention, incidents will still occur (e.g., previously unknown types of threats, human error). For this reason, as described in Section 4, organizations should have robust malware incident handling capabilities to limit the damage that malware can cause and restore data and services efficiently. An effective awareness program explains proper rules of behavior for use of an organization's IT hosts and information. Accordingly, awareness programs should include guidance to users on malware incident prevention, which can help reduce the frequency and severity of malware incidents."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 2)"}, {"role": "assistant", "content": "ly the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities.\nThe 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. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "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 Security Assessment?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nt software. For example, your organization might subscribe to vulnerability feeds from software vendors, security researchers, and the National Vulnerability Database (NVD). 2. Plan the risk response.\nThis involves assessing the risk the vulnerability poses to your organization, choosing which form of risk response (or combination of forms) to use, and deciding how to implement the risk response. For example, you might determine that risk is elevated because the vulnerability is present in many organization assets and is being exploited in the wild, then choose mitigation as the risk response and mitigate the vulnerability by upgrading the vulnerable software and altering the software's configuration settings. 3. Execute the risk response. This will vary depending on the nature of the selected risk response, but common phases include the following:\n- a. Prepare the risk response. This encompasses any preparatory activities, such as acquiring, validating, and testing patches for the vulnerable software; deploying additional security controls to safeguard the vulnerable software; or acquiring a replacement for a legacy asset that cannot be patched. It might also include scheduling the risk response and coordinating deployment plans with enterprise change management, business units, and others. - b. Implement the risk response. Examples of this include distributing and installing a patch, purchasing cybersecurity insurance, deploying additional security controls, and changing asset configurations and state (e.g., software reset,"}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.9 (NIST 3.1.9)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.9. 3.1.9."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.9", "cmmc_practice_id": "AC.L2-3.1.9", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n..................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5.\nTraceability of CE Operations.....................................................................................................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1. Information Decisions in the System Life Cycle..........................................................................20 |\n| 4.3.2. Determination of Security Categorization..................................................................................21 |\n| 4.3.3. Reuse of Media...........................................................................................................................22 |\n| 4.3.4. Control of Media ........................................................................................................................22 |\n| 4.3.5. Data Protection Level .................................................................................................................23 |\n| 4.3.6. Sanitization and Disposal Decision.............................................................................................23 |"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\ntributes for permissions. This means that there is no choice but to trust the key issuer. Such accountability for user secret keys provides fine-grained access without flexibility or scalability [BS].\nThis makes it unsuitable for certain applications unless it is supported by re-encryption techniques [GOLIC] or integrated with legacy systems such that the key generation system does not manage permission by itself instead of receiving the entitlement data from other system components (e.g., a user permission database so data owners are able to verify such data)."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 10)"}, {"role": "assistant", "content": "that can detect, mitigate, and contain data integrity events in the components of an enterprise network. It also identifies tools and strategies to aid in a security team's response to such an event.\n## KEYWORDS\n\nattack vector; data integrity; malicious actor; malware; malware detection; malware response; ransomware. ## ACKNOWLEDGMENTS\n\nWe are grateful to the following individuals for their generous contributions of expertise and time. | Name | Organization |\n|-------------------|--------------------------------|\n| Kyle Black | Bay Dynamics |\n| Sunjeet Randhawa | Broadcom Inc."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| 4-13 |\n| 4.5 | Data Checks and Integrity | 4-13 |\n| 5.\n| APPLICATIONS INTERFACE | 4-14 |\n| 5.1 | General | 4-14 |\n| 5.2 | System Development Controls | 4-14 |\n| 5.3 | Project Definition | 4-14 |\n| 5.4 | System Design | 4-15 |\n| 5.5 | Detailed Design and Programming | 4-15 |\n| 5.6 | System Testing | 4-15 |\n| 5.7 6. | Conversion | 4-16 |\n| | INTERNAL CONTROL | 4-16 |\n| 6.1 | General | 4-16 4-16 |\n| 6.2 | Control Policies | 4-17 |\n| 6.3 7."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to 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 is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.3.1. 3.3.1)\n\n13. 3.3.1) of any CSP\n\nfraud checks and mitigation technologies to identify potential privacy risks or\nunintended harms."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nThese results suggest the need to provide more guidance and baseline standards for federal RBT activities. An upcoming NIST update to NIST SP 800-50 Building a Cybersecurity and Privacy Learning Program , which our research has informed, may address many of the suggestions for supporting organizations through guidance. Additionally, federal organizations may benefit from standard, government-wide RBT content that could then be tailored to unique mission needs.\n\n- Training on specific tools required for employees to perform security-related job duties\n- Training for employees who have privileged access to applications or systems\n- Training for oversight roles such as information systems security officer (ISSO), information systems security manager (ISSM), or auditors\n- Training for employees who manage access and authorizations to applications and systems\n- Training on organizational policies and procedures related to security and privacy configurations, settings, controls, etc.\n- Cybersecurity for employees in leadership positions, such as 'Cybersecurity for Executives,' Cybersecurity for System Owners,' or 'Becoming A Chief Information System Officer'"}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\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. - Zero trust (ZT) is the term for an evolving set of cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users, assets, 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 assets or user accounts based solely on their physical or network location (i.e., local area networks versus the internet) or on asset ownership (e.g., enterprise or personally owned). Zero trust focuses on protecting resources (e.g., assets, 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 (ZTA) uses zero trust principles to plan industrial and enterprise infrastructure and workflows. - Creation of application identity: The fundamental requirement to enable this is the assignment of a unique identity to each application or service, just like how each user carries a unique identity (e.g., userid)."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Software Supply Chain (SSC) -Definition and Model .....................................................................4 |\n| 2.4.1. Software Supply Chain Defects ....................................................................................................6 |\n| 2.4.2. Software Supply Chain Attacks.....................................................................................................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1. Developer Environment ...............................................................................................................8 |\n| 3.1.2. Threat Actors................................................................................................................................8 |\n| 3.1.3. Attack Vectors ..............................................................................................................................9 |\n| 3.1.4. Attack Targets (Assets).................................................................................................................9 |\n| 3.1.5. Types of Exploits.........................................................................................................................10 |\n| 3.2.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "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 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 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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\n3.3. HAWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n3.3. HAWK"}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Access Control?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n5 An IoT platform is typically a third-party vendor provided/hosted SaaS-based tool that is used to support IoT device and endpoint management, connectivity and network management, data management, processing and analysis, application development, cybersecurity, access control, monitoring, event processing, and interfacing/integration. Documentation about such a third party can provide important information about supply chain cybersecurity practices and vulnerabilities to allow for the IoT user to more accurately determine risks related to the use of an IoT platform."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 6)"}, {"role": "assistant", "content": "a technical field (cybersecurity, IT, or software development). ## Knowledge and Skills\n\n- Survey participants rated the importance of having specific knowledge and skills represented on their teams.\nNot surprisingly, cybersecurity, IT, and privacy knowledge and skills were overwhelming rated as important (over 95% for each). However, many professional knowledge and skills - interpersonal skills, communication skills, creativity, and contextual knowledge of the organization and policies - were also rated highly by over 95% of survey participants. Focus group participants particularly emphasized the importance of oral and written communication skills, for example, being able to translate highly technical information into a language understandable by a diverse workforce. - 61% of survey participants agreed that they have the right mix of skills and abilities within their security awareness teams. Participants mentioned it may be difficult to find a single individual who possesses all the necessary skills. Therefore, building a multidisciplinary team or reaching out to other components in an organization, such as the human resources or public relations departments, can be beneficial. - 70% of survey participants agreed that they were provided with adequate professional development opportunities. However, due to budgetary constraints or lack of specific role-based training, a few participants expressed difficulties obtaining security awareness-specific trainings. This report can serve as a resource for federal security awareness professionals, organizational decision makers, policy makers, and guidance developers to: improve professional development activities for those with security awareness duties; inform hiring decisions for security awareness positions; and advocate for federal security awareness professionals. The results may also be valuable to security awareness professionals outside of the government who face similar challenges."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to 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 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 is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.2.4. 3.2.4."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\nbit of 𝑆 , 𝑖 0≤𝑖≤4 , 0≤𝑗 ≤63 | | 𝑆 𝑖 [𝑗] | 𝑗 𝑡ℎ byte of state word 𝑆 𝑖 for 0≤𝑖≤4 , 0≤𝑗≤7 | | 𝑆 [𝑖∶𝑗] | The subset of state S beginning at index and ending at index , inclusive."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nProgram managers, system owners, and security personnel in the organization must understand the system security planning process. In addition, users of the information system and those responsible for defining system requirements should be familiar with the system security planning process. Those responsible for implementing and managing information systems must participate in addressing security controls to be applied to their systems. This guidance provides basic information on how to prepare a system security plan and is designed to be adaptable in a variety of organizational structures and used as reference by those having assigned responsibility for activity related to security planning.\n\nThe roles and responsibilities in this section are specific to information system security planning. Recognizing that agencies have widely varying missions and organizational structures, there may be differences in naming conventions for security planning-related roles and how the associated responsibilities are allocated among agency personnel (e.g., multiple individuals filling a single role or one individual filling multiple roles 4 ).\n\n- Develops and maintains information security policies, procedures, and control techniques to address system security planning,\n- Manages the identification, implementation, and assessment of common security controls,\n- Ensures that personnel with significant responsibilities for system security plans are trained,\n- Assists senior agency officials with their responsibilities for system security plans, and\n- Identifies and coordinates common security controls for the agency."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 3)"}, {"role": "assistant", "content": "irst Round\nof the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization\nProcess. (National Institute of Standards and Technology, Gaithersburg, MD), NIST IR 8528.\nhttps://doi.org/10.6028/NIST.IR.8528\n\n\fAuthor ORCID iDs\nGorjan Alagic: 0000-0002-0107-6037\nMaxime Bros: 0000-0001-7838-2529\nPierre Ciadoux: 0009-0001-2272-681X\nDavid Cooper: 0009-0001-2410-5830\nQuynh Dang: 0009-0005-9801-6805\nThinh Dang: 0000-0001-9705-0925\nJohn Kelsey: 0000-0002-3427-1744\nJacob Lichtinger: 0000-0003-2407-5309\nYi-Kai Liu: 0000-0001-7458-4721\nCarl Miller: 0000-0003-1917-1531\nDustin Moody: 0000-0002-4868-6684\nRene Peralta: 0000-0002-2318-7563\nRay Perlner: 0000-0001-8793-2238\nAngela Robinson: 0000-0002-1209-0379\nHamilton Silberg: 0009-0004-4178-8954\nDaniel Smith-Tone: 0000-0002-7995-8734\nNoah Waller: 0000-0002-6979-9725\n\nContact Information\npqc-comments@nist.gov\n\nAdditional Information\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8528/final,\nincluding related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). NIST IR 8528\nOctober 2024\n\nAbstract\n\nAdditional Digital Signatures\nFirst Round Status Report\n\nNIST is in the process of evaluating public-key digital signature algorithms for potential\nstandardization to protect sensitive information into the foreseeable future, including after\nthe advent of quantum computers. Any signature scheme that is eventually selected would\naugment FIPS 204, Module-Lattice-Based Digital Signature Standard; FIPS 205, Stateless\nHash-Based Digital Signature Standard; FIPS 186-5, Digital Signature Standard (DSS); and\nSP 800-208, Recommendation for Stateful Hash-Based Signature Schemes. This report de-\nscribes the evaluation criteria and selection process of the First Round of the Additional\nDigital Signatures for the NIST Post-Quantum Cryptography (PQC) Standardization Process."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Configuration Management?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n## Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)\n\n## Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)\n\nTrapnell M, Trapnell E, Souppaya MP, Gendler B, Brodjieski D, Golbig A, Scarfone K, Heiserman B (2023) Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-219r1. https://doi.org/10.6028/NIST.SP.800-219r1"}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.1.2. 3.1.2. 3.1.2 on authenticator optionality, agencies will likely have varied requirements across their user base."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "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 Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne provide? (Part 10)"}, {"role": "assistant", "content": "learly defined and\n- o The interactions of the logical object of the software or firmware module with the operating system and other supporting applications resident within the cryptographic boundary.\n- o Tested Operational Environment's Physical Perimeter (TOEPP) - The location of the cryptographic module with respect to the TOEPP that is part of the module's tested configuration but may be outside of the module's cryptographic boundary so that all of the logical and physical layers between the cryptographic module and the TOEPP are clearly defined. This also includes a description and components list of the TOEPP. - Precise definition of the module's physical TOEPP and cryptographic boundariesy\n\n## · B.2.3 Cryptographic module interfaces\n\nNo change. ## · B.2.4 Roles, services, and authentication\n\nNo change. ## · B.2.5 Software/firmware security\n\n- No change. ## · B.2.6 Operational environment\n\n- No change. - B.2.7 Physical security\n- No change. - B.2.8 Non-invasive security\n- No change. ## · B.2.9 Sensitive security parameters management\n\n- Provide an key SSP [sensitive security parameter] table specifying the key SSP type(s), strength(s) in bits, security function(s), security function certification number(s), where and how the key(s) SSP(s) is generated, whether the key(s) SSP(s) is imported or exported what method(s) is used to input or output the SSP(s), and any SSP generation and establishment method used, and indicate any related keys SSPs. - Specify the electronic and manual key SSP I/O [input/output] method(s). - Specify the SSP storage technique(s) areas, formats (encrypted or plaintext), and persistence types (dynamic or static). ## · B.2.10 Self-tests\n\nNo change. ## · B.2.11 Lifecycle assurance\n\nNo change. ## · B.2.12 Mitigation of other attacks\n\nNo change."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Risk Assessment?"}, {"role": "assistant", "content": "According to A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments:\n\nEach segment is protected by gateway devices, such as intelligent switches and routers or nextgeneration firewalls, that should have the capacity to react and adapt in response to the threats and changes in the application workflows. Segmentation gateways monitor traffic, stop threats, and enforce granular access across east-west traffic (rarely for north-south traffic) within onpremises data centers or cloud regions. The main difficulty with this approach is in mapping the applications' security requirements-based segments to corresponding network segments. Another difficulty is change management. The mapping between applications and network identities that are being statically maintained has to be kept in sync with the operational scenario in which the application's network locations are continuously changing due to performance and security."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to 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 Blockchain for Access Control Systems provide? (Part 2)"}, {"role": "assistant", "content": "aft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\nSubmit comments on this publication to: ir8403-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). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nThe rapid development and wide application of distributed network systems have made network security - especially access control and data privacy - ever more important. Blockchain technology offers features such as decentralization, high confidence, and tamper-resistance, which are advantages to solving auditability, resource consumption, scalability, central authority, and trust issues - all of which are challenges for network access control by traditional mechanisms. This document presents general information for blockchain access control systems from the views of blockchain system properties, components, functions, and supports for access control policy models."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 2)"}, {"role": "assistant", "content": "ent, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI.\nExamples of CUI include:\n\n\n\n| | When provided as part of a government contract, examples include: | Marking 1 |\n|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| Controlled | e.g., research and engineering data, engineering drawings, specifications, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. | CUI//SP-CTI |\n| General Proprietary | e.g., financial information, trade secrets, product research and development, existing and future product designs and performance specifications. | CUI//PROPIN |\n| Business Information | you do not handle CUI, implementing the security requirements in SP 800-171 will | help you take |\n\n1 For more information on types of CUI and markings, visit the National Archives and Records Administration (NARA) https://www.archives.gov/cui."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nDetermine the Goals of an Incident Response | • Gain an understanding as to what constitutes a true security incident. Under the HIPAA Security Rule, a security incident is the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system (45 CFR § 164.304). • Ensure that the incident response program covers all parts of the organization in which ePHI is created, stored, processed, or transmitted. • Determine how the organization will respond to a security incident. • Establish a reporting mechanism and a process to coordinate responses to the security incident. • Provide direct technical assistance, advise vendors to address product-related problems, and provide liaisons to legal and criminal investigative groups, as needed. | • Has the HIPAA-required security risk assessment resulted in a list of potential physical or technological events that could lead to a breach of security? • Is there a procedure in place for reporting and handling incidents? • Has an analysis been conducted that relates reasonably anticipated organizational threats (that could result in a security incident) to the methods that would be used for mitigation? • Have the key functions of the organization been prioritized to determine what would need to be restored first in the event of a disruption? 69 |\n| 2. Develop and Deploy an Incident Response Team or Other Reasonable and Appropriate Response Mechanism | • Determine whether the size, scope, mission, and other aspects of the organization justify the reasonableness and appropriateness of maintaining a standing incident response team. • Identify appropriate individuals to be part of a formal incident response team if the organization has determined that implementing an incident response team is reasonable and appropriate."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\nfrl-northrop-grumman-locked-electronicsassured-design-lead-delay-locking-asic-ip\n- [5] Wolfe F (2020) Aether Spy Next-Generation Multi-Function Radar to Advance, Northrop Grumman Says. Defense Daily .\nAvailable at https://www.defensedaily.com/aether-spynext-generation-multi-function-radar-advance-northrop-grumman-says/air-force/\n- [6] CISA (2020) Defining Insider Threats. Available at https://www.cisa.gov/topics/physicalsecurity/insider-threat-mitigation/defining-insider-threats\n- [7] Areno M (2020) Supply chain threats against integrated circuits. Intel Whitepaper . Available at https://www.intel.com/content/dam/www/centrallibraries/us/en/documents/2022-08/supply-chain-threats-against-integrated-circuitswhitepaper-july2020.pdf\n- [8] Evernex (2024) EOL Meaning: What Does End of Life Mean for Your Hardware? Available at https://evernex.com/industry-guide/eol-meaning/\n- [9] Vincent J (2018) Chinese spies reportedly inserted microchips into servers used by Apple, Amazon, and others. Available at https://www.theverge.com/2018/10/4/17935868/-chinese-spies-microchip-hackservers-apple-amazon-supermicro\n- [10] Yu S, Liu W, O'Neill M (2019) An improved automatic hardware Trojan generation platform. IEEE Computer Society Annual Symposium on VLSI (ISVLSI) (IEEE, Miami, Florida), pp 302-307. https://doi.org/10.1109/ISVLSI.2019.00062\n- [11] Cruz J, Huang Y, Mishra P, Bhunia S (2018) An automated configurable Trojan insertion framework for dynamic trust benchmarks. Design, Automation & Test in Europe Conference & Exhibition (IEEE, Dresden, Germany) pp 1598-1603. https://doi.org/10.23919/DATE.2018.8342270\n- [12] Perez TD, Pagliarini S (2023) Hardware Trojan insertion in finalized layouts: From methodology to a silicon demonstration. IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems (IEEE) 42(7): 2094-2107. https://doi.org/10.1109/TCAD.2022.3223846"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer:\n\nd, communicated, understood, and enforced. Even if cybersecurity activities are outsourced to an external provider, someone within the business should still be designated to manage cybersecurity risk.\n|\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| It's not all technology. | An important point to emphasize is that many requirements in SP 800-171 do not need investments in technology or services to implement. Many requirements can be achieved through the creation of processes and procedures. |\n| Implement the requirements and document implementation in a system security plan. | Satisfying the security requirements won't be accomplished overnight. Implement in phases based upon your resources (includin g time, expertise, budget, etc.), starting with understanding what security requirements you may have already satisfied and building from there."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide? (Part 9)"}, {"role": "assistant", "content": ". . . . | 36 |\n| Table 11. Examples of padding an unsigned integer 𝑥 to a 64-bit block, where 𝑥 encodes a sequence of bytes that each have value 0xFF in little-endian byte order . | 38 |\n| Table 12.\nPrecomputedinitialization phasevaluesfor Ascon-Hash256 , Ascon-XOF128 and Ascon-CXOF128 provided in hexadecimal integer form . . . . . . . . . . . . . . . . . . . . . . . . . . | 40 |\n| Table 13. Parameters for initial value construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 40 |\n| Table 14. Initial values as hexadecimal integers......................................... | 41 |\n\n## List of Figures\n\n| Figure 1. Application of constant-addition layer 𝑝 𝐶 to Ascon state . . . . . . . . . . . . . . . . . . . | 9 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| Figure 2. Application of substitution layer 𝑝 𝑆 to Ascon state . . . . . . . . . . . . . . . . . . . . . . . . . | 9 |\n| Figure 3. Circuit representation of the 5-bit S-box SBOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| Figure 4. Application of linear diffusion layer 𝑝 𝐿 to Ascon state........................ | 10 |\n| Figure 5. Ascon-AEAD128 encryption................................................... | 11 |\n| Figure 6. Ascon-AEAD128 decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| Figure 7. Structure of Ascon-Hash256 and Ascon-XOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| Figure 8. Structure of Ascon-CXOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 30 |\n| Figure 9. Mapping between state words, bytes, and bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 35 |\n| Figure 10."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 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 are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n## Assessing Enhanced Security Requirements for Controlled Unclassified Information\n\nRON ROSS VICTORIA PILLITTERI KELLEY DEMPSEY\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-172A\n\n\n\n## NIST Special Publication 800-172A\n\n## Assessing Enhanced Security Requirements for Controlled Unclassified Information\n\nRON ROSS VICTORIA PILLITTERI KELLEY DEMPSEY\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172A\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by the National Institute of Standards and Technology (NIST) to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 Approaches and Challenges of Federal Cybersecurity Awareness Programs provide? (Part 2)"}, {"role": "assistant", "content": "es even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nOrganizational security awareness programs experience a number of challenges, including lack of resources, difficulty measuring the impact of the program, and perceptions among the workforce that training is a boring, 'check-the-box' activity. While prior surveys and research have examined programs in the private sector, there is little understanding of whether these findings also apply within the U.S. government."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 2. Preliminaries.......................................................................... | 3 |\n| 2.1. Auxiliary Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 7 |\n| 3. Ascon Permutations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.1. Internal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.2. Constant-Addition Layer 𝑝 𝐶 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 8 |\n| 3.3. Substitution Layer 𝑝 𝑆 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 9 |\n| 3.4. Linear Diffusion Layer 𝑝 𝐿 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 4. Authenticated Encryption Scheme: Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1. Specification of Ascon-AEAD128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.1. Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 11 |\n| 4.1.2. Decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 15 |\n| 4.2. Implementation Options . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 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 1 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nPrivacy is a complex and evolving concept that safeguards important values like human autonomy and dignity. It reflects various factors and individual preferences and is highly context-specific, differing between public and private activities. Effective privacy risk management must consider these contexts and the various ways to achieve privacy, such as seclusion, limiting observation, and controlling facets of identity. Gilbert emphasized that privacy could drive innovation and serve as a market differentiator. However, organizations need to have honest and risk-informed discussions about how best to balance optimizing data utility while protecting individuals' privacy, particularly in cases where privacy risk interacts with other risk domains such as cybersecurity. The NIST Privacy Framework helps organizations understand the relationship between privacy and cybersecurity risks in the context of the Internet of Things (IoT). Problematic data actions, such as deriving inferences about individuals, can pose significant privacy risks, particularly in consumer IoT. A key factor in managing privacy risks is an organization's role in t he data processing ecosystem, which includes the complex relationships among entities involved in data processing. An organization's role(s) in the IoT ecosystem can affect its legal obligations and the measures it should take to manage privacy risk. High-level goals for mitigating cybersecurity and privacy risks include protecting device security, data security, and individual privacy. The privacy engineering objectives of predictability, manageability, and disassociability can be useful to meet these goals by supporting the determination of privacy capabilities in IoT products. Gilbert also discussed specific privacy risks related to IoT, such as interactions with the physical world leading to reputational harm or safety issues."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n5.3.3 | Accidental VMDeletion via Maintenance Script ........................................................23 | | | 5.3.4 | Backdoor Creation via Email Vector ...........................................................................24 Insider..............................................................25 | | | 5.3.5 | Database Modification via Malicious |"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\n## 3.4. Augmenting EPSS-Based Remediation Prioritization"}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.......................................................................75 |\n| 5.4.1.\nBusiness Associate Contracts or Other Arrangements (§ 164.314(a)).......................................77 |\n| 5.4.2. Requirements for Group Health Plans (§ 164.314(b))................................................................79 |\n| 5.5.1. Policies and Procedures (§ 164.316(a))......................................................................................81 |\n| 5.5.2. Documentation (§ 164.316(b))...................................................................................................83 |\n| References.......................................................................................................................................85 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................87 |\n| Appendix B. Glossary .......................................................................................................................91 |\n| Appendix C."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "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 Audit and Evaluation of Computer Security:\n\nStandards Application and Analysis —• Electronic Technology — Center for Consumer Product Technology: Product\nSystems Analysis; Product Engineering — Center for Building Technology; Structures, Materials, and Safety; Building\nEnvironment; Technical Evaluation and Application — Center for Fire Research: Fire Science; Fire Safety Engineering. THE INSTITUTE FOR COMPUTER SCIENCES AND TECHNOLOGY conducts research and provides technical services\ndesigned to aid Government agencies in improving cost effectiveness in the conduct of their programs through the selection,\nacquisition, and effective utilization of automatic data processing equipment: and serves as the principal focus wthin the exec-\nutive branch for the development of Federal standards for automatic data processing equipment, techniques, and computer\nlanguages. The Institute consist of the following divisions:\n\nTHE OFFICE FOR INFORMATION PROGRAMS promotes optimum dissemination and accessibility of scientific informa-\ntion generated within NBS; promotes the development of the National Standard Reference Data System and a system of in-\nformation analysis centers dealing with the broader aspects of the National Measurement System; provides appropriate services\nto ensure that the NBS staff has optimum accessibility to the scientific information of the world. The Office consists of the\nfollowing organizational units:\n\nThe National Bureau of Standards has a special responsibility within the Federal\nGovernment for computer science and technology activities. The programs of the\nNBS Institute for Computer Sciences and Technology are designed to provide ADP\nstandards, guidelines, and technical advisory services to improve the effectiveness of\ncomputer utilization in the Federal sector, and to perform appropriate research and\ndevelopment efforts as foundation for such activities and programs."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n1. The high-performance computing zone consists of a pool of compute nodes connected by one or more high-speed networks. The high-performance computing zone provides key services specifically designed to run parallel jobs at scale. 2. The data storage zone comprises one or multiple high-speed parallel file systems that provide data storage service for user data. The high-speed parallel file systems are designed to store very large data sets and provide fast access to data for reading and writing. 3. The access zone has one or more nodes that are connected to external networks, such as the broader organizational network or the internet. This zone provides the means for authenticating and authorizing the access and connections of users and administrators. The access zone provides various services, including interactive shells, web-based portals, data transfer, data visualization, and others. 4. The management zone comprises multiple management nodes and/or cloud service clusters through which HPC management services are provided. The management zone allows HPC system administrators to configure and manage the HPC system, including the configuration of compute nodes, storage, networks, provisioning, identity management, auditing, system monitoring, and vulnerability assessment. Various management software modules (e.g., job schedulers, workflow management, and the Domain Name System [DNS]) run in the management zone. ## 3.3. Other Threats\n\nContainers bundle an application's code, related libraries, configuration files, and required dependencies to allow the applications to run seamlessly across environments. Containers provide the benefits of portability, reproducibility, and productivity, but they can hide software. By decoupling operating system dependencies from the host system, a container image may contain unknown vulnerable or insecure software, which poses a software supply chain risk."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations provide? (Part 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.2.2. 3.2.2. 3.2.2 of [SP800-63B]."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 3)"}, {"role": "assistant", "content": "tions during public comment periods and provide feedback to NIST. All NIST Computer Security Division publications, other than the ones noted above, are available at http://csrc.nist.gov/publications.\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nMobile device forensics is the science of recovering digital evidence from a mobile device under forensically sound conditions using accepted methods. Mobile device forensics is an evolving specialty in the field of digital forensics. This guide attempts to bridge the gap by providing an indepth look into mobile devices and explaining technologies involved and their relationship to forensic procedures. This document covers mobile devices with features beyond simple voice communication and text messaging capabilities. This guide also discusses procedures for the validation, preservation, acquisition, examination, analysis, and reporting of digital information."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\nAI model producers, AI system producers, AI system acquirers, and others can use the SSDF to foster their communications regarding secure AI model development throughout the software development life cycle. 2 Following SSDF practices should help AI model producers reduce the number of vulnerabilities in their AI models, reduce the potential impacts of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of vulnerabilities to prevent recurrences. AI system producers can use the SSDF's common vocabulary when communicating with AI model producers regarding their security practices for AI model development and when integrating AI models into the software they are developing. AI system acquirers can also use SSDF terms to better communicate their cybersecurity requirements and needs to AI model producers and AI system producers, such as during acquisition processes. The SSDF Community Profile is not a checklist to follow, but rather a starting point for planning and implementing a risk-based approach to adopting secure software development practices involving AI models. The contents of the Profile are meant to be adapted and customized, as not all practices and tasks are applicable to all use cases. Organizations should adopt a riskbased approach to determine what practices and tasks are relevant, appropriate, and effective to mitigate the threats to software development practices from the organization's perspective as an AI model producer, AI system producer, or AI system acquirer. Factors such as risk, cost, feasibility, and applicability should be considered when deciding which practices and tasks to use and how much time and resources to devote to each one. Cost models may need to be updated to effectively consider the costs inherent to AI model development."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "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 NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n- Include your relevant suppliers in cybersecurity incident planning, response, and recovery activities. [GV.SC-08] See NIST's Computer Security Incident Handling Guide for more information on key practices for cybersecurity incidents.\n\n☐ Identify one or more specific roles or positions that will be responsible and accountable for planning, resourcing, and executing C-SCRM activities."}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "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 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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 4)"}, {"role": "assistant", "content": "e cycle. This report summarizes the content that was presented and discussed at the workshop. ## Keywords\n\ncybersecurity; hardware security; measurement; semiconductors; supply chain; vulnerabilities.\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the US economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Table of Contents\n\n| 1. Introduction...................................................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Workshop Sessions ........................................................................................................................3 |\n| 2.1.1. Speaker Viewpoints......................................................................................................................3 |\n| 2.1.2. Key Highlights ...............................................................................................................................4 |\n| 2.2.1. Speaker Viewpoints......................................................................................................................5 |\n| 2.2.2."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n3.3.3\n\nMedia Control\n\nFor example, media labeled \"secret\"\n\nIn order to properly safeguard media (tapes, disks,\netc."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\n7-12\n7-12\n7-13\n7-13\n7-13\n....... 7-13\nDesign Standards o\n7-14\nOrganization Control .\n7-14\nAccess Control .\n7-15\nPhase Review/Project Control\nTesting/System Assurance ........ ^\n7-16\n7-16\nPromotion Process\nDocumentation ............... 7-17\n7-17\nAuditor/Independent Party Involvement\nConfiguration Management .......... 7-17\nEmergency Procedures ........... 7-18\n\nProcedure Review\nOrganization Control\nAccess Control ....<, o\nContingency Plan\n\n9c5.3\n905.4\n9.5.5\nSecurity Administration (Interactive Environment) .\nAccess Control\nContingency Plan .....\nSummary"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................3 |\n| 2. An Overview of MFA Technologies and Concepts ............................................................................5 |\n| 2.4.1. Benefits of Identity Federation ....................................................................................................7 |\n| 2.4.2. Benefits of Single Sign-On ............................................................................................................8 |\n| 3. Choosing an MFA Implementation for Protecting CJI .....................................................................11 |\n| 3.1.1. Principle 1: Authenticator Reusability........................................................................................12 |\n| 3.1.2. Principle 2: Authenticator Optionality .......................................................................................12 |\n| 3.1.3. Principle 3: Minimize the Passing of Memorized Secrets ..........................................................12 |\n| 3.1.4. Principle 4: Ensure MFA Is Integrated to Protect CJI..................................................................13 |\n| 3.2.1. MFA Users ..................................................................................................................................13 |\n| 3.2.2."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\ny. 2. Verify the source of new software and the software's integrity before installing it. 3. Configure platforms to use only approved DNS services that block access to known malicious domains. 4. ...\n| • NIST SP 800-161r1, control SI-3 • ISO 27002:2022, control 8.7 • … |\n| … | | | |"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\n- Training on specific tools required for employees to perform security-related job duties\n- Training for employees who have privileged access to applications or systems\n- Training for oversight roles such as information systems security officer (ISSO), information systems security manager (ISSM), or auditors\n- Training for employees who manage access and authorizations to applications and systems\n- Training on organizational policies and procedures related to security and privacy configurations, settings, controls, etc.\n- Cybersecurity for employees in leadership positions, such as 'Cybersecurity for Executives,' Cybersecurity for System Owners,' or 'Becoming A Chief Information System Officer'"}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 5)"}, {"role": "assistant", "content": "| Focus Group Design...................................................................................................\n| 3 |\n| 2.1.2 | Focus Group Recruitment........................................................................................... | 3 |\n| 2.1.3 | Focus Group Data Collection..................................................................................... | 3 |\n| 2.1.4 | Focus Group Data Analysis........................................................................................ | 4 |\n| 2.2 SURVEY METHODOLOGY ..................................................................................................... 4 | 2.2 SURVEY METHODOLOGY ..................................................................................................... 4 | 2.2 SURVEY METHODOLOGY ....................................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 2)"}, {"role": "assistant", "content": "lar A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority.\nNor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-40 Rev. 4 Natl. Inst. Stand. Technol. Spec. Publ. 800-40r4, 28 pages (April 2022) CODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-40r4\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\n'They [the Department team] start with the same approach every year where they are developing the annual training at the Department level and the agencies are providing input for improvement and development before it's released to users, so we can provide ideas for topics directly for the training.' (S05)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nOrganizations should use centrally managed antivirus software that is controlled and monitored regularly by antivirus administrators, who are also typically responsible for acquiring, testing, approving, and delivering antivirus signature and software updates throughout the organization. Users should not be able to disable or delete antivirus software from their hosts, nor should they be able to alter critical settings. Antivirus administrators should perform continuous monitoring to confirm that hosts are using current antivirus software and that the software is configured properly. Implementing all of these recommendations should strongly support an organization in having a strong and consistent antivirus deployment across the organization.\n\n| Resource Name | URL |\n|-----------------------------------------------------------------------------------------------|--------------------------------------------------------|\n| NIST, SP 800-94, Guide to Intrusion Detection and Prevention Systems (IDPS) | http://csrc.nist.gov/publications/PubsSPs.html#800-94 |\n| NIST, SP 800-115, Technical Guide to Information Security Testing and Assessment | http://csrc.nist.gov/publications/PubsSPs.html#800-115 |\n| NIST, SP 800-117, Guide to Adopting and Using the Security Content Automation Protocol (SCAP) | http://csrc.nist.gov/publications/PubsSPs.html#800-117 |\n| NIST, SP 800-128, Guide for Security-Focused Configuration Management of Information Systems | http://csrc.nist.gov/publications/PubsSPs.html#800-128 |\n| NIST, SP 800-147. BIOS Protection Guidelines | http://csrc.nist.gov/publications/PubsSPs.html#800-147 |"}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "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 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 Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 7)"}, {"role": "assistant", "content": "|\n| 2.1.3. Develop Technical Analysis Capability .....................................................................\n| 9 | |\n| Receive Source Vulnerability | Report .......................................................................... 9 | |\n| Triage and Prioritize Source Vulnerability | Report........................................................"}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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.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 additional guidance does Guide for Developing Security Plans for Federal Information Systems provide? (Part 7)"}, {"role": "assistant", "content": "|\n| 2.5.2 Compensating Controls ..................................................................................................\n| 15 |\n| 2.5.3 Common Security Controls ............................................................................................. | 16 |\n| 3. PLAN DEVELOPMENT........................................................................................................... 19 | 3. PLAN DEVELOPMENT........................................................................................................... 19 |\n| 3.1 SYSTEM NAMEAND I DENTIFIER............................................................................................... | 19 |\n| 3.2 SYSTEM CATEGORIZATION ...................................................................................................... | 19 |\n| 3.3 SYSTEM OWNER ...................................................................................................................... | 19 |\n| 3.4 AUTHORIZING OFFICIAL .........................................................................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 10)"}, {"role": "assistant", "content": "|\n| Fig. 5. Basic process steps of KP-ABE scheme........................................................................19 | Fig. 5.\nBasic process steps of KP-ABE scheme........................................................................19 | |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Elliptic curve used for general ECC and bilinear pairing..............................................10 | Table 1. Elliptic curve used for general ECC and bilinear pairing..............................................10 | |\n\n## Acknowledgments\n\nThe author would like to express his thanks to Lily Chen, Isabel Van Wyk, and Jim Foti of NIST, Alex Leadbeater of Maketh Secure, Giovanni Bartolomeo of CNIT, and Laure Pourcin of ETSI for their reviews of both the public comment version as well as the final publication. ## Executive Summary\n\nTraditional public-key encryption (PKE) requires different data to have different keys that can be distributed to users who satisfy access control policies along with the encrypted version of the data."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Blockchain for Access Control Systems:\n\n1. The semantic and syntactic correctness (i.e., veracity of AC data) needs to be ensured or trusted. If such data are from out-of-the-chain sources, an authority for oracle needs to be applied to validate and oversee the correctness of the data. However, if it is provided by different AC nodes, then multiple authorities working in coordination can take part in validating different sources or functions embedded in the smart contracts that need to be developed for the tasks [GMS]. 2. In addition to secure transmission and repositories of AC data in the blockchain, inherited hash cypher schemes may be required to avoid exposing vulnerabilities or other types of malicious actions performed by unauthorized entities in AC notes or smart contracts. Smart contracts may also be created to define the secure communications between AC notes for AC data owners, creators, or managers. 3. Cache synchronization and failover/backup capabilities for readiness of the AC system refers to the frequency of refresh for AC data change. A blockchain AC system needs to adequately perform AC data update and retrieval frequencies to ensure that a recent set of AC data in question is cached in the blockchain if the most current AC data from authoritative sources or repositories cannot be accessed during an emergency (e.g., low bandwidth, loss of service). Migrating from a legacy centralized system to a blockchain AC system needs to address the changes in security assumptions and the assurances of tools and communication protocols for the new decentralized architecture. For example, reimplementing a system using a smart contract language requires changes to secure programming practices, or changing a legacy protocol to Hypertext Transfer Protocol Secure (HTTPS) requires new communications acknowledgements."}], "metadata": {"source": "Blockchain for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\nforward | A telecommunications technique in which information is sent to an intermediate station where it is kept and later sent to the final destination or to another intermediate station.\n|\n| Support (a security strength) | A security strength of s bits is said to be supported by a particular choice of algorithm, primitive, auxiliary function, parameters (etc.) for use in the implementation of a cryptographic mechanism if that choice will not prevent the resulting implementation from attaining a security strength of at least s bits. In this Recommendation, it is assumed that implementation choices are intended to support a security strength of 112 bits or more (see SP 800-57 6 and SP 800-131A 7 ). |\n| Symmetric key | A cryptographic key that is shared between two or more entities and used with a cryptographic application to process information. |\n| Symmetric-key algorithm | A cryptographic algorithm that uses secret keying material that is shared between authorized parties. |\n| Targeted security strength | The security strength that is intended to be supported by one or more implementation-related choices (such as algorithms, primitives, auxiliary functions, parameter sizes and/or actual parameters) for the purpose of instantiating a cryptographic mechanism. In this Recommendation, it is assumed that the targeted security strength of any instantiation of an approved key-establishment scheme has a value greater than or equal to 112 bits and less than or equal to 256 bits. |\n| Trusted association | Assurance of the integrity of an asserted relationship between items of information that may be provided by cryptographic or non- cryptographic (e.g., physical) means. Also see Binding. |\n| Trusted party | A party that is trusted by an entity to faithfully perform certain services for that entity. An entity could be a trusted party for itself."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nThe 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. 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. Dr. Arnold joined the National Institute of Standards and Technology (NIST) in September 2006 as Deputy Director, Technology Services, after a 33-year career in the telecommunications and information technology industry. He was appointed National Coordinator for Smart Grid Interoperability at in April 2009. He has been responsible for leading the development of standards underpinning the nation's Smart Grid. In October 2011, Dr. Arnold added an additional role as Director of Cyber Physical Systems within NIST's Engineering Laboratory (EL)."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST. This guideline focuses on the authentication of subjects who interact with government\ninformation systems over networks to establish that a given claimant is a subscriber\nwho has been previously authenticated. The result of the authentication process may\nbe used locally by the system performing the authentication or asserted elsewhere in a\nfederated identity system. This document defines technical requirements for each of the\nthree authentication assurance levels. The guidelines are not intended to constrain the\ndevelopment or use of standards outside of this purpose. This publication supersedes\nNIST Special Publication (SP) 800-63B. The Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to 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 Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 7)"}, {"role": "assistant", "content": "elihood that a vulnerability has been observed to be exploited. Only a small fraction of the tens of thousands of software and hardware vulnerabilities that are published every year will be exploited.\nPredicting which ones is important for the efficiency and cost effectiveness of enterprise vulnerability remediation efforts. One study shows that only 5 % of vulnerabilities have been observed to be exploited in the wild [2], while the monthly vulnerability remediation rate for companies is 16 % [3]. The remediation rate is so low because it is expensive for companies to address vulnerabilities. Security patches must be tested with enterprise software to ensure continuity of operations; some vulnerabilities require non-patch remediations that require human deployment. This situation would not be a problem if the 16 % were to cover the 5 %, but metrology is lacking to accurately make that calculation. Thus, predicting which vulnerabilities will be exploited is critically important for the efficiency and cost-effectiveness of enterprise vulnerability remediation efforts. One effort that has made great progress towards this goal is the Exploit Prediction Scoring System (EPSS). EPSS provides probabilities that a vulnerability will be observed to be exploited in the wild within the next 30 days [4]. However, its probabilities are known to be inaccurate for vulnerabilities that have been previously observed to be exploited; this is stated in the EPSS documentation itself [1]. Fortunately, the probabilities are not randomly inaccurate; they underestimate the true probability. Another area that is foundational for vulnerability remediation prioritization are Known Exploited Vulnerability (KEV) lists. KEV lists are enumerations of vulnerabilities that have definitively been exploited in the past (e.g., [5] and [6]). However, such lists may not be comprehensive, and prior to this research, metrology did not exist to measure their coverage."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Guide for Developing Security Plans for Federal Information Systems provide? (Part 2)"}, {"role": "assistant", "content": "lines, including minimum requirements, for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems.\nThis guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III. This guideline has been prepared for use by federal agencies. It may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright. (Attribution would be appreciated by NIST.)\n\nNothing in this document should be taken to contradict standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. iii\n\n## Acknowledgements\n\nThe National Institute of Standards and Technology would like to acknowledge the authors of the original NIST Special Publication 800-18, Guide for Developing Security Plans for Information Technology System. The original document was used as the foundation for this revision. Additionally, thank you to all the NIST staff that reviewed and commented on the document."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Ordered t-way Combinations for Testing State-based Systems provide? (Part 7)"}, {"role": "assistant", "content": "y combinations in other rows. For three Boolean parameters a, b, c in Fig. 3, ab =00 is followed by ab =10 ab =00 ac =11 ac =01 bc =01 ( ac =01 and bc =01 are also followed by this group). Fig 3.\nOrdered combinations of parameter values\n\n| a | b | c |\n|-----|-----|-----|\n| 0 | 0 | 1 |\n| 1 | 0 | 1 |\n| 0 | 0 | 1 |\n\nCombinations of parameter values such as this can be significant in protocol verification and testing, such as with combinations of values in each packet affecting the state where later packets produce different responses depending on the state that resulted from previous packet orders. Definition 2. An ordered combination cover , OCC( N,s,t,p,v ), covers all s -orders of t -way combinations of the v values of p parameters, where t is the number of parameters in combinations and s is the number of combinations in an ordered series. Permutations of parameter value combinations may appear multiple times in a combination order. For example, a particular 2-order of 2-way combinations may be ( p 1 p 2 = 01) *→ ( p 2 p 4 = 11). The utility of combination order covering can be illustrated with an example. Consider the covering array in Fig. 4, which includes all 2-way combinations of four Boolean variables. Fig. 4. 2-way covering array of Boolean variables. | Test | p 1 | p 2 | p 3 | p 4 |\n|--------|-------|-------|-------|-------|\n| 1 | 0 | 0 | 1 | 0 |\n| 2 | 0 | 1 | 0 | 1 |\n| 3 | 1 | 0 | 0 | 1 |\n| 4 | 1 | 1 | 1 | 0 |\n| 5 | 0 | 1 | 0 | 0 |\n| 6 | 0 | 0 | 1 | 1 |\n\nSuppose these six tests are applied to the system modeled with a finite state machine diagram in Fig. 5, and tests are run in the order 1..6. If condition A = 'p1 ∧ p2' and condition B = 'p1 ∧ ~p2', then the error in state 2 will not be discovered."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\nJust like RDMBS, NoSQL databases are susceptible to injection attacks, which allow attackers to add malicious data to the NoSQL and cause unavailability and corrupt data. NoSQL injection attacks typically occur when the attack string is parsed, evaluated, or concatenated into a NoSQL API call. Attackers who are familiar with the syntax, data model, and underlying programming language of the target database can design specific exploits, especially in cases where server-side middleware (e.g., JavaScript, PHP) is heavily used to enhance database performance. For example, an internal operator '$where,' designed to be used like the 'where' clause in SQL, can accept sophisticated JavaScript functions to filter data. An attacker can exploit this by passing arbitrary code or commands into the $where operator as part of the query. The Open Worldwide Application Security Project (OWASP) Test Guide (v4) [OW] plans to include new procedures for testing NoSQL injections to assess NoSQL systems built upon JavaScript and/or PHP engines that may possess similar vulnerabilities [CJ]. - [CJ] Crawford J (2014) Current Data Security Issues of NoSQL Databases, Fidelis Cybersecurity Volume 17 . Available at https://silo.tips/download/current-data-security-issues-ofnosql-databases\n- [FA] Fullstack Academy (2017) RDF Tutorial - An Introduction to the Resource Description Framework. Available at https://www.youtube.com/watch?v=zeYfT1cNKQg\n- [FF] Colombo P, Ferrari E. (2016) Fine-Grained Access Control Within NoSQL DocumentOriented Datastores, Data Sci. Eng. 1, pp 127-138. https://doi.org/10.1007/s41019-0160015-z\n- [HI] hiteshreddy2181(2023) Types of NoSQL Databases, Geeksforgeeks . Available at https://www.geeksforgeeks.org/types-of-nosql-databases/\n- [HS] Hu VC, Quirolgico S, Scarfone K (2008) Access Control Policy Composition for Resource Federation Networks Using Semantic Web and Resource Description Framework (RDF), Proceeding of 2008 International Computer Symposium , pp 497-502 (v1)."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n3.2.4. 3.2.4."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n| 1 | | 1.1 | | Purpose and Scope...................................................................................................1 | | | | 1.2 | Audience ...................................................................................................................1 | | | | 1.3 | Document Structure | ..................................................................................................1 | | 2."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "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 8)"}, {"role": "assistant", "content": "e requirements also apply to services, including externally provided services, that process, store, or transmit CUI, or that provide security protections, for the system requiring enhanced protection.\nThe protection of a specific service to include CUI that is processed, stored or transmitted during the provision of that service, is achieved by implementing the enhanced security requirements for the service, or the system or system components responsible for providing that service. In addition to protecting CUI from unauthorized disclosure, the enhanced security requirements have been designed to protect the integrity and availability of CUI. This is achieved by promoting penetration-resistant architectures, damage-limiting operations, and designs to help achieve cyber resiliency and survivability. The term organizational system is used in many of the enhanced security requirements. It has a specific meaning regarding the applicability of the enhanced requirements as described above. Appropriate scoping considerations for the requirements are important factors in determining protection-related investment decisions and managing security risk for nonfederal organizations that have the responsibility of protecting CUI associated with critical programs and high value assets. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## FRAMEWORK FOR IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY\n\nOrganizations that have implemented or plan to implement the NIST Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] can find in Appendix C a mapping of the enhanced security requirements in this publication to the security controls in [SP 800-53]."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 3)"}, {"role": "assistant", "content": "The guide was developed and is maintained by the Joint Task Force Transformation Initiative Interagency Working Group, part of an ongoing information security partnership among the U.S. Department of Defense, the Intelligence Community, the Committee on National Security Systems, the Department of Homeland Security, and U.S. federal civil agencies. SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. SP 800-53 Revision 4 is part of the NIST Special Publication 800-series that reports on the NIST Information Technology Laboratory's (ITL) computer security-related research, guidelines, and outreach. The publication provides a comprehensive set of security controls, three security control baselines (low, moderate, and high impact), and guidance for tailoring the appropriate baseline to specific needs according to the organization's missions, environments of operation, and technologies used. As the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information provide? (Part 4)"}, {"role": "assistant", "content": "nistrative, technical, and physical standards and guidelines for the cost-effective security and privacy of information other than national security-related information in federal information systems.\n## Audience\n\nThe audience for this document includes state CJIS information security officers (ISOs) and CJIS systems officers (CSOs), law enforcement agency chief information officers (CIOs) and chief information security officers (CISOs), and anyone else responsible for safeguarding CJI. The audience also includes vendors that supply CJI-related technology products and services to agencies that are subject to the CJIS Security Policy. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................3 |\n| 2."}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n| | Introduction ....................................................................................................1 | | |-----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| | 1.1 | | Purpose.......................................................................................................................1 | | | 1.2 | | Scope..........................................................................................................................2 | | | 1.3 | | Audience.....................................................................................................................3 | | | 1.4 | Document | Structure....................................................................................................4 | | | Chapter 2."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Machine Learning for Access Control Policy Verification provide?"}, {"role": "assistant", "content": "## NISTIR 8360\n\n## Machine Learning for Access Control Policy Verification\n\nVincent C. Hu\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8360\n\n\n\n## NISTIR 8360\n\n## Machine Learning for Access Control Policy Verification\n\nVincent C. Hu\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8360\n\nSeptember 2021\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8360 25 pages (September 2021)\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8360\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Machine Learning for Access Control Policy Verification", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.5.4 | Segregation Through Virtualization | ... 3.5.4 Segregation Through Virtualization\n\nBrowser separation essentially segregates web browsers from each other."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.5.4", "cmmc_practice_id": "IA.L2-3.5.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 9)"}, {"role": "assistant", "content": ".................................................................................. | 3.3 SECURITY AWARENESS PROGRAMS ...................................................................................\n| 12 |\n| 3.3.1 | Program Size............................................................................................................. | 12 |\n| 3.3.2 | Team Size .................................................................................................................. | 14 |\n| 4 CONCLUSION................................................................................................................... 17 | 4 CONCLUSION................................................................................................................... 17 | 4 CONCLUSION................................................................................................................... 17 |\n| REFERENCES............................................................................................................................ 18 | REFERENCES............................................................................................................................ 18 | REFERENCES............................................................................................................................"}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 2)"}, {"role": "assistant", "content": "ailable at https://csrc.nist.gov/publications/cswp, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA).\nMay 19, 2025\n\n## Abstract\n\nThis work presents a proposed security metric to determine the likelihood that a vulnerability has been observed to be exploited. Only a small fraction of the tens of thousands of software and hardware vulnerabilities that are published every year will be exploited. Predicting which ones is important for the efficiency and cost effectiveness of enterprise vulnerability remediation efforts. Currently, such remediation efforts rely on the Exploit Prediction Scoring System (EPSS), which has known inaccurate values, and Known Exploited Vulnerability (KEV) lists, which may not be comprehensive. The proposed likelihood metric may augment EPSS remediation (correcting some inaccuracies) and KEV lists (enabling measurements of comprehensiveness). However, collaboration with industry is necessary to provide necessary performance measurements. ## Keywords\n\nCommon Vulnerabilities and Exposures; CVE; Known Exploited Vulnerabilities; KEV; Exploit Prediction Scoring System; EPSS; exploit; Likely Exploited Vulnerabilities; LEV; metrology; prediction; scoring; security; vulnerability. | Table of Contents |\n|------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................1 |\n| 2. Background....................................................................................................................................3 |\n| 3."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information:\n\n| A representative cohort of general users can help test the MFA solution before a general user rollout. | • Take volunteers or a selection of the general cohort to test the MFA solution.\n• Test IT support and help desk procedures. • Hold user feedback sessions. • Update communications and/or policy based on feedback. |\n| 4 | General user rollout | Once agencies are satisfied with testing from phases 1-3, it is time to proceed to a general rollout. This may not include some user populations that fall into corner cases. | • Provide multiple waves of communication around the MFA transition. • Allow for questions, answers, and feedback. • Provide a clear deadline for making the transition. • Update communications and/or policy based on feedback. • Monitor and grow adoption over time. |\n| 5 | Corner case users | Corner case requirements may require alternate MFA solutions. | • Enumerate requirements and potential solutions for corner cases. • Test potential solutions with phases 1-3 before rolling out to corner case users. |"}], "metadata": {"source": "Multi-Factor Authentication for Criminal Justice Information Systems_ Implementation Considerations for Protecting Criminal Justice Information", "cmmc_level": "all", "cmmc_domain": "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 3)"}, {"role": "assistant", "content": "The guide was developed and is maintained by the Joint Task Force Transformation Initiative Interagency Working Group, part of an ongoing information security partnership among the U.S. Department of Defense, the Intelligence Community, the Committee on National Security Systems, the Department of Homeland Security, and U.S. federal civil agencies. SP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. SP 800-53 Revision 4 is part of the NIST Special Publication 800-series that reports on the NIST Information Technology Laboratory's (ITL) computer security-related research, guidelines, and outreach. The publication provides a comprehensive set of security controls, three security control baselines (low, moderate, and high impact), and guidance for tailoring the appropriate baseline to specific needs according to the organization's missions, environments of operation, and technologies used. As the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nBefore the system security plan can be developed, the information system and the information resident within that system must be categorized based on a FIPS 199 impact analysis. Then a determination can be made as to which systems in the inventory can be logically grouped into major applications or general support systems. The FIPS 199 impact levels must be considered when the system boundaries are drawn and when selecting the initial set of security controls (i.e., control baseline). The baseline security controls can then be tailored based on an assessment of risk and local conditions including organization-specific security requirements, specific threat information, costbenefit analyses, the availability of compensating controls, or special circumstances. Common security controls, which is one of the tailoring considerations, must be identified prior to system security plan preparation in order to identity those controls covered at the agency level, which are not system-specific. These common security controls can then be incorporated into the system security plan by reference. - -Security controls associated with public access information systems must be carefully considered and applied with discretion since some of the security controls from the specified security control baselines (e.g., personnel security controls, identification and authentication controls) may not be applicable to users accessing information systems through public interfaces. 12\n\n12 For example, while the baseline security controls require identification and authentication of organizational personnel who maintain and support information systems that provide public access services, the same controls might not be required for users accessing those systems through public interfaces to obtain publicly available information."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 2)"}, {"role": "assistant", "content": "## Table of Contents | 1 | Introduction ............................................................................................................1 | |------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 2 | NIST SP 800-53 Revision 4 and the Risk Management Framework (RMF)........2 | | 3 | Control Baselines and Tailoring ...........................................................................4 | | 4 | Documenting the Control Selection Process ......................................................5 | | 5 | Assurance...............................................................................................................6 | | 6 | Security Controls ...................................................................................................7 | | 7 | International Information Security Standards .....................................................8 | | 8 | Overlays..................................................................................................................9 | | 9 | Privacy ..................................................................................................................10 | | List of Figures | List of Figures | | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | Figure 1: Risk Management 3-Tiered Approach.........................................................2 | | Figure 2: The Risk Management Framework ..............................................................3 | Figure 2: The Risk Management Framework ..............................................................3 | | Figure 3: Security Control Selection Process ............................................................5 | Figure 3: Security Control Selection Process ............................................................5 | ## 1 Introduction In April, 2013, NIST published an update, Revision 4, to NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organization ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 5)"}, {"role": "assistant", "content": "11 | | Appendix B-Acronyms and Abbreviations............................................................14 Appendix C-Glossary | ..............................................................................................15 | | Appendix D-References ..........................................................................................16 | | | List of Figures | List of Figures | | Figure 1: SCAP v2 Architectural Components and Protocols ..................................4 | Figure 1: SCAP v2 Architectural Components and Protocols ..................................4 | | Figure 2: SCAP v2 Architecture: Endpoint Posture Information Collection ............9 | Figure 2: SCAP v2 Architecture: Endpoint Posture Information Collection ............9 | | Figure 3: SCAP v2 Architecture: Vulnerability Information Sharing.......................10 | Figure 3: SCAP v2 Architecture: Vulnerability Information Sharing.......................10 | | Figure 4: SCAP v2 Architecture: Vulnerability Analysis Capabilities.....................11 | Figure 4: SCAP v2 Architecture: Vulnerability Analysis Capabilities.....................11 | | Figure 5: SCAP v2 Architecture: Configuration Setting Checklist Assessment....12 | Figure 5: SCAP v2 Architecture: Configuration Setting Checklist Assessment....12 | ## 1 Introduction This document defines a set of design goals for the next major revision of the Security Content Automation Protocol (SCAP), SCAP v2."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process provide? (Part 8)"}, {"role": "assistant", "content": "signature\nschemes remained. In July 2022, NIST called for additional digital signature proposals to be considered in the\nPQC standardization process to diversify its post-quantum signature portfolio.\nSince two\nsignature schemes based on structured lattices had already been standardized, NIST ex-\npressed particular interest in additional general-purpose signature schemes based on a\nsecurity assumption that did not use structured lattices as well as signature schemes with\nshort signatures and fast verification. NIST published the Call for Proposals for Additional Digital Signatures [2], which specified\nthe submission requirements and evaluation criteria, and received 50 submission packages\non June 1, 2023. Of those, NIST accepted 40 First-Round Candidates that consisted of\nsignature schemes based on a variety of different security assumptions. The submission\npackages of the first-round candidates were posted online at https://csrc.nist.gov/Projec\nts/pqc-dig-sig/round-1-additional-signatures for public review and comment. The Fifth NIST PQC Standardization Conference was held in Rockville, Maryland, on April\n10-12, 2024. The submission teams of the accepted first-round candidates were invited to\npresent posters for their candidate algorithms. Throughout the first round, NIST received\nsignificant feedback from the cryptographic community. Based on the public feedback\nand internal reviews of the first-round candidates, NIST announced the selection of 14\nsignature algorithms as Second-Round Candidates in October 2024 to move forward to\nthe next stage of the standardization process. Table 1 shows a timeline of major events with respect to the Additional Digital Signatures\nfor the NIST PQC Standardization Process to date. 1\n\n\fNIST IR 8528\nOctober 2024\n\nAdditional Digital Signatures\nFirst Round Status Report\n\nTable 1."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Personnel Security?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n| FOREWORD | FOREWORD | FOREWORD | HI |\n|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-----------------|\n| ABSTRACT | ABSTRACT | ABSTRACT | Iv |\n| ACKNOWLEDGEtENTS | ACKNOWLEDGEtENTS | ACKNOWLEDGEtENTS | Iv |\n| EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | xlll |\n| PART T: INTRODUCTION | PART T: INTRODUCTION | PART T: INTRODUCTION | 1-] |\n| 1. HOST WELCOIING ADDRESS | 1. HOST WELCOIING ADDRESS | 1."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "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 AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.3.3 KAS2-Party_U-confirmation | ... 3.3.3); it may also be added to a KAS1 or KTS-OAEP scheme, but only with party V (the party contributing the key pair) acting as the key-confirmation provider, and party U acting as the key-confirmation recipient (see Sections 8. 3.3.3 can be used to provide assurance to a key-pair owner, acting as party V, that both parties are in possession of the correct private key; i."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 6)"}, {"role": "assistant", "content": "|\n| Fig. 1. Components for securing microelectronics................................................................................1 |\n| Fig. 2.\nDistribution of workshop participants.......................................................................................2 |\n\n## 1. Introduction\n\nSemiconductor-based hardware is the foundation of modern-day electronics - from smartphones, computers, and telecommunications to transportation and critical infrastructure. The semiconductor hardware supply chain is a complex network of companies that collectively provide intellectual property, designs, and raw materials and manufacture, test, package, and distribute products. Coordination among the components of a supply chain is required at different stages, including inception, deployment to end users, maintenance during use, and disposal or end of life. Securing semiconductor-based hardware and their supply chains help protect sensitive information, maintain the integrity of systems, and ensure overall stability across the infrastructure and connected world. Securing semiconductors involves the security of the component being built as well as the design, development, manufacturing, and distribution environments. Figure 1 illustrates the components of achieving robust semiconductor security. Fig. 1. Elements for securing microelectronics\n\n\n\nThese activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Audit and Evaluation of Computer Security:\n\nThe National Bureau of Standards, with the support of the U.S. Gen-\neral Accounting Office, sponsored an invitational workshop on \"Audit and\nEvaluation of Computer Security,\" held in Miami Beach, Florida on March\n22-24, 1977.\narea and define appropriate subjects for future research.\nperts in the audit and computer communities were invited to discuss the\nsubject in one of ten sessions, each of which considered a different as-\npect.\nthese reports form the body of these Proceedings.\nThe ten topics re-\nported on are: Internal Audit Standards, Qualifications and Training,\nSecurity Administration, Audit Considerations in Various System Environ-\nments, Administrative and Physical Controls, Program Integrity, Data In-\ntegrity, Communications, Post-Processing Audit Tools and Techniques, and\nInteractive Audit Tools and Techniques.\n\nKEYWORDS:\ntraining, communications security, computer controls, computer\nsecurity, data integrity, interactive audit, internal audit, post-\nprocessing audit, program integrity.\n\n........\n....\nInternal Audit Standards\nQualifications and Training ............\n.....\nSecurity Administration\nAudit Considerations in Various System\n.....\nEnvironments\nAdministrative and Physical Controls .......\n.....\nProgram Integrity\nData Integrity\nCommunications\nPost-Processing Audit Tools and Techniques ....\nInteractive Audit Tools and Techniques"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to 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 does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges:\n\nNIST Special Publication (SP) 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations , provides guidance for organizations in protecting their operations, assets, and personnel from security threats and risks [SP800-53]. Within the document, Awareness and Training Control (AT-3) 'Role-based Training' addresses training for personnel with 'responsibilities related to operations and supply chain risk management within the context of organizational security and privacy programs.' Furthermore, organizations are instructed to document, monitor, and retain records for their training activities. In addition to federal personnel, RBT applies to contractors providing services to federal organizations."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "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 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 System and Communications Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.6. Verifier-CSP or IdP Communications . . . . . . . . . . . . . . . .\n\nThroughout this document, [FIPS140] requirements are satisfied by security\ntechnologies, products, and services that utilize implementations of cryptography\nvalidated by the Cryptography Module Validation Program [CMVP]. FIPS 140\nrequirements at a given AAL are often different for authenticators and verifiers, with\nmore stringent requirements generally applying to verifiers. This is in recognition of the\npractical limitations on the certification of authenticators as well as the broader scope\nthat is often associated with a security breach at a verifier.\n\n2.1.2. Authenticator and Verifier Requirements\nAuthenticators used at AAL1 SHALL use approved cryptography. In other words, they\nmust use approved algorithms, but the implementation need not be validated under\n[FIPS140]."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Validating the Integrity of Computing Devices:\n\n7 |\n| | | 3.2.2 Scenario 2: | Verification of Components During Acceptance Testing........................... 7 |\n| | | 3.2.3 | Scenario 3: Verification of Components During Use...................................................."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 9)"}, {"role": "assistant", "content": "- Phase III | 27 | | | 2.3.4 Programming and Training - Phase IV | 2.3.4 Programming and Training - Phase IV | 2.3.4 Programming and Training - Phase IV | 28 | | | 2.3.5 Evaluation and Acceptance - Phase V | 2.3.5 Evaluation and Acceptance - Phase V | 2.3.5 Evaluation and Acceptance - Phase V | 28 | | | 2.3.6 Installation and Operation - Phase VI | 2.3.6 Installation and Operation - Phase VI | 2.3.6 Installation and Operation - Phase VI | 29 | | 2.4 | RESPONSIBLE PARTICIPANTS AND THEIR FUNCTION IN THE | RESPONSIBLE PARTICIPANTS AND THEIR FUNCTION IN THE | RESPONSIBLE PARTICIPANTS AND THEIR FUNCTION IN THE | 29 | | | AIS LIFE CYCLE 2.4.1 Policy/Oversight Participants | AIS LIFE CYCLE 2.4.1 Policy/Oversight Participants | AIS LIFE CYCLE 2.4.1 Policy/Oversight Participants | 29 | | | 2.4.1.1 | 2.4.1.1 | Information Resources Management (IRM) Official | 29 | | | 2.4.1.2 | 2.4.1.2 | System Security Officer (SSO) | 30 | | | 2.4.1.3 | 2.4.1.3 | Internal Control Officer (ICO) | 30 | | | 2.4.2 Functional/Operational Participants | 2.4.2 Functional/Operational Participants | 2.4.2 Functional/Operational Participants | 30 |"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 5)"}, {"role": "assistant", "content": "Organization of This Document . . . . | 3 |\n| 2. Evaluation Criteria and Selection Process . . | . . . . . . . . | 4 |\n| 2.1. | Acceptance of the Fourth-Round Candidates . .\n. . | 4 |\n| 2.2. | Evaluation Criteria . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.1. Security . . . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.2.Cost and Performance . . . . . . . . . . . . . | 5 |\n| | 2.2.3.Algorithm and Implementation Characteristics | 8 |\n| 2.3. | Selection of the Candidates for Standardization . . . | 8 |\n| 3. Summary of the Fourth-Round Candidates . | . . . . . . . . | 10 |\n| 3.1. | HQC . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . . . . . | 14 |\n| 3.4. | SIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 16 |\n| 4. Conclusion . . | . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| References . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| Appendix A."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n3.5.1 Maintenance Plans for Scenario 1, Routine Patching... 3.5.1 Maintenance Plans for Scenario 1, Routine Patching\n\nOrganizations should consider adopting phased deployments for routine patching in which a small subset of the assets to be patched receive the patch first."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "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 System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\nautomated key-establishment schemes. | Algorithm | A clearly specified mathematical process for computation; a set of rules that, if followed, will give a prescribed result.\n|\n|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Approved | FIPS- approved or NIST-Recommended. An algorithm or technique that is either 1) specified in a FIPS or NIST Recommendation, or 2) adopted in a FIPS or NIST Recommendation and specified either (a) in an appendix to the FIPS or NIST Recommendation, or (b) in a document referenced by the FIPS or NIST Recommendation. |\n| Assumption | Used to indicate the conditions that are required to be true when an approved key-establishment scheme is executed in accordance with this Recommendation. |\n| Assurance of private-key possession | Confidence that an entity possesses a private key corresponding to a public key. |\n| Assurance of validity | Confidence that either a key or a set of domain parameters is arithmetically correct. |\n| Big-endian | The property of a byte string having its bytes positioned in order of decreasing significance."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n- o ENISA : European Union Agency for Network and Information Security (ENISA), 'Baseline Security Recommendations for IoT in the context of Critical Information Infrastructures' [10] - o ETSI : European Telecommunications Standards Institute (ETSI), 'Cyber Security for Consumer Internet of Things' [11] - o GSMA : Groupe Spéciale Mobile Association (GSMA), 'GSMA IoT Security Assessment' [12] - o IEC : International Electrotechnical Commission (IEC), 'IEC 62443-4-2, Edition 1.0, Security for industrial automation and control systems - Part 4-2: Technical security requirements for IACS components' [13] - o IIC : Industrial Internet Consortium (IIC), 'Industrial Internet of Things Volume G4: Security Framework' [14] - o IoTSF : IoT Security Foundation (IoTSF), 'IoT Security Compliance Framework, Release 2' [15] - o ISOC/OTA : Internet Society/Online Trust Alliance (OTA), 'IoT Security & Privacy Trust Framework v2.5' [16] - o NEMA : National Electrical Manufacturers Association (NEMA), 'Cyber Hygiene Best Practices' [17] - o OCF : Open Connectivity Foundation (OCF) 'OCF Security Specification Version 2.1.2' [18] - o PSA : Platform Security Architecture (PSA) Joint Stakeholder Agreement (JSA) Members, 'PSA Certified™ Level I Questionnaire, Version 2.0 Beta' [19] | Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |--------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 10)"}, {"role": "assistant", "content": "Timeline of the NIST Post-Quantum Cryptography Standardization Process | Date | Event | |-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | April 2015 | Workshop on Cybersecurity in a Post-Quantum World, NIST, Gaithersburg,MD | | February 2016 | PQC Standardization: Announcement and outline of NIST's Call for Submissions presentation given at PQCrypto 2016 | | April 2016 | Release of IR 8105, Report on Post-Quantum Cryptography [10] | | December 2016 | Federal Register Notice - Announcing Request for Nominations for Public-Key Post-Quantum Cryptographic Algorithms [11] | | November 30, 2017 | Submission Deadline for NIST PQC Standardization Process | | December 2017 | Announcement of first-round candidates and beginning of first- round public comment period | | April 2018 | First NIST PQC Standardization Conference, Ft."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Awareness and Training?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| 1. The ability to report the device's cybersecurity state 2. The ability to differentiate between when a device will likely operate as expected from when it may be in a degraded cybersecurity state 3. The ability to restrict access to the state indicator so only authorized entities can view it 4. The ability to prevent any entities (authorized or unauthorized) from editing the state except for those entities that are responsible for maintaining the device's state information 5. The ability to make the state information available to a service on another device, such as an event/state log server | • This capability supports vulnerability management and incident detection. • Cybersecurity state awareness helps enable investigating compromises, identifying misuse, and troubleshooting certain operational problems. • How the device makes other entities aware of a cybersecurity state will vary based on context- specific needs and goals, but may include capturing and logging information about events in a persistent record that may have to be stored off the device, sending signals to a monitoring system to be handled externally, or alerting via an interface on the IoT device itself. | • CSDE : 5.1.7 • CTIA : 4.7, 4.12, 5.7, 5.16 • ENISA : GP-TM-55, GP-TM- 56 • ETSI : 4.7-2, 4.10-1 • GSMA : CLP13_6.13.1, 7.2.1, 9.1.1.2 • IEC : CR 2.8, CR 3.9, CR 6.1, CR 6.2 • IIC : 7.3, 7.5, 7.7, 8.9, 10.3, 10.4 • IoTSF : 2.4.7.5 • NEMA : Monitoring Devices and Systems • OCF: 5.1, 5.7, 8.6, 12, 13.8, 13.16 • PSA : C1.3, D1.1, D3.2, D3.4, D3.5, D5.1, R4.1, R4.3, R4.4 |"}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.5 (NIST 3.4.5)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.4.5 | Two Level Work Priority Dimensions/Characteristics | Two Level Work Priority Dimensions/Characteristics | 54 |\n| | 3. 3.4.5. 3.4.5."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.4.5", "cmmc_practice_id": "CM.L2-3.4.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\n3.2.1. 3.2.1."}], "metadata": {"source": "Access Control on NoSQL Databases", "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 2)"}, {"role": "assistant", "content": "systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process:\n\n| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . | . . . | 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|\n| 1.1. | Purpose and Organization of This Document . . . . | 3 |\n| 2. Evaluation Criteria and Selection Process . . | . . . . . . . . | 4 |\n| 2.1. | Acceptance of the Fourth-Round Candidates . . . . | 4 |\n| 2.2. | Evaluation Criteria . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.1. Security . . . . . . . . . . . . . . . . . . . . . . | 4 |\n| | 2.2.2.Cost and Performance . . . . . . . . . . . . . | 5 |\n| | 2.2.3.Algorithm and Implementation Characteristics | 8 |\n| 2.3. | Selection of the Candidates for Standardization . . . | 8 |\n| 3. Summary of the Fourth-Round Candidates . | . . . . . . . . | 10 |\n| 3.1. | HQC . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 10 |\n| 3.2. | BIKE . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 12 |\n| 3.3. | Classic McEliece . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "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 Guide for Developing Security Plans for Federal Information Systems:\n\nTitle III of the E-Government Act, entitled the Federal Information Security Management Act (FISMA), requires each federal agency to develop, document, and implement an agency-wide information security program to provide information security for the information and information systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor, or other source. System security planning is an important activity that supports the system development life cycle (SDLC) and should be updated as system events trigger the need for revision in order to accurately reflect the most current state of the system. The system security plan provides a summary of the security requirements for the information system and describes the security controls in place or planned for meeting those requirements. The plan also may reference other key security-related documents for the information system such as a risk assessment, plan of action and milestones, accreditation decision letter, privacy impact assessment, contingency plan, configuration management plan, security configuration checklists, and system interconnection agreements as appropriate. Before the system security plan can be developed, the information system and the information resident within that system must be categorized based on a FIPS 199 impact analysis. Then a determination can be made as to which systems in the inventory can be logically grouped into major applications or general support systems. The FIPS 199 impact levels must be considered when the system boundaries are drawn and when selecting the initial set of security controls (i.e., control baseline). The baseline security controls can then be tailored based on an assessment of risk and local conditions including organization-specific security requirements, specific threat information, costbenefit analyses, the availability of compensating controls, or special circumstances."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 4)"}, {"role": "assistant", "content": "y. This publication introduces the mSCP and gives an overview of the resources available from the project's GitHub site, which is continuously curated and updated to support each new release of macOS.\nThe GitHub site provides practical, actionable recommendations in the form of secure baselines and associated rules. This publication also describes use cases for leveraging the mSCP content. Updates from the previous version of this publication mainly involve the new mSCP capability to create a custom benchmark by tailoring a baseline. ## Keywords\n\nApple; baseline; configuration management; endpoint device security; macOS; macOS Security Compliance Project (mSCP); operating system security; security compliance. ## 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\nThe mSCP's GitHub site is at https://github.com/usnistgov/macos\\_security#readme, and the project documentation wiki is at https://github.com/usnistgov/macos\\_security/wiki. ## Trademark Information\n\nAll registered trademarks or trademarks belong to their respective organizations."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 4)"}, {"role": "assistant", "content": "00-171A, Assessing Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the CUI security requirements in SP 800-171.\nNIST SP 800-172, Enhanced Security Requirements for Protecting Controlled Unclassified Information provides enhanced security requirements to help protect CUI associated with critical programs or high value assets in nonfederal systems and organizations from the advanced persistent threat (APT). The SP 800-172 enhanced security requirements are designed to protect confidentiality, integrity and availability of information. \n\nNIST SP 800-172A, Assessing Enhanced Security Requirements for Controlled Unclassified Information provides assessment procedures and a methodology to conduct assessments of the enhanced security requirements in SP 800-172. ## A is for Assessment\n\nKnowing what requirements to implement is important, but it is also important to understand how to evaluate the organization's implementation. Both publications work handin-hand for full implementation. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas\n\n\n\nified-information\n\nProtecting information from unauthorized modification\n\n## Key Term: Security Requirement\n\n[SP 800-171] Security Requirement: Security outcomes levied on a nonfederal organization to ensure adequate measures are taken to protect the confidentiality of CUI being processed, stored, or transmitted. \n\n\n\nImportant Note: The security requirements in NIST SP 800-171 are only applicable to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. Protecting information from unauthorized access and disclosure\n\nPreventing disruption in how information is accessed\n\n\n\n2 SP 800-171 does not explicitly cover integrity and availability so it is not a comprehensive security program."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body ...................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "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 Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 7)"}, {"role": "assistant", "content": "ing to network identity, endpoint health, or data flows. Some discussion of the tenets is included, and some considerations that planners should keep in mind when developing a zero trust architecture.\n## 1.1.1 Tenets that Deal with Network Identity Governance\n\n- I. All resource authentication and authorization are dynamic and strictly enforced before access is allowed. A typical enterprise has a wide collection of network identities: end users, accounts used by processes and services, etc. Some end users may have multiple network identities, and some identities may only be used by\n\n1 The unit of 'session' can be nebulous and differ depending on tools, architecture, etc. The basic definition in a zero trust context is a connection to one resource utilizing one network identity and one privilege for that identity (e.g. read, write, delete, etc.) or even a single operation (similar to an API call). This would be the ideal case, but implementations may not allow this fine grain of control and may define sessions as broadly as 'connection to a resource by a network identity with set privileges for a period of time' with reauthentication and reauthorization needed for increased privilege, after a set time period, or an operational change is detected. hardware/software components. The enterprise needs to have a governance policy and structure in place so that only authorized operations are performed, and only when the identity has properly authenticated itself. The enterprise needs to consider if their current identity governance policies are mature enough and where and how are authentication and authorization checks currently performed. Dynamic enforcement means that other factors such as endpoint and environmental factors impact authentication and authorization policies. ## 1.1.2 Tenets that Deal with Endpoints\n\n- I. All data sources and computing services are considered resources."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to 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 additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 4)"}, {"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## Abstract\n\nFew software development life cycle (SDLC) models explicitly address software security in detail, so secure software development practices usually need to be added to each SDLC model to ensure that the software being developed is well-secured. This document recommends the Secure Software Development Framework (SSDF) - a core set of high-level secure software development practices that can be integrated into each SDLC implementation. Following such practices should help software producers reduce the number of vulnerabilities in released software, reduce the potential impact of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of vulnerabilities to prevent future recurrences. Because the framework provides a common vocabulary for secure software development, software acquirers can also use it to foster communications with suppliers in acquisition processes and other management activities. ## Keywords\n\nsecure software development; Secure Software Development Framework (SSDF); secure software development practices; software acquisition; software development; software development life cycle (SDLC); software security. ## Trademark Information\n\nAll registered trademarks or trademarks belong to their respective organizations. ## Acknowledgments\n\nThe authors thank all of the organizations and individuals who provided input for this update to the SSDF. In response to Section 4 of Executive Order (EO) 14028 on 'Improving the Nation's Cybersecurity,' NIST held a June 2021 workshop and received over 150 position papers, many of which suggested secure software development practices, tasks, examples of implementations, and references for consideration for this SSDF update."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- A portable and interoperable cryptographic identity is required for workloads or services, as well as a standardized way to retrieve, validate, and interact with those identities. An example of such a specification is Secure Production Identity Framework for Everyone (SPIFFE) [47]. - The location of the service may change due to the virtualized nature of the application hosting environment (e.g., migration to different Virtual Machines (VMs), migration to a different pod in containerized applications). Hence, the identity should abstract the environment hosting the service. - The validation of identity (authentication) and authorization need to be done continuously (and not just at the beginning of a service request) as the risk profile associated with the request may change if there are multiple entities involved or if there are changes in behavioral patterns that need to be included as a validation parameter and monitored. - Packet filters and network address translation: Packet filtering and Network address translation (NAT) are used to monitor and control packets moving across a network interface, apply predetermined security rules, and obscure the internal network from the public internet. - Stateful inspection: Stateful firewalling, also known as dynamic packet filtering, monitors the state of connections and makes determinations as to what types of data packets belong to a known active connection and can be allowed to pass through the firewall. - Deep packet inspection (DPI): This feature, also known as packet sniffing, examines the content of packets (both the header and the payload, unlike the stateful inspection that inspects only the packet header). In addition to the capability provided by stateful inspection, this has capabilities related to finding hidden threats within the data stream, such as attempts at data exfiltration, violations of content policies, malware, and more."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\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. that and now have automated tools…Our onboarding site is a self-registration site so that our new staff can go and self-register, take their training, and then that ties into our primary learning center once they're on board and approved. We reconcile those transcripts. So, we do have now the automated means where we do tie it into our backend account management system so that, truly, people aren't getting access to things before they've taken that training and signed the rules of behavior."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "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 Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\n## Workshop on Enhancing Security of Devices and Components Across the Supply Chain\n\n## Workshop on Enhancing Security of Devices and Components Across the Supply Chain\n\nRekhi S, Kuhn DR, Schaffer K, Souppaya M, Stein AJ, Waller N, Hastings N, Ogata M, Barker WC (2025) Workshop on Enhancing Security of Devices and Components Across the Supply Chain. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8532. https://doi.org/10.6028/NIST.IR.8532"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nCybersecurity utility: Maintaining confidentiality, integrity, and availability of data is foundational to cybersecurity for IoT products. Customers will expect that data are protected and that protection of data helps to ensure safe and intended functionality of the IoT product. Cybersecurity utility: Enumerating and controlling access to all internal and external interfaces to the IoT product will help preserve the confidentiality, integrity, and availability of the IoT product, its components, and data by helping prevent unauthorized access and modification. | Vulnerability | Relevant Consumer Profile Capabilities |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Mirai Malware Variants Attacks - Use of weak authentication to enable the loading of malware onto the device and use that device in DDOS and other attacks. | Mirai Malware Variants Attacks - Use of weak authentication to enable the loading of malware onto the device and use that device in DDOS and other attacks."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 9)"}, {"role": "assistant", "content": "NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Introductory Tips for Implementers\n\n\n\n## What's New in SP 800 -171, Revision 3? ## SP 800-171, Revision 3 was published in May 2024. Significant changes include:\n\n## Updates to the Security Requirements and Families\n\n- Based on NIST SP 800-53, Revision 5 and the NIST SP 800-53B moderate impact control baseline. - Applies updated tailoring criteria addressing stakeholder feedback (adding new, consolidating, and withdrawing requirements). - Includes increased specificity in security requirements. - Introduces organization-defined parameters (ODP) to increase flexibility to better manage organizationspecific risks. ## Additional Revision 3 Resources\n\n- A CUI overlay (.xlsx) showing the direct link between SP 800-53 and SP 800171, including NIST's tailoring decisions. - Transitioning your organization from implementation of Revision 2 to Revision 3? Review this detailed analysis of the changes between Revision 2 and Revision 3 (.xlsx). - The SP 800-171 security requirements in multiple formats (Excel, JSON, and online) through the NIST Cybersecurity and Privacy Reference Tool. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Key Terms\n\n\n\n\n\nControl Baseline: A set of controls you can implement to meet strategic, legal, regulatory, or contractual security and privacy requirements and manage risk. Organization-Defined Parameters (ODPs) are included in certain security requirements. ODPs provide the flexibility and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.12 (NIST 3.2.12)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.2.12 of [SP800-63B]). 3.2.12 of [SP800-63B])."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.2.12", "cmmc_practice_id": "AT.L2-3.2.12", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\n- Integrate C-SCRM into cybersecurity and enterprise risk management, risk assessment, and improvement processes, and monitor the performance of C-SCRM practices throughout the technology lifecycle. [GV.SC-03, GV.SC-09] See the Enterprise Risk Management Quick-Start Guide for more information on C-SCRM integration.\n\n☐ vet their employees and guard against insider threats\n\n- Risk Assessment: The authenticity and integrity of hardware and software are assessed prior to acquisition and use [ID.RA-09]; Critical suppliers are assessed prior to acquisition [ID.RA-10]\n- Improvement: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties [ID.IM-02]"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "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 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 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 require for Security Assessment?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n## Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls\n\n## Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls NATIOIVAX.\n\nThe National Bureau of Standards, with the support of the U.S. General Accounting Office, sponsored a second invitational workshop on computer security audit, entitled \"Audit and Evaluation of Computer Security II: System Vulnerabilities and Controls,\" In Miami Beach, Florida, on November 28-30, 1978. A cross-section of highly qualified people In the computer science and EDP audit fields was assembled to develop material that would be directly usable for a Federal Information Processing Standard (FTPS) Guideline on the subject. Tn order to cover the material in a systematic fashion, the workshop was partitioned into three management sessions and five technical sessions. The management sessions addressed Managerial and Organizational Vulnerabilities and Controls at the Staff Level (1 session) and the Line Level (2 sessions). The technical sessions addressed vulnerabilities and controls in the areas of Terminal and Remote Peripherals, Communication Components, Operating Systems, Applications and Non- Integrated Data Files, and Data Base/ Data Base Management Systems. These Proceedings are the reports developed by the eight sessions of the workshop."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "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 IR.L2-3.6.5 (NIST 3.6.5)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.6.5 Classification Schemes | Encryption | 10-12 10-12 |\n| 3. 3.6.5 Encryption ; While access control and inference are discouraging, database encryption is thought (by some) to be a more promising tool in database security [6]."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.6.5", "cmmc_practice_id": "IR.L2-3.6.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 Configuration Management?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## 3.4. Analyze the Effect of Collusion Among Adversaries in Different Stages"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security:\n\nthe National Bureau of Standards.\nrity audit project, Mrs. Ruthberg worked closely with Mr. McKenzie on\nthe planning, acted as the Workshop arrangements chairman, and is co-\neditor of these Proceedings.\nin computer science at NBS and most recently has become active in the\nmanagerial procedures required for computer security.\n\nIntroduction\nPlanning by Management\nManagement Control .....\nADP Security\n2.4.1\n2.4.2\n2.4.3\n2.4.4\n2.4.5\n\nINITIATING THE WORKSHOP\nPLANNING THE WORKSHOP\n2.1\n2.2\n2.3\nAT THE WORKSHOP\nTHE SESSION REPORTS"}], "metadata": {"source": "Audit and Evaluation of Computer Security", "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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.8. Authentication Intent\nAn authentication process demonstrates intent if it requires the claimant to respond\nexplicitly to each authentication or reauthentication request. The goal of authentication\nintent is to make it more difficult for authenticators (e.g., multi-factor cryptographic\nauthenticators) to be used without the claimant’s knowledge, such as by malware on\nthe endpoint. The authenticator itself SHALL establish authentication intent. Multi-\nfactor authenticators MAY establish intent by reentry of the activation factor for the\nauthenticator.\n\nSome technologies (e.g., the emerging device bound session credentials specification\n[DBSC]) mitigate the risk of theft of session secrets by using cryptographic protocols\nthat prove the possession of a session secret rather than using them as bearer tokens.\nThese technologies might additionally store and use these session secrets in protected\nkeystores to reduce the risk of exfiltration by malware. Session secrets used with such\nproof of possession techniques MAY persist. However, RPs and CSPs SHALL ensure that\nthe session lifetime limits described in Sec. 2.2.3 are enforced even when a knowledge of\nthe session secret is demonstrated.\n\nEnsure the endpoint’s security\nbefore use, especially with\nrespect to freedom from malware\n(e.g., key loggers)."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Configuration Management?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n## IoT Non-Technical Supporting Capability Core Baseline\n\n## Internet of Things Non-Technical Supporting Capability Core Baseline\n\nNon-technical supporting capabilities are actions a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device. This publication defines an Internet of Things (IoT) device manufacturers' non-technical supporting capability core baseline , which is a set of non-technical supporting capabilities generally needed from manufacturers or other third parties to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems. The purpose of this publication is to provide organizations a starting point to use in identifying the non-technical supporting capabilities needed in relation to IoT devices they will manufacture, integrate, or acquire. This publication is intended to be used in conjunction with NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers and NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 9)"}, {"role": "assistant", "content": "y and Privacy Controls for Information Systems and Organizations , provides guidance for organizations in protecting their operations, assets, and personnel from security threats and risks [SP800-53].\nWithin the document, Awareness and Training Control (AT-3) 'Role-based Training' addresses training for personnel with 'responsibilities related to operations and supply chain risk management within the context of organizational security and privacy programs.' Furthermore, organizations are instructed to document, monitor, and retain records for their training activities. In addition to federal personnel, RBT applies to contractors providing services to federal organizations. NIST SP 800-53 is a major basis for the Federal Information Security Modernization Act of 2014 (FISMA) [FISMA2014], which requires federal organizations to implement RBT [CISA2022]. ## There was no clear picture of how federal organizations conduct RBT and what challenges they experience when implementing these training activities. We conducted a prior study that explored federal security awareness programs through focus groups and a survey [IR8420][IR8420A] [IR8420B]. In the focus groups, we found that security awareness professionals were often also assigned responsibilities for role-based training activities, for which they identified significant challenges. However, at the time, no one had taken a broader look across federal organizations to see how RBT activities were implemented and what issues organizations were experiencing. This lack of understanding hindered the development of improvements and resources for federal RBT. ## We conducted a research study to explore the approaches and challenges of federal RBT activities. To address the lack of understanding about how RBT activities are implemented in the U.S. Federal Government, we conducted a study to answer the following questions:\n\n- Q1. How do federal organizations determine which employees need to take RBT? - Q2."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 additional guidance does Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges provide? (Part 3)"}, {"role": "assistant", "content": "organizations are required to conduct cybersecurity role-based training for federal government personnel and supporting contractors who are assigned roles having security and privacy responsibilities.\nDespite the training mandate, there has been little prior effort to look broadly across federal organizations to see how they are implementing these training activities and what issues they are experiencing. This lack of understanding may be hindering the development of improvements and resources for training activities. To address this gap, the Usable Cybersecurity team at the National Institute of Standards and Technology conducted a research study consisting of focus groups and a survey to gain insights into the approaches of and challenges faced by federal organizations when implementing role-based training activities. This paper reports the results of the study and suggests actions that organizations can take to improve federal role-based training activities."}], "metadata": {"source": "Federal Cybersecurity Role-Based Training Approaches, Successes, and Challenges", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Incident Response?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThis includes requirements from internal sources (e.g., the organization's policies, business objectives, and risk management strategy) and external sources (e.g., applicable laws and regulations). | PO.1.1 : Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. | Example 1 : Define policies for securing software development infrastructures and their components, including development endpoints, throughout the SDLC and maintaining that security. Example 2 : Define policies for securing software development processes throughout the SDLC and maintaining that security, including for open-source and other third-party software components utilized by software being developed. Example 3 : Review and update security requirements at least annually, or sooner if there are new requirements from internal or external sources, or a major security incident targeting software development infrastructure has occurred. Example 4 : Educate affected individuals on impending changes to requirements."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to 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 additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-03-30 Supersedes NIST Special Publication (SP) 800-140Dr1 (May 2022) https://doi.org/10.6028/NIST.SP.800-140Dr1\n\n## How to Cite this NIST Technical Series Publication:\n\nCalis A (2023) Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods: CMVP Validation Authority Updates to ISO/IEC 24759. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-140Dr2. https://doi.org/10.6028/NIST.SP.800-140Dr2\n\n## Author ORCID iDs\n\nAlexander Calis: 0000-0003-1937-8129\n\n## Contact Information\n\nsp800-140-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe approved sensitive security parameter generation and establishment methods listed in this publication replace the ones listed in International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 19790 Annex D and ISO/IEC 24759 paragraph 6.16, within the context of the Cryptographic Module Validation Program (CMVP). As a validation authority, the CMVP may supersede Annex D in its entirety. This document also supersedes SP 800-140Dr1."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 IR.L2-3.6.2 (NIST 3.6.2)?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n3.6.2 | Potential Effects of Deficiencies on Meeting System Mission | Potential Effects of Deficiencies on Meeting System Mission | ... 3.6.2 Potential Effects of Deficiencies on Meeting System Mission - The impact of the identified deficiencies on completing the system mission must be determined."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "nist_control": "3.6.2", "cmmc_practice_id": "IR.L2-3.6.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Audit and Evaluation of Computer Security provide? (Part 4)"}, {"role": "assistant", "content": "ional units:\n\nOffice of Standard Reference Data — Office of Information Activities — Office of Technical Publications — Library —\nOffice of International Standards — Office of International Relations.\n' Headquarters and Laboratories at Gaithersburg, Maryland, imless otherwise noted; mailing address Washington, D.C. 20234. ^ Located at Boulder, Colorado 80302. ona! Bureau oi i>ianaarg®\n\nOCT 2 6 1977\n\n- COMPUTER SCIENCE & TECHNOLOGY:\n\n>cioo\n\n.)^^\n\n1)6\n\nAudit and Evaluation\nof Computer Security ^\n\nProceedings of the NBS Invitational Workshop\nheld at Miami Beach, Florida, March 22-24, 1977\n\nEdited by:\n\nZella G. Ruthberg\n\nInstitute for Computer Sciences and Technology\nNational Bureau of Standards\nWashington, D. C. 20234\n\nRobert G. McKenzie\n\nGeneral Accounting Office\nWashington, D. C. 20548\n\nSession Chairpersons;\n\nWilliam E. Perry\n\nC. O. Smith\n\nBlake Greenlee\nCarl Hammer\nW. H. Murray\nClark Weissman\nLeonard 1. Krauss\n\nJerry FitzGerald\nRichard D. Webb\nHart J. Will\n\n^^^^^^ °' oo,\n\nU.S. DEPARTMENT OF COMMERCE, Juanita M. Kreps, Secretary\n\nDr. Sidney Harman, Under Secretary\nJordan J. Baruch, Assistant Secretary for Science and Technology\nU A . NATIONAL BUREAU OF STANDARDS, Ernest Ambler, Acting Director\n\nIssued October 1977\n\n\fReports on Computer Science and Technology\n\nThe National Bureau of Standards has a special responsibility within the Federal\nGovernment for computer science and technology activities. The programs of the\nNBS Institute for Computer Sciences and Technology are designed to provide ADP\nstandards, guidelines, and technical advisory services to improve the effectiveness of\ncomputer utilization in the Federal sector, and to perform appropriate research and\ndevelopment efforts as foundation for such activities and programs. This publication\nseries will report these NBS efforts to the Federal computer community as well as to\ninterested specialists in the academic and private sectors."}], "metadata": {"source": "Audit and Evaluation of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nThe PIV System protects the trustworthiness of the PIV Card data objects through PIV Card access rules and digital signatures. Overall trust in the execution of a PIV authentication mechanism is also dependent on correct operation of the PIV Card, the PACS, and the PIV Card validation infrastructure, and, to a degree, on protecting the confidentiality, integrity, and availability of the communication channels among them. Attacks may, therefore, be directed against any of these components, with varying difficulty and potential impact.\n\n9 Secure messaging is an optional mechanism specified in [SP 800-73] that provides confidentiality and integrity protection for the card commands that are sent to the card as well as for the responses received from the PIV Card.\n\nThe PIV and PACS systems are complex, and this brief discussion has focused on properties of the PIV Card. A number of other attack vectors have not been discussed in detail, including sophisticated technical attacks against the integrity of the PIV Card, PIV System, or PACS components, and cryptanalysis of the PIV cryptographic algorithms. While the impact of successful attacks such as these could be moderate to high, the probability of success is believed to be extremely low."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "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 Planning?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\nnd sensitive data are loaded into the manufactured IC. Standard data are generic and mostly available open source, but the sensitive data are anything whose disclosure would compromise IP or security.\nFor example, keys of crypto modules or logic locking keys are sensitive data. 7. Deployment and Use: This stage includes delivering the IC to customers and using the IC. Many hardware vulnerabilities are exploited at this stage. 8. End of Life: End-of-life for an IC is the stage where the manufacturer no longer sells or manufactures IC [8]. This is often because of technological advancements when new ICs exhibiting better performance have been launched. When a chip reaches its end-of-life, the deployed chips are gradually replaced and discarded. These discarded chips are"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nutomated means where we do tie it into our backend account management system so that, truly, people aren't getting access to things before they've taken that training and signed the rules of behavior.\nSo, automation is key because the level of effort for, particularly, smaller agencies, where they may not have access to tools or there's a single person, is really impactful and inefficient.' (S11)\n\n| Type of Data | Example Responses | Number Participants |\n|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|\n| Security incidents | 'We also need incidents more granularly analyzed and categorized as to the types of human actions/inactions that contributed, and who, so we can adjust both general training and targeted follow-up training with individuals (i.e."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "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 Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 5)"}, {"role": "assistant", "content": "and 'need not' indicate a course of action permissible within the limits of the publication. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical, or causal.\n## Disclaimer\n\nThis publication offers general guidance and is provided for informational purposes. This publication should not be construed or relied upon as legal advice or guidance. This document does not modify the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Health Information Technology for Economic and Clinical Health (HITECH) Act, or any other federal law or regulation. The participation of other federal organizations with the National Institute of Standards and Technology (NIST) in the development of this Special Publication does not and shall not be deemed to constitute the endorsement, recommendation, or approval by those organizations of its contents. The use of this publication or any other NIST publication does not ensure or guarantee that an organization will be compliant with the Security Rule. ## 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": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators provide? (Part 9)"}, {"role": "assistant", "content": "afeguards should be in place to protect the confidentiality and integrity of data in transit. If a resource cannot provide this functionality natively, a separate PEP component may be necessary. - II.\nAccess to individual enterprise resources is granted on a per -session basis. In an ideal zero trust architecture, every unique operation would undergo authentication and authorization before the operation is performed. For example, a delete operation following a read operation to a database should trigger an additional authentication and authorization check. This level of granularity may not always possible and other mitigating solutions such as logging and backups, may be needed to detect and recover from unauthorized operations. Enterprise administrators will need to plan how to enforce fine grain access policies on individual resources. If the security tools used by\n\nthe enterprise do not allow this, other solutions such as logging, versioning tools, or backups may help achieve the desired access control outcome and manage this risk. - III. Access to resources is determined by dynamic policy-including the observable state of client identity, application/service, and the requesting asset-and may include other behavioral and environmental attributes. In zero trust, the default behavior for all resources is to deny all connections and only accept connections that are explicitly allowed by policy. Those authorized to access the resource must still authenticate themselves and prove they meet the enterprise policy to be granted the session. This may include meeting requirements such as client software versions, patch level, geolocation, historical request patterns, etc. Note that it may not be possible to perform all checks at the time of each access request, some policy check may be performed on an independent schedule (e.g., daily software versioning checks). - IV."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nDocumentation captures information potential customers and others in the ecosystem may need to know about the IoT devices and ways in which it, and associated data and systems, can be secured. Such documentation is also often necessary prior to purchase and throughout the IoT device's lifecycle for the customer and others in the ecosystem (e.g., auditors and assessors). This documentation supports the appropriate treatment of risk, compliance, and assurance from internal and external perspectives when the IoT device and associated systems are implemented within the customer environment. As shown in Figure 1, documentation acts as a pillar of support for other non-technical capabilities. This is because other non-technical capabilities, including those in the IoT non-technical supporting baseline, will use the information captured via documentation to customize their delivery."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\ns, Symbols and Abbreviations ............................................................... | 3. Definitions, Symbols and Abbreviations ...............................................................\n| 2 |\n| | 3.1 | Definitions........................................................................................................................ | 2 |\n| | 3.2 | Symbols and Abbreviations ............................................................................................. | 9 |\n| 4. Overview of Key-Establishment Schemes........................................................... | 4. Overview of Key-Establishment Schemes........................................................... | 4. Overview of Key-Establishment Schemes..........................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Planning?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\n## Report on the Design-A-Thon: Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness\n\n## Report on the Design-A-Thon: Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness\n\nFagan M, Haney J, Eliot D, Cuthill B, Rigopoulos K (2025) Report on the Design-A-Thon: Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8558. https://doi.org/10.6028/NIST.IR.8558"}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national 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\nThis section describes the basic cryptographic elements that support the development of the keyestablishment schemes specified in this Recommendation. The schemes described herein are based upon the correct implementation of these elements."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events provide? (Part 4)"}, {"role": "assistant", "content": "curity Framework in April 2018 to help organizations better manage and reduce cybersecurity risk to critical infrastructure and other sectors. The framework core contains five functions, listed below.\n-  Identify - develop an organizational understanding to manage cybersecurity risk to systems, people, assets, data, and capabilities\n-  Protect - develop and implement appropriate safeguards to ensure delivery of critical services\n-  Detect - develop and implement appropriate activities to identify the occurrence of a cybersecurity event\n-  Respond - develop and implement appropriate activities to take action regarding a detected cybersecurity incident\n-  Recover - develop and implement appropriate activities to maintain plans for resilience and to restore any capabilities or services that were impaired due to a cybersecurity incident\n\n\n\nFor more information, see the Framework for Improving Critical Infrastructure Cybersecurity v1.1. Applying the Cybersecurity Framework to data integrity, this practice guide informs organizations of how to quickly detect and respond to data integrity attacks by implementing appropriate activities that immediately inform about the data integrity events. The NCCoE developed and implemented a solution that incorporates multiple systems working in concert to detect an ongoing data integrity cybersecurity event. Additionally, the solution provides guidance on how to respond to the detected event. Addressing these functions together enables organizations to have the necessary tools to act during a data integrity attack. The NCCoE sought existing technologies that provided the following capabilities:\n\n- event detection\n- integrity monitoring\n- logging\n- reporting\n- mitigation and containment\n- forensics/analytics\n\n-  While the NCCoE used a suite of commercial products to address this challenge, this guide does not endorse these particular products, nor does it guarantee compliance with any regulatory initiatives."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\niving privacy inquiries from the public. Organizations identify and select the set of common controls and allocate those controls to the organizational entities designated as common control providers.\nCommon controls may differ based upon a variety of factors, such as hosting location, system architecture, and the structure of the organization. The organization-wide list of common controls takes these factors into account. Common controls can also be identified at different levels of the organization (e.g., corporate, department, or agency level; bureau or subcomponent level; or individual program level). Organizations may establish one or more lists of common controls that can be inherited by information systems. A requirement may not be fully met by a common control. In such cases, the control is considered a hybrid control and is noted as such by the organization, including specifying which parts of the control requirement are provided for inheritance by the common control and which parts are to be provided at the system level."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Ordered t-way Combinations for Testing State-based Systems:\n\nVulnerability and fault detection often depend on the specific order of inputs that establish states which eventually lead to a failure. That is, many software processes are not deterministic functions where an input produces the same output whenever the process is invoked irrespective of previous invocations. This is particularly true of real-time systems, which are designed to run continuously, maintain states, and respond to a changing series of inputs. Such systems are typically driven by a loop function that accepts input values, processes and responds to those inputs, and updates its current state. Examples include network protocols and data servers. The system state may change, depending on input, and the system may subsequently respond differently to the same input. That is, the response of the process to a particular set of input values may depend on its current state, such as whether a communication protocol is in a listen or connection-open state. The current state depends on the order of input values that were contained in previously received packets. The same sort of statedependent behavior occurs in many other types of systems as well."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide?"}, {"role": "assistant", "content": "\n\n\n\nHoward Lutnick, Secretary of Commerce\n\n\n\nProtecting Controlled Unclassified Information (CUI): NIST Special Publication 800-171, Revision 3 Small Business Primer\n\n## Purpose of this Primer\n\nThis guide provides small businesses with an overview of NIST Special Publication (SP) 800-171 Revision 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations . The following pages contain:\n\n- An overview of foundational components of SP 800-171\n- A list of frequently asked questions and their answers\n- Tips for getting started\n- Related resources\n\n## What is Controlled Unclassified Information (CUI)?*\n\nCUI is information the government creates or possesses, or that an entity creates or possesses on behalf of the government, that law, regulation, or governmentwide policy requires you to take technical and operational steps to protect. Systems that process, store, and transmit CUI often support government programs involving sensitive critical assets. As part of a contractual agreement with the federal government, or possibly with other organizations like municipal governments, prime contractors, universities, etc., you will likely be required to demonstrate you are taking adequate measures to protect CUI."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n.................. | 50 |\n| 5.3.3 | PR.AC-4: Access Permissions and Authorizations are Managed, Incorporating the Principles of Least Privilege and Separation of Duties .........................\n50 | |\n| 5.3.4 | PR.AC-7: Users, Devices, and Other Assets are Authenticated (e.g., single-factor, multi-factor) Commensurate with the Risk of the Transaction (e.g., Individual Security and Privacy Risks and Other Organizational Risks) | 50 |\n| 5.3.5 | PR.DS-1: Data-at-Rest is Protected......................................................................... | 51 |\n| 5.3.6 | PR.DS-6: Integrity Checking Mechanisms are Used to Verify Software, Firmware, and Information Integrity ..................................................................... | 51 |\n| 5.3.7 | PR.IP-4: Backups of Information are Conducted, Maintained, and Tested............ | 51 |\n| 5.3.8 | PR.MA-1: Maintenance and Repair of Organizational Assets are Performed and Logged, with Approved and Controlled Tools ...................................... | 51 |\n| 5.3.9 | PR.MA-2: Remote Maintenance of Organizational Assets is Approved, Logged, and Performed in a Manner that Prevents Unauthorized Access............... | 51 |\n| 5.3.10 | DE.AE-1: A Baseline of Network Operations and Expected Data Flows for Users Systems is Established and Managed................................................... | and 52 |\n| 5.3.11 | DE.AE-2: Detected Events are Analyzed to Understand Attack Targets And Methods | |"}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines provide? (Part 9)"}, {"role": "assistant", "content": "ibutions\nand review. The authors would also like to acknowledge the past contributions of Donna\nF. Dodson, Elaine M. Newton, Ray A. Perlner, W. Timothy Polk, Emad A. Nabbus, Paul A. Grassi, Michael E.\nGarcia, Kaitlin Boeckl, Joni Brennan, Ellen Nadeau, Ben Piccarreta, and\nDanna Gabel O’Rourke. vi\n\n\fNIST SP 800-63-4\nJuly 2025\n\n1. Introduction\n\nThis section is informative. Digital Identity Guidelines\n\nThe rapid proliferation of online services over the past few years has heightened the\nneed for reliable, secure, and privacy-protective digital identity solutions. A digital\nidentity is always unique in the context of an online service. However, a person could\nhave multiple digital identities and, while a digital identity could relay a unique and\nspecific meaning within the context of an online service, the real-life identity of the\nindividual behind the digital identity might not be known. When confidence in a person’s\nreal-life identity is not required to provide access to an online service, organizations can\nuse anonymous or pseudonymous accounts. In all other use cases, a digital identity is\nintended to establish trust between the holder of the digital identity and the person,\norganization, or system interacting with the online service. However, this process can\npresent challenges. There are multiple opportunities for mistakes, miscommunication,\nand attacks that fraudulently claim another person’s identity. Additionally, given the\nbroad range of individual needs, constraints, capacities, and preferences, online services\nmust be designed with flexibility and customer experience in mind to support broad and\nenduring participation and access to online services. Digital identity risks are dynamic and exist along a continuum. Consequently, a digital\nidentity risk management approach should seek to manage risks using outcome-based\napproaches that are designed to meet the organization’s unique needs."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 9)"}, {"role": "assistant", "content": "eats can arise from attack vectors unleashed by malicious actors during SSC activities as well as defects introduced when due diligence practices are not followed by legitimate actors during the SDLC.\nExecutive Order (EO) 14028, NIST's Secure Software Development Framework (SSDF) [2], other government initiatives, and industry forums have discussed the security of SSC and provided a roadmap to enhance the security of all deployed software. This document uses this roadmap as the basis for developing actionable measures to integrate the various building blocks of SSC security assurance into CI/CD pipelines to enhance the preparedness of organizations to address SSC security in the development and deployment of cloud-native applications. To demonstrate that the SSC security integration strategies for CI/CD pipelines meet the objectives of SSDF, a mapping of these strategies to the high-level practices in the SSDF has also been provided. Building a robust SSC security edifice requires various artifacts, such as a software bill of materials (SBOM) and frameworks for the attestation of software components. Since the specification of these artifacts, their mandatory constituents, and the requirements that processes using them must satisfy are continually evolving through projects in government organizations and various industry forums, they are beyond the scope of this document. ## 1. Introduction\n\nCloud-native applications typically consist of multiple loosely coupled services or microservices and are sometimes accompanied by an integrated application service infrastructure, such as a service mesh. The applications are developed through an agile software development life cycle (SDLC) paradigm called DevSecOps, which uses flow processes called Continuous Integration/ Continuous Delivery (CI/CD) pipelines."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\nperform provisioning, enrollment, and finalization. + Fewer credentials. A single PIV Card provides a small set of authentication methods that are applicable to many applications and in many contexts.\nThis means significantly fewer identity credentials that need to be issued and significantly fewer account enrollments."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n2. Identify reasonably anticipated threats. The regulated entity identifies the potential threat events and threat sources that are applicable to it and its operating environment. The list of threat events and threat sources should include reasonably anticipated and probable human and natural incidents that can negatively impact the regulated entity's ability to protect ePHI. Use the information gathered from Step 1 (i.e., the preparation step) to identify reasonably anticipated threats to ePHI. Be sure to consider threats to the confidentiality, integrity, and availability of ePHI via phishing, ransomware, or insider threat."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.3.4. 3.3.4."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\nPrevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. 1. Ensure that you have a current version of Oracle Java. You must install both the Java Runtime Environment (JRE) and the Java Cryptography Extension (JCE). 2. Download and run the JRE installer. 3. Click Install. 4. Download the JCE, and extract the files. 5. Copy the local\\_policy.jar and US\\_export\\_policy.jar files to /lib/security/Unlimited/ and /lib/security/Limited in the Java installation directory. 6. Run install-server-windows-amd64. 7. Select the Java runtime that was just installed. 8. Click OK."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 9)"}, {"role": "assistant", "content": "| 5.2.1 MACTag Computation for Key Confirmation .................................................\n| 20 |\n| | | 5.2.2 MACTag Verification for Key Confirmation................................................... | 21 |\n| 5.3 | Random Number Generation......................................................................................... | Random Number Generation......................................................................................... | 21 |\n| 5.4 | Nonce............................................................................................................................ | Nonce............................................................................................................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 10)"}, {"role": "assistant", "content": "5\n\n65\n\n66\n\n66\n\n66\n\n66\n\n67\n\n68\n\n68\n\n69\n\n71\n\n76\n\n76\n\n79\n\n81\n\n87\n\n87\n\n87\n\n88\n\n89\n\n90\n\nv\n\n\fNIST SP 800-63B-4\nJuly 2025\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nAppendix B.\nSyncable Authenticators . . . . . . . . . . . . . . . . . . . . . . . . B.1. B.2. B.3. B.4. B.5. B.6. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cloning Authentication Keys . . . . . . . . . . . . . . . . . . . . . . . . Implementation Requirements\n\n. . . . . . . . . . . . . . . . . . . . . . Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Considerations\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . Appendix C. List of Symbols, Abbreviations, and Acronyms . . . . . . . . . . . . 91\n\n91\n\n91\n\n92\n\n94\n\n95\n\n96\n\n99\n\nAppendix D. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102\n\nAppendix E. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117\n\nList of Tables\nSummary of requirements by AAL . . . . . . . . . . . . . . . . . . . . Table 1. Summary of secrets (non-normative)\n. . . . . . . . . . . . . . . . . . Table 2. Authenticator threats . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. Table 4. Mitigating authenticator threats . . . . . . . . . . . . . . . . . . . . . . . . . . . Syncable authenticator threats, challenges, and mitigations\nTable 5. List of Figures\nFig. 1. Fig. 2. Fig. 3. Transfer of secret to primary device . . . . . . . . . . . . . . . . . . . . Transfer of secret to out-of-band device . . . . . . . . . . . . . . . . . . Usability considerations by authenticator type . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 3)"}, {"role": "assistant", "content": "aft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Email: SP800-56b\\_comments@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThis Recommendation specifies key-establishment schemes using integer factorization cryptography (in particular, RSA). Both key-agreement and key transport schemes are specified for pairs of entities, and methods for key confirmation are included to provide assurance that both parties share the same keying material. In addition, the security properties associated with each scheme are provided."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.4.4 of [SP800-63] for more information about the DIAS."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.4.4", "cmmc_practice_id": "CM.L2-3.4.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.4.2 Handling Repeat Clickers... 3.4.2 Handling Repeat Clickers... 3.4.2 Handling Repeat Clickers\n\nWe also asked participants what happens to repeat clickers in their organization (those who repeatedly fall victim to phishing)."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "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 is CMMC practice AC.L2-3.1.10 (NIST 3.1.10)?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.1.10 cis: benchmark: - 2."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "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 Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\nenterprise patch management; patch; risk management; update; upgrade; vulnerability management. Leadership at all levels of the organization, business/mission owners, and security/technology management teams should jointly create an enterprise patch management strategy that simplifies and operationalizes patching while also improving its reduction of risk. This will strengthen organizational resiliency to active threats and minimize business and mission impacts. This publication provides recommendations for enterprise patch management planning. | Executive Summary..................................................................................................... | Executive Summary..................................................................................................... | Executive Summary....................................................................................................."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## 3.2. Identify Hardware Threats"}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide? (Part 8)"}, {"role": "assistant", "content": "sions. This documentation is essential when examining the security considerations for organizational information systems with respect to the potential impact on an organization's mission and business.\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3. Figure 3: Security Control Selection Process\n\n\n\n## 5 Assurance\n\nAppendix E in SP 800-53 Revision 4 provides an update to guidance regarding security assurance. This section outlines methods for agencies to establish measures of confidence that the implemented security controls provide the security capability required to protect critical missions and business operations. The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. Appendix E provides three tables that identify specific assurance-related controls that are included in the low-, moderate-, and high-impact baselines described in Appendix D."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.2.3. 3.2.3. 3.2.3)."}], "metadata": {"source": "Guidelines for Media Sanitization", "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 guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-218A\n\n## Secure Software Development Practices for Generative AI and Dual-Use Foundation Models\n\nAn SSDF Community Profile\n\nHarold Booth Murugiah Souppaya Apostol Vassilev Michael Ogata Martin Stanley\n\nKaren Scarfone\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-218A\n\n\n\n## NIST Special Publication 800 NIST SP 800-218A\n\n## Secure Software Development Practices for Generative AI and Dual-Use Foundation Models\n\nAn SSDF Community Profile\n\nHarold Booth Murugiah Souppaya Apostol Vassilev\n\nComputer Security Division Information Technology Laboratory\n\nMichael Ogata\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nMartin Stanley Cybersecurity and Infrastructure Security Agency (CISA)\n\nKaren Scarfone Scarfone Cybersecurity\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-218A\n\nJuly 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."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Guidelines on Mobile Device Forensics:\n\n## 3.3.1 Software and Hardware Based Methods\n\n## 3.3.2 Investigative Methods\n\n- [GSM04] IMEI Allocation and Approval Guidelines, Version 3.3.0, GSM Association, Permanent Reference Document TW.06, December 2004, <URL: http://www.gsmworld.com/documents/twg/tw06.pdf>. - [GSM05] GSME Position On Data Retention - Implications for The Mobile Industry, GSM Europe, GSM Association, 23 August 2005, <URL: http://www.gsmworld.com/gsmeurope/documents/positions/2005/gsme\\_position\\_d ata\\_retention.pdf#search=%22GSME%20POSITION%20ON%20DATA%20RET ENTION%22>. - [Haa04] Job de Haas, Reverse Engineering ARM Based Devices, Black Hat Europe, May 2004, <URL: https://www.blackhat.com/presentations/bh-europe-04/bh-eu-04dehaas/bh-eu-04-dehaas.pdf>. - [Hoo11] Andrew Hoog, Katie Strzempka, 2011, iPhone and iOS Forensics: Investigation, Analysis and Mobile Security for Apple iPhone, iPad and iOS Devices, Elsevier, Jul 25, 2011>. - [ITU06] ITU-T (2006), Automatic International Telephone Credit Cards, International Telecommunications Union, Telecommunication Standardization Sector (ITU-T), Recommendation E.118, (02/01). - [INT06] Mobile Phone Forensics, 47th EWPITC meeting - Final report, European Working Party on IT Crime, INTERPOL, September 7, 2006. - [Jan09] Wayne Jansen, Aurélien Delaitre, Mobile Forensic Reference Materials: A Methodology and Reification, NIST Interagency Report IR-7617, October 2009, <URL: http://csrc.nist.gov/publications/nistir/ir7617/nistir-7617.pdf>. - [Jon10] Kevin Jonkers, The forensic use of mobile phone flasher boxes5, digital investigation 6 (2010) 168-178, <URL: http://www.sciencedirect.com>. - [Kat10] Eric Katz, A Field Test of Mobile Phone Shielding Devices, 2010, College of Technology Masters Thesis, Paper 33, <URL: http://docs.lib.purdue.eud/techmasters/33>."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "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 Configuration Management?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "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 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 require for Configuration Management?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| 5.2.4. Device and Media Controls (§ 164.310(d)).................................................................................63 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 5.3.1. Access Control (§ 164.312(a)).....................................................................................................65 |\n| 5.3.2. Audit Controls (§ 164.312(b)).....................................................................................................69 |\n| 5.3.3. Integrity (§ 164.312(c))...............................................................................................................71 |\n| 5.3.4. Person or Entity Authentication (§ 164.312(d)).........................................................................73 |\n| 5.3.5. Transmission Security (§ 164.312(e)(1)).....................................................................................75 |\n| 5.4.1."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "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 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 does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n## Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule\n\n## Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule\n\nMarron J (2024) Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-66r2. https://doi.org/10.6028/NIST.SP.800-66r2"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "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 Ordered t-way Combinations for Testing State-based Systems provide? (Part 9)"}, {"role": "assistant", "content": "arting block is reset to 0 {0 = start from last position, 1 = start from block 0}. A read or write test processes from the starting block indicated by p 2 and continues to the end of the file.\nSo tests 1 to 4 represent 'read from last read position,' 'read from start,' 'write from last write position,' and 'write from start.' State 1 is entered when the file is filled by writing to the end after rewinding to start. The failure represented by state 2 is only exposed when a write is attempted on a file starting from the end. Then, as noted previously, running tests in the order 1..6 will not detect the error. However, when test 4 is run before test 3, the error will be detected because a write is attempted from the last position (end of file), as indicated by the value of p 2 . When tests are executed in sequence with each individual t-way combination considered an event, an order of tway combinations containing s combinations input in sequence with possible interleaving is an s -sequence of tway combinations. For example, a 2-sequence of 3-way combinations could be\n\n\n\nand a 3-sequence of 2-way combinations could be\n\n\n\nAn OCC covers all ssequences of t -way combinations of the v values of the p parameters. Because a t -tuple is included s times in an ssequence, and the number of t -way combinations of p parameters is 𝐶𝐶 ( 𝑝𝑝 , 𝑡𝑡 ), for v t settings of each combination, the total number of combination sequence tuples to be covered is\n\n\n\nThe number of combination sequences to be covered grows rapidly with s and t , so methods for the efficient construction of OCCs are of interest. Example. Fig. 6 shows a test array that covers all 2way combinations of values for four parameters, as well as all 2-sequences of 2-way parameter combinations. Fig.6."}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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 Personnel Security?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n| [OPM] | U.S. Office of Personnel Management (2018) Guidance for Identifying, Addressing and Reporting Cybersecurity Work Roles of Critical Need. (U.S. Office of Personnel Management, Washington, DC). Available at https://chcoc.gov/content/guidance-identifying-addressing-and-reporting- cybersecurity-work-roles-critical-need |\n|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [SANS] | SANS (2021). 2021 SANS Security Awareness Report: Managing Human Cyber Risk. Available at https://www.sans.org/security-awareness- training/resources/reports/sareport-2021/ |\n| [SMAC] | CIO.gov (2021) About the SACC and SMAC Councils . Available at https://www.cio.gov/about/members-and-leadership/SMACC/ |\n| [STEWART] | Stewart, G, Lacey, D (2012) Death by a Thousand Facts: Criticising the Technocratic Approach to Information Security Awareness. Information Management &Computer Security 20(1):29-38. |\n| [WILSON] | Wilson M, Hash J (2003) Building an Information Technology Security Awareness and Training Program. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-50."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.2.3. 3.2.3. 3.2.3."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer provide? (Part 9)"}, {"role": "assistant", "content": "NIST does not necessarily endorse the views expressed or the facts presented on those sites. Further, NIST does not endorse any commercial products that may be advertised or available on these sites.\nht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Introductory Tips for Implementers\n\n\n\n## What's New in SP 800 -171, Revision 3? ## SP 800-171, Revision 3 was published in May 2024. Significant changes include:\n\n## Updates to the Security Requirements and Families\n\n- Based on NIST SP 800-53, Revision 5 and the NIST SP 800-53B moderate impact control baseline. - Applies updated tailoring criteria addressing stakeholder feedback (adding new, consolidating, and withdrawing requirements). - Includes increased specificity in security requirements. - Introduces organization-defined parameters (ODP) to increase flexibility to better manage organizationspecific risks. ## Additional Revision 3 Resources\n\n- A CUI overlay (.xlsx) showing the direct link between SP 800-53 and SP 800171, including NIST's tailoring decisions. - Transitioning your organization from implementation of Revision 2 to Revision 3? Review this detailed analysis of the changes between Revision 2 and Revision 3 (.xlsx). - The SP 800-171 security requirements in multiple formats (Excel, JSON, and online) through the NIST Cybersecurity and Privacy Reference Tool. ht ps:/\n\ncsrc.nist.gov/projects/protecting-control ed-unclas ified-information\n\n## Key Terms\n\n\n\n\n\nControl Baseline: A set of controls you can implement to meet strategic, legal, regulatory, or contractual security and privacy requirements and manage risk. Organization-Defined Parameters (ODPs) are included in certain security requirements. ODPs provide the flexibility and specificity needed by organizations to clearly define their CUI security requirements, given the diverse nature of their missions, business functions, operational environments, and risk tolerance."}], "metadata": {"source": "Protecting Controlled Unclassified Information (CUI)_ NIST Special Publication 800-171, Revision 3. Small Business Primer", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nThis paper presents a rigorous research plan to study automated response within the unique requirements of an AMI. The proposed solution will help utilities improve on services, operation costs, and reliability. Automated responses in AMI will reduce the maintenance cost for utilities, as it improves the ability to troubleshoot the distribution network by providing situational awareness. Moreover, automated response has the potential to significantly reduce the load on human operators by automatically managing low-level alarms generated by sensors in the network."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "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 1 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\ncybersecurity baseline; Internet of Things (IoT); IoT products; manufacturing; privacy; risk management; securable products; security requirements; software development; threat modelling. | 1. | Government actions to support strengthening IoT cybersecurity need to be coordinated with industry. |\n|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | The use of robust frameworks and the adoption of open standards are crucial for effectively managing risks across heterogeneous environments. |\n| 3 | The dynamic nature of threats requires more context aware inputs, more proactive tracking and mitigation measures, and more examination into the inputs of the threat modeling approach. |\n| 4 | There are market opportunities to securely design the next wave of products with cybersecurity through end of life and instill incentives into the maintenance of existing products. |\n| 5 | The balance of shared responsibility between manufacturers and users for improving security varies by sector and needs the right incentives for both. |\n| 6 | There are broad challenges to integrating privacy objectives into IoT cybersecurity risk management. |\n| 7 | There is an increased awareness for evolving cybersecurity responsibilities across the players of the IoT ecosystem from manufacturers to users of the ecosystem. |\n\n- Broaden the discussions from a focus on the IoT system device component to considerations of entire IoT products (and connected products) to better reflect the wide variety of applications and use cases that exist. - Develop the relationship between risk assessment and threat modeling activities."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nThis publication provides a catalog of security and privacy controls for information systems and\norganizations to protect organizational operations and assets, individuals, other organizations,\nand the Nation from a diverse set of threats and risks, including hostile attacks, human errors,\nnatural disasters, structural failures, foreign intelligence entities, and privacy risks. The controls\nare flexible and customizable and implemented as part of an organization-wide process to\nmanage risk. The controls address diverse requirements derived from mission and business\nneeds, laws, executive orders, directives, regulations, policies, standards, and guidelines. Finally,\nthe consolidated control catalog addresses security and privacy from a functionality perspective\n(i.e., the strength of functions and mechanisms provided by the controls) and from an assurance\nperspective (i.e., the measure of confidence in the security or privacy capability provided by the\ncontrols). Addressing functionality and assurance helps to ensure that information technology\nproducts and the systems that rely on those products are sufficiently trustworthy. Organizations must exercise due diligence in managing information security and privacy risk. This\nis accomplished, in part, by establishing a comprehensive risk management program that uses\nthe flexibility inherent in NIST publications to categorize systems, select and implement security\nand privacy controls that meet mission and business needs, assess the effectiveness of the\ncontrols, authorize the systems for operation, and continuously monitor the systems. Exercising\ndue diligence and implementing robust and comprehensive information security and privacy risk\nmanagement programs can facilitate compliance with applicable laws, regulations, executive\norders, and governmentwide policies."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 additional guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide? (Part 7)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 21 |\n| 5. Hash and eXtendable-Output Functions (XOFs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n| 23 |\n| 5.1. Specification of Ascon-Hash256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 23 |\n| 5.2. Specification of Ascon-XOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 25 |\n| 5.3. Specification of Ascon-CXOF128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 28 |\n| 5.4. Streaming API for XOF............................................................ | 30 |\n| 5.5. Security Strengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 31 |\n| 6. Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 31 |\n\n## Appendix A. Implementation Notes.................................................... 35\n\nA.1. A.2. A.3. Conversion\n\nFunctions ............................................................ Implementing with\n\nIntegers ..................................................... 35\n\n36\n\nPrecomputation .................................................................. 39\n\n## Appendix B. Determination of the Initial Values....................................... 40\n\n## List of Tables\n\n| Table 1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 3 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| Table 2."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Karen Scarfone Matthew Smith\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\n\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Applied Cybersecurity Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nMatthew Smith Huntington Ingalls Industries Annapolis Junction, MD\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nMay 2020\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259A 23 pages (May 2020)\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 7)"}, {"role": "assistant", "content": ".................................16 |\n| 5.1.2. Secure Pull-Push Operations on Repositories............................................................................17 |\n| 5.1.3.\nIntegrity of Evidence Generation During Software Updates......................................................18 |\n| 5.1.4. Secure Code Commits ................................................................................................................19 |\n\n| 5.2.1. Secure CD Pipeline -Case Study (GitOps) ................................................................................21 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 6. Summary and Conclusions............................................................................................................23 |\n| References.......................................................................................................................................24 |\n| Appendix A. Mapping of Recommended Security Tasks in CI/CD Pipelines to Recommended High-Level Practices in SSDF..............................................................................................................................26 |\n| B."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nECURITY AWARENESS APPROACHES..................................................................... | 3 SECURITY AWARENESS APPROACHES.....................................................................\n| 3 |\n| 3.1 ANNUAL REQUIRED TRAINING............................................................................................. | 3.1 ANNUAL REQUIRED TRAINING............................................................................................. | |\n| .................................................................................... | .................................................................................... | 3 |\n| 3.1.1 | Required Training Fulfillment | 3 |\n| 3.1.2 | Obtaining Training Content........................................................................................"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "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 High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\now software quality. - Granular access control on databases: Since different research groups may have a need to know for different portions of data, granular access control capabilities are necessary.\nAccess control requirements may need to be dynamically adjusted as some scientific experiments may increase data needs based on the outcome of experiments."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "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 Guide for Developing Security Plans for Federal Information Systems:\n\n|\n| 1.1 BACKGROUND............................................................................................................................\n| 1 |\n| 1.2 TARGET AUDIENCE.................................................................................................................... | 1 |\n| 1.3 ORGANIZATION OF DOCUMENT.................................................................................................. | 1 |\n| 1.4 SYSTEMS INVENTORY AND FEDERAL INFORMATION PROCESSING STANDARDS (FIPS 199) | ...... 2 |\n| 1.5 MAJOR APPLICATIONS, GENERAL SUPPORT SYSTEMS, AND MINOR APPLICATIONS | .................. 2 |\n| 1.6 OTHER RELATED NIST PUBLICATIONS ..................................................................................... | 3 |\n| 1.7 SYSTEM SECURITY PLAN RESPONSIBILITIES .............................................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography provide? (Part 4)"}, {"role": "assistant", "content": "lishment schemes based on the discrete logarithm problem over finite fields and elliptic curves, including several variations of Diffie-Hellman and Menezes-Qu-Vanstone (MQV) key establishment schemes.\n## Keywords\n\nDiffie-Hellman; elliptic curve cryptography; finite field cryptography; key agreement; key confirmation; key derivation; key establishment; MQV. ## Acknowledgements\n\nThe authors gratefully acknowledge the contributions on previous versions of this document by Mike Hopper, Don Johnson, Sharon Keller, Laurie Law, and Miles Smid. ## Conformance Testing\n\nConformance testing for implementations of this Recommendation will be conducted within the framework of the Cryptographic Algorithm Validation Program (CAVP) and the Cryptographic Module Validation Program (CMVP). The requirements of this Recommendation are indicated by the word 'shall.' Some of these requirements may be out-of-scope for CAVP or CMVP validation testing, and thus are the responsibility of entities using, implementing, installing or configuring applications that incorporate this Recommendation. ## Table of Contents\n\n| 1. Introduction.............................................................................................................. 1 | 1. Introduction.............................................................................................................. 1 | 1. Introduction.............................................................................................................. 1 | 1. Introduction.............................................................................................................."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.11 (NIST 3.1.11)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.1.11)\n\n3. 3.1.11 requires CSPs that collect or process biometric data to provide detailed,\npublicly available information about this process. 3.1.11."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.1.11", "cmmc_practice_id": "AC.L2-3.1.11", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 5)"}, {"role": "assistant", "content": "Farnham Jahanian ...............................................................................45 | | 6 | Security Challenges and Requirements for Control Systems in the Semiconductor Manufacturing Sector....................................................................................72 | | 7 | Keynote Speaker: Tom Dion.................................................................................................94 | | 8 | Application of Dynamic System Models and State Estimation Technology to the Cyber Security of Physical Systems.........................................................96 | | 9 | Challenges of Cybersecurity Research in a Multi-user Cyber-Physical Testbed .................................................................................................................................119 | | 10 | Security of power grids: a European perspective .................................................................135 | | 11 | Understanding the Role of Automated Response Actions to Improve AMI Resiliency .............................................................................................................................157 | | 12 | Cyber-Physical Systems Security for the Smart Grid ..........................................................189 | | 13 | State Estimation and Contingency Analysis of the Power Grid in a Cyber- Adversarial Environment .....................................................................................................215 | | 14 | False Data Injection Attacks in Smart Grid: Challenges and Solutions...............................241 | | 15 | Conclusion............................................................................................................................269 | [This page left intentionally blank.] ## 1."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Risk Assessment?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\n...................................................... | 5 |\n| 2.3.\n| Bilinear Pair Mapping.................................................................................................. | 7 |\n| 2.4. | Bilinear Pairing for Cryptography................................................................................ | 9 |\n| 3. | Identity-Based Encryption ..............................................................................................11 | |\n| 4. | Attribute-Based Encryption............................................................................................13 | |\n| 4.1. | Ciphertext-Policy Attribute-Based Encryption | ............................................................13 |\n| 4.2. | Key-Policy Attribute-Based Encryption ......................................................................18 | |\n| 5."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nCybersecurity education and awareness can provide critical support for the cybersecurity of digital products. Notably, the capability can inform and educate users about other cybersecurity capabilities, particularly technical capabilities. For example, cybersecurity education and awareness can guide users on creating strong access control credentials and permissions for products where such features are supported. Other information can be delivered using this capability as well, such as expectations for use of the product and other cybersecurity expectations, which can reduce the possibility of a risk being missed or otherwise unaddressed when the product is deployed."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "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 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 Digital Identity Guidelines provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental\norganizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\nNIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements\nNIST Technical Series Publication Identifier Syntax\n\n\fPublication History\n\nApproved by the NIST Editorial Review Board on 2025-04-28. Supersedes NIST SP 800-63-3 (June 2017; updated March 2, 2020) https://doi.org/10. 6028/NIST.SP.800-63-3\n\nHow to Cite this NIST Technical Series Publication\n\nTemoshok D, Galluzzo R, LaSalle C, Lefkovitz N, Regenscheid A, Choong YY, Proud-\nMadruga D, Gupta S (2025) Digital Identity Guidelines. (National Institute of Standards\nand Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-63-4. https://doi.org/10.6028/NIST.SP.800-63-4\n\nAuthor ORCID iDs\n\nDavid Temoshok: 0000-0001-6195-0331\nDiana Proud-Madruga: 0000-0002-8972-7809\nYee-Yin Choong: 0000-0002-3889-6047\nRyan Galluzzo: 0000-0003-0304-4239\nSarbari Gupta: 0000-0003-1101-0856\nConnie LaSalle: 0000-0001-6031-7550\nNaomi Lefkovitz: 0000-0003-3777-3106\nAndrew Regenscheid: 0000-0002-3930-527X\n\nContact Information\n\nmailto:dig-comments@nist.gov\n\nNational Institute of Standards and Technology\nAttn: Applied Cybersecurity Division, Information Technology Laboratory\n100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAdditional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/\nsp/800/63/4/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). NIST SP 800-63-4\nJuly 2025\n\nAbstract\n\nDigital Identity Guidelines\n\nThese guidelines cover the identity proofing, authentication, and federation of users\n(e.g., employees, contractors, or private individuals) who interact with government\ninformation systems over networks."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\n| 1. Document assumptions made during the development process and other expectations related to the IoT device, such as: a. Expected customers and use cases b. Physical use and characteristics c. Network access and requirements (e.g., bandwidth requirements) d. Data created and handled by the device e. Expected data inputs and outputs (including error codes, frequency, type/form, range of acceptable values, etc.) f. Assumed cybersecurity requirements for the IoT device g. Laws and regulations with which the IoT device and related support activities comply h. Expected lifespan, anticipated cybersecurity costs related to the IoT device (e.g., price of maintenance), and term of support 2. Document the device cybersecurity capabilities , such as those detailed within NISTIR 8259A, that are implemented within the IoT device and how to configure and use them. 3. Document device design and support considerations related to the IoT device, such as: 4 a. IoT platform 5 used in the development and operation of the IoT device and related documentation b. Protection of software and hardware components of the IoT device (e.g., secure boot, hardware root of trust, and secure enclave) c. Consideration of the known risks related to the IoT device and known potential misuses d. Secure software development and supply chain practices used e. Accreditation, certification, and/or evaluation results for cybersecurity-related practices | • This capability supports Information Dissemination and Education and Awareness. • Manufacturers and/or supporting entities should consider documentation throughout their development lifecycle in order to capture cybersecurity-relevant information when it is available so as to ensure access to this information when it is needed. Documentation will begin as internal resources for a manufacturer and/or supporting entity that can be used in various ways."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "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 Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThis session began with Lok Yan from DARPA's Microsystems Technology Office (MTO), whose portfolio includes the Automatic Implementation of Secure Silicon (AISS) program. Lok provided a high-level overview of why the semiconductor community needs to recognize security metrics. Meaningful metrics require assets, use cases, and threats to be clearly identified within the context of a threat model. The value of assets, associated potential threats, and the consequences of an asset's compromise must be quantifiable to support the design decisionmaking process. Understanding and identifying a minimum acceptable security baseline within the context of a particular use case would help bring various security metrics together. Due to the continuously evolving threat space, Lok emphasized that establishing an initial set of metrics and an associated minimum security baseline is not a one-time process. Rather, they must be continuously measured, monitored, and updated as assets, threats, vulnerabilities, and use cases evolve over time. Finally, security metrics could support decisions related to the threat and vulnerability space versus the time to test or implement countermeasures. More time must be allocated to implement and test countermeasures that address the most important threats and vulnerabilities for a particular use case. Jason Oberg, Cycuity CTO and co-founder, described how metrics can be used in the hardware security space based on his organization's experiences. Since different metrics are relevant to different people within an organization (e.g., metrics that work for a designer or tester may not translate to executives), there need to be different tiers of metrics based on the audience or user. For example, the CWE structure could be used to define security requirements that lead to associated security metrics."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process:\n\nThere may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities. The information in this publication, including\nconcepts and methodologies, may be used by federal agencies even before the completion of such\ncompanion publications. Thus, until each publication is completed, current requirements, guidelines, and\nprocedures, where they exist, remain operative. For planning and transition purposes, federal agencies\nmay wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Status Report on the First Round of the Additional Digital Signature Schemes for the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nir life cycle. Furthermore, Jonathan stressed the importance and continued need for public-private partnerships, like the Semiconductor Research Corporation and the Semiconductor Industry Association.\nHe also stressed the need for continued conversations concerning advanced metrology for supply chain trust and assurance, guidelines for security analytics and automation, vulnerability management across all product life cycles, and the use of machine learning in chip design and manufacturing."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.3. General Privacy Requirements . . . . . . . . . . . . . . . . . . . . . . .\n\n3.3.1. Privacy Risk Assessment . . . . . . . . . . . . . . . . . . . . . .\n\n3.3.2. Additional Privacy Protective Measures . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "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 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for 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 are the CMMC Level 3 requirements?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide? (Part 6)"}, {"role": "assistant", "content": "|\n| 4. Conclusion . . | . . . . . . . . . . . . . . . . . . . . . . . . . . | 18 |\n| References . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| Appendix A.\nList of Symbols, Abbreviations, and Acronyms | . | 26 |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | Table 1. Timeline of the NIST Post-Quantum Cryptography Standardization Process | 2 |\n| Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | Table 2. Fourth-round KEM candidates organized by category, with the candidate se- lected for standardization bolded and in blue . . . . . . . . . . . . . . . . | 4 |\n| Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | Table 3. Performance of BIKE in thousands of cycles on x86_64 [1] . . . | 6 |\n| Table 4. Performance of HQC in thousands of cycles on x86_64 [1] . . . | Table 4. Performance of HQC in thousands of cycles on x86_64 [1] . . . | 6 |\n| Table 5. Performance of Classic McEliece in thousands of cycles on x86_64 | Table 5."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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": "How does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 support CMMC certification?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nsystems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems.\nThis guideline is consistent with requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-172 Natl. Inst. Stand. Technol. Spec. Publ. 800-172, 84 pages (February 2021)\n\nCODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\nCertain commercial entities, equipment, or materials may be identified in this document to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nre IoT products (and connected products) to better reflect the wide variety of applications and use cases that exist. - Develop the relationship between risk assessment and threat modeling activities.\n- Address the different cybersecurity considerations among Information Technology (IT), Internet of Things (IoT), Operational Technology (OT), and Industrial Internet of Things (IIoT)\n- Identify insights, considerations, approaches, etc. for IoT based on the NIST Privacy Framework, NIST Cyber Physical Systems/IoT Framework, NIST Cybersecurity Framework 2.0, and the NIST Secure Software Development Framework."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\n## 4.2. Compute Node Sanitization\n\nExamples of compute node sanitization include:\n\nCompute node sanitization is highly recommended as the compute nodes are equipped with sophisticated hardware accelerators. Nevertheless, the process of sanitization must be carefully balanced with the goal of maximizing the utilization of HPC systems."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n------------------------------------------------------------------|\n| Symmetric-key algorithm | A cryptographic algorithm that uses secret keying material that is shared between authorized parties.\n|\n| Targeted security strength | The security strength that is intended to be supported by one or more implementation-related choices (such as algorithms, primitives, auxiliary functions, parameter sizes and/or actual parameters) for the purpose of instantiating a cryptographic mechanism. In this Recommendation, it is assumed that the targeted security strength of any instantiation of an approved key-establishment scheme has a value greater than or equal to 112 bits and less than or equal to 256 bits. |\n| Trusted association | Assurance of the integrity of an asserted relationship between items of information that may be provided by cryptographic or non- cryptographic (e.g., physical) means. Also see Binding. |\n| Trusted party | A party that is trusted by an entity to faithfully perform certain services for that entity. An entity may choose to act as a trusted party for itself. |\n| Trusted third party | A third party, such as a CA, that is trusted by its clients to perform certain services. (By contrast, the two participants in a key- establishment transaction are considered to be the first and second parties.) |"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.6.\n\n4.3.6. Verification Requirements . . . . . . . . . . . . . . . . . . . . .\n\n3.6. Redress Requirements"}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "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 Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| | Implement Roles and Responsibilities (PO.2): Ensure that everyone inside and outside of the organization involved in the SDLC is prepared to perform their SDLC-related roles and responsibilities throughout the SDLC."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Overview and Considerations of Access Control Based on Attribute Encryption provide? (Part 9)"}, {"role": "assistant", "content": "| List of Figures |\n| Fig. 1.\nP + (- P ) = P - P = 0 in an elliptic curve ............................................................................ | Fig. 1. P + (- P ) = P - P = 0 in an elliptic curve ............................................................................ | 4 |\n| Fig. 2. P + Q in an elliptic curve ................................................................................................. | Fig. 2. P + Q in an elliptic curve ................................................................................................. | 5 |\n| Fig. 3 . Basic process steps of the CP-ABE scheme..................................................................14 | Fig. 3 . Basic process steps of the CP-ABE scheme..................................................................14 | |\n| Fig. 4. Tree structure of an example access control policy........................................................15 | Fig. 4. Tree structure of an example access control policy........................................................15 | |\n| Fig. 5. Basic process steps of KP-ABE scheme........................................................................19 | Fig. 5."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM):\n\nConfigure platforms to allow the installation of organization-approved software only. 2. Verify the source of new software and the software's integrity before installing it. 3. Configure platforms to use only approved DNS services that block access to known malicious domains. 4. ... | • NIST SP 800-161r1, control SI-3 • ISO 27002:2022, control 8.7 • … |\n| … | | | |"}], "metadata": {"source": "NIST Cybersecurity Framework 2.0_ Quick-Start Guide for Cybersecurity Supply Chain Risk Management (C-SCRM)", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\n## Guide for Developing Security Plans for Federal Information Systems\n\nThe National Institute of Standards and Technology would like to acknowledge the authors of the original NIST Special Publication 800-18, Guide for Developing Security Plans for Information Technology System. The original document was used as the foundation for this revision. Additionally, thank you to all the NIST staff that reviewed and commented on the document. | EXECUTIVE SUMMARY.......................................................................................................... | VII |\n|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1. INTRODUCTION ........................................................................................................................ | 1 |\n| 1.1 BACKGROUND............................................................................................................................ | 1 |\n| 1.2 TARGET AUDIENCE.................................................................................................................... | 1 |\n| 1.3 ORGANIZATION OF DOCUMENT.................................................................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 6)"}, {"role": "assistant", "content": "tage is the birthplace of an Integrated Circuit (IC). At this stage, the goals and purpose of an integrated circuit (IC) are formulated, and the scope and target of a hardware component are discussed.\nCustomers, the design, planning, finance teams, and other key stakeholders are involved at this stage. 2. Design: Design stage gives a form to the ideas generated in the concept stage. This is the stage where prototypes of the concept are created with the help of different Computer Aided Design (CAD) tools and analysis of whether the goals identified during the concept stage are met. This stage also includes the use of third-party software and hardware prototyping. 3. Integration: Integration is the stage where different design components from designers and third parties are integrated together. This phase is crucial since many design elements already have tested solutions, so not everything needs to be created from the ground up. It is more feasible to purchase these solutions from third parties and integrate them into the design. 4. Manufacturing: After the IC's design is finished, the manufacturing phase begins. This stage includes several processes, including fabrication and packaging. Due to the high cost of building and maintaining manufacturing facilities, many design houses are fabless and outsource their designs to manufacturers located elsewhere. 5. Testing: Testing is the stage at which manufactured Integrated Circuits (ICs) are tested to ensure that they perform properly. Following the completion of fabrication, each IC undergoes testing. An IC's functionalities are tested here to make sure they adhere to design specifications. 6. Provisioning: Provisioning is the stage where standard and sensitive data are loaded into the manufactured IC. Standard data are generic and mostly available open source, but the sensitive data are anything whose disclosure would compromise IP or security."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.1 (NIST 3.7.1)?"}, {"role": "assistant", "content": "According to Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector:\n\n3.7.1."}], "metadata": {"source": "Protecting Information and System Integrity in Industrial Control System Environments_ Cybersecurity for the Manufacturing Sector", "cmmc_level": "all", "nist_control": "3.7.1", "cmmc_practice_id": "MA.L2-3.7.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.2.1 rsakpg2-basic ... 3.2.1 rsakpg2-basic\n\nrsakpg2-basic is the generator in the RSAKPG2 family such that the private key is in the basic format ( n , d ). 3.2.1) except that the private key is in the prime-factor format: ( p , q , d )."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Incident Response?"}, {"role": "assistant", "content": "According to Profile of the IoT Core Baseline for Consumer IoT Products:\n\nCybersecurity utility: The ability to identify IoT products and their components is necessary to support such activities as asset management for updates, data protection, and digital forensics capabilities for incident response. Cybersecurity utility: Protection of data and ensuring proper functionality can be supported by the ability to alert the customer when the device starts operating in unexpected ways, which could mean that unauthorized access is being attempted, malware has been loaded, botnets have been created, device software errors have happened, or other types of actions have occurred that was not initiated by the IoT product user or intended by the developer. 1. The IoT product developer creates awareness and provides education targeted at customers about information relevant to cybersecurity of the IoT product and its product components, including :\n- a. The presence and use of IoT product cybersecurity capabilities, including at a minimum :\n- i. How to change configuration settings and the cybersecurity implications of changing settings, if any. - ii. How to configure and use access control functionality (e.g., set and change passwords). - iii. How software updates are applied and any instructions necessary for the customer on how to use software update functionality. - iv. How to manage device data including creation, update, and deletion of data on the IoT product. - b. How to maintain the IoT product and its product components during its lifetime, including after the period of security support (e.g., delivery of software updates and patches) from the IoT product developer. - c. How an IoT product and its product components can be securely reprovisioned or disposed of. - d. Vulnerability management options (e.g., configuration and patch management and anti-malware) available for the IoT product or its product components that could be used by customers. - e."}], "metadata": {"source": "Profile of the IoT Core Baseline for Consumer IoT Products", "cmmc_level": "2", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness provide? (Part 9)"}, {"role": "assistant", "content": "an provide critical support for the cybersecurity of digital products. Notably, the capability can inform and educate users about other cybersecurity capabilities, particularly technical capabilities.\nFor example, cybersecurity education and awareness can guide users on creating strong access control credentials and permissions for products where such features are supported. Other information can be delivered using this capability as well, such as expectations for use of the product and other cybersecurity expectations, which can reduce the possibility of a risk being missed or otherwise unaddressed when the product is deployed. For more information about cybersecurity education and awareness, please see NIST Internal/Interagency Reports 8259 [2], 8259B [1], 8425 [3], 8425A [4], and NIST Special Publication 800-213A [5]. ## Human-Factors Considerations for Cybersecurity\n\nParticular care should be taken with the messaging and presentation of consumer education materials or users may not engage with or understand them. Users are more likely to read or interact with educational materials that are visually appealing or in alternative formats appropriate to the product (e.g., videos) [6]. Further, materials should be written in language that is understandable to a wide range of users, typically written at no more than an 8th grade reading level for adult users. Translations of education materials into common languages spoken across the customer base should be provided, as is the practice for US federal agencies\n\n[7]. Additionally, materials should meet accessibility 1 standards and guidance (e.g., Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act of 1973) to support users with disabilities."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.2.3. 3.2.3."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nSemiconductor-based hardware is the foundation of modern-day electronics - from smartphones, computers, and telecommunications to transportation and critical infrastructure. The semiconductor hardware supply chain is a complex network of companies that collectively provide intellectual property, designs, and raw materials and manufacture, test, package, and distribute products. Coordination among the components of a supply chain is required at different stages, including inception, deployment to end users, maintenance during use, and disposal or end of life. Securing semiconductor-based hardware and their supply chains help protect sensitive information, maintain the integrity of systems, and ensure overall stability across the infrastructure and connected world.\n\nThese activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "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 Contingency Planning Guide for Federal Information Systems provide? (Part 4)"}, {"role": "assistant", "content": "FISMA requires that federal agencies comply with these standards, agencies may not waive their use. - Guidance documents and recommendations are issued in the NIST Special Publication (SP) 800series.\nOffice of Management and Budget (OMB) policies (including OMB FISMA Reporting Instructions for the Federal Information Security Management Act and Agency Privacy Management) state that, for other than national security programs and systems, agencies must follow NIST guidance. 1\n- Other security-related publications, including NIST interagency and internal reports (NISTIRs) and ITL Bulletins, provide technical and other information about NIST's activities. These publications are mandatory only when so specified by OMB. 1 While agencies are required to follow NIST guidance in accordance with OMB policy, there is flexibility within NIST's guidance in how agencies apply the guidance. Unless otherwise specified by OMB, the 800-series guidance documents published by NIST generally allow agencies some latitude in the application. Consequently, the application of NIST guidance by agencies can result in different security solutions that are equally acceptable, compliant with the guidance, and meet the OMB definition of adequate security for federal information systems. When assessing federal agency compliance with NIST guidance, auditors, evaluators, and assessors should consider the intent of the security concepts and principles articulated within the particular guidance document and how the agency applied the guidance in the context of its specific mission responsibilities, operational environments, and unique organizational conditions. ## Acknowledgements\n\nThe authors, Marianne Swanson and Pauline Bowen of the National Institute of Standards and Technology (NIST), Amy Wohl Phillips, Dean Gallup, and David Lynes of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nThe enterprise architecture team should focus on identifying relevant business processes (workflows) and systems at the RMF mission/business level. A risk analysis should be done on each workflow including the possible impact of new operations or components added for the proposed ZTA. The owners and key personnel involved in the workflow should be identified and have input in the analysis, as they may have knowledge and experience about the workflows that deviate from existing workflow or system documentation. This maps to the organization and mission/business process level tasks (P-3 to P-7) of the PREPARE step (table 1 of NIST SP 80037r2) [2]. System administrators and operators should focus on identifying the resources that are used to conduct the identified business processes. This focus maps to the system level tasks (P-8 through P-18) of the PREPARE step (table 2 of NIST SP 800-37r2) [2]."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "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 Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide provide? (Part 10)"}, {"role": "assistant", "content": "ions Crosswalk........................105 |\n| Appendix E.\nNational Online Informative References (OLIR) Program..............................................106 |\n| Appendix F. HIPAA Security Rule Resources (Informative)...............................................................109 |\n| Appendix G. Change Log.................................................................................................................110 |\n| List of Tables |\n| Table 1. Security Rule standards and implementation specifications .................................................12 |\n| Table 2. Common threat sources ......................................................................................................17 |\n| Table 3. Assessment scale for overall likelihood................................................................................19 |\n| Table 4."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to 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 is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.1.1 rsakpg1 - basic ... 3.1.1 rsakpg1 -basic\n\nrsakpg1-basic is the generator in the RSAKPG1 family where the private key is in the basic format ( n , d ). 3.1.1) except that the private key is in the prime-factor format: ( p , q , d )."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for 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 additional guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 9)"}, {"role": "assistant", "content": "on Strategies . . . . . . . . . . . . . . . . . . . . . . . . 6.3. Authenticator Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4. Session Attacks . . . . . . . . . . . . . . . . . . .\n. . . . . . . . . . . . 7. Privacy Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1. 7.2. Privacy Risk Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . Privacy Controls\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3. Use Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4. Agency-Specific Privacy Compliance . . . . . . . . . . . . . . . . . . . . 8. Customer Experience Considerations\n\n. . . . . . . . . . . . . . . . . . . . . . 8.1. Usability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1. Common Usability Considerations for Authenticators . . . . . . . 8.1.2. Usability Considerations by Authenticator Type . . . . . . . . . . 8.1.3. Summary of Usability Considerations . . . . . . . . . . . . . . . 8.1.4. Usability Considerations for Biometrics . . . . . . . . . . . . . . 8.2. Customer Success Considerations . . . . . . . . . . . . . . . . . . . . . References\n\n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A. Strength of Passwords . . . . . . . . . . . . . . . . . . . . . . . . . A.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2. Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.3. Complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4. Central vs. Local Verification . . . . . . . . . . . . . . . . . . . . . . . . A.5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53\n\n53\n\n55\n\n55\n\n56\n\n57\n\n58\n\n58\n\n62\n\n65\n\n65\n\n66\n\n66\n\n66\n\n66\n\n67\n\n68\n\n68\n\n69\n\n71\n\n76\n\n76\n\n79\n\n81\n\n87\n\n87\n\n87\n\n88\n\n89\n\n90\n\nv\n\n\fNIST SP 800-63B-4\nJuly 2025\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nAppendix B."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental\norganizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\nNIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements\nNIST Technical Series Publication Identifier Syntax\n\n\fPublication History\n\nApproved by the NIST Editorial Review Board on 2025-05-30. Supersedes NIST SP 800-63B (June 2017; updated March 2, 2020) https://doi.org/10. 6028/NIST.SP.800-63b\n\nHow to Cite this NIST Technical Series Publication\n\nTemoshok D, Fenton JL, Choong YY, Lefkovitz N, Regenscheid A, Galluzzo R, Richer JP\n(2025) Digital Identity Guidelines: Authentication and Authenticator Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special\nPublication (SP) NIST SP 800-63B-4. https://doi.org/10.6028/NIST.SP.800-63B-4\n\nAuthor ORCID iDs\n\nDavid Temoshok: 0000-0001-6195-0331\nJames L. Fenton: 0000-0002-2344-4291\nYee-Yin Choong: 0000-0002-3889-6047\nNaomi Lefkovitz: 0000-0003-3777-3106\nAndrew Regenscheid: 0000-0002-3930-527X\nRyan Galluzzo: 0000-0003-0304-4239\nJustin P. Richer: 0000-0003-2130-5180\n\nContact Information\n\nmailto:dig-comments@nist.gov\n\nNational Institute of Standards and Technology\nAttn: Applied Cybersecurity Division, Information Technology Laboratory\n100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAdditional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/\nsp/800/63/B/4/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA)."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n. It also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones.\n| Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | Executive Summary................................................................................................................vii | |\n|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ...................................................................................................................... | 1. Introduction ...................................................................................................................... | 1."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nal requirements are listed for each section of the security policy, grouped by the source publication or document, and reference the specific section from the document where the requirement is stated.\nWhere possible, they are direct\n\n- Description - Description of the module\n- Purpose - The intended purpose or use of the module, including the intended use environment\n- Module Type - Hardware, software, firmware, or hybrid designation\n- Embodiment - Specific embodiment of the module (e.g., single-chip, multi-chip embedded, or multi-chip stand-alone) [Moved from Annex B Section 7]\n- Tested Operational Environment's Physical Perimeter (TOEPP) - Location of the cryptographic module with respect to the TOEPP that is part of the module's tested configuration but may be outside the module's cryptographic boundary so that all of the logical and physical layers between the cryptographic module and the TOEPP are clearly defined. This also includes a description and components list of the TOEPP. - TOEPP and Cryptographic Boundary - Precise definition of the module's TOEPP and cryptographic boundary\n- Diagram, Schematic, or Photograph - Illustrative diagram, schematic, or photograph of the module. If the security policy encompasses multiple versions of the module, each version is represented separately or annotated to note that the representation is illustrated for all versions. For a software, firmware, hybrid, or"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "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 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 is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n3.3.3 Other Considerations\n\nThis solution will aid in identifying the script that causes a configuration change or deletion, but ultimately some things cannot be automated by the solution."}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process provide?"}, {"role": "assistant", "content": "\n\n## NIST Internal Report NIST IR 8545\n\n## Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process\n\nGorjan Alagic\n\nMaxime Bros\n\nPierre Ciadoux\n\nDavid Cooper\n\nQuynh Dang\n\nThinh Dang\n\nJohn Kelsey\n\nJacob Lichtinger\n\nYi-Kai Liu\n\nCarl Miller\n\nDustin Moody\n\nRene Peralta\n\nRay Perlner\n\nAngela Robinson\n\nHamilton Silberg\n\nDaniel Smith-Tone\n\nNoah Waller\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8545\n\n\n\n## NIST Internal Report NIST IR 8545\n\n## Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process\n\nGorjan Alagic\n\nMaxime Bros\n\nPierre Ciadoux\n\nDavid Cooper\n\nQuynh Dang\n\nThinh Dang\n\nJohn Kelsey\n\nJacob Lichtinger\n\nCarl Miller\n\nDustin Moody\n\nRene Peralta\n\nRay Perlner\n\nAngela Robinson\n\nHamilton Silberg\n\nDaniel Smith-Tone\n\nNoah Waller\n\nComputer Security Division Information Technology Laboratory\n\nYi-Kai Liu\n\nApplied and Computational Mathematics Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8545\n\nMarch 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "Status Report on the Fourth Round of the NIST Post-Quantum Cryptography Standardization Process", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 A Data Structure for Integrity Protection with Erasure Capability provide? (Part 7)"}, {"role": "assistant", "content": "blockchains are designed to ensure that block contents are immutable. Any change in a blockchain will invalidate subsequent hashes in following blocks, losing integrity protection.\nThe data block matrix structure retains integrity protection of non-deleted blocks. Note that this data structure could also be extended beyond two dimensions to an arbitrary number of dimensions, with extensions to the algorithms above. ## ACKNOWLEDGMENTS\n\nMany thanks to Lee Badger, Jeff Voas, Sandy Ressler, Dylan Yaga, and Peter Mell for review and discussion of the original paper on this work. Thanks to Peter for suggesting the alternative of hashing a concatenation of block hashes. ## REFERENCES\n\n[1] D Richard Kuhn. A data structure for integrity protection with erasure capability. NIST Cybersecurity Whitepaper , 2018. ## NIST CSWP 25\n\n- [2] Matthias Berberich and Malgorzata Steiner. Blockchain technology and the gdpr-how to reconcile privacy and distributed ledgers. Eur. Data Prot. L. Rev. , 2:422, 2016. - [3] Henry Chang. Blockchain: Disrupting data protection? Privacy Law and Business International Report, November , 2017. - [4] O. Kharif. Is your blockchain doomed? Bloomberg Business Week, Mar. 22 , 2018."}], "metadata": {"source": "A Data Structure for Integrity Protection with Erasure Capability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 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 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 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 Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability provide? (Part 10)"}, {"role": "assistant", "content": "e United States National Vulnerability Database (NVD) provides information and references for all CVEs [8]. ## 2.2. Exploit Prediction Scoring System\n\nEPSS provides a daily updated score for each CVE.\nThese scores are estimated probabilities that each CVE will be observed to be exploited in the wild within the next 30 days. The EPSS scores are widely accepted by the security industry as shown by the scores being incorporated into 111 security products as of January 2025 [10]. However, security experts debate the pros and cons of using it (e.g., [11], [12]). The scores are created using a machine learning model trained with several thousand inputs. Training data is provided by a small number of enterprise security monitoring companies, each of which has a large, deployed sensor net to observe exploitation activity for their enterprise customers. Discussed more thoroughly in Sec. 5.1, EPSS was designed to not include past vulnerability exploitation as an input into its model. This makes the model blind to past exploitation, resulting in inaccurate scores (i.e., probabilities) for vulnerabilities that have been previously exploited. The scores will be too low. A vulnerability that is exploited in a 30-day period will NOT receive a bump up in EPSS score in the subsequent 30-day period. This is not an error as it enables the model to be predictive and have more accurate results for vulnerabilities that have not been previously exploited. EPSS version 1 was first released 2021-4-14; it was updated to version 2 on 2022-2-04. A much more accurate version 3 was released on 2023-3-07. A research paper explaining EPSS is available at [4]. ## 2.3. Known Exploited Vulnerability Lists\n\nKEV lists identify vulnerabilities that are known to have been exploited in the past. Typically, once a vulnerability is added to a KEV list, it stays on the list permanently. Vulnerabilities not on a list have an unknown status relative to past exploitation."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 9)"}, {"role": "assistant", "content": "transport layer interoperability, forces redundant posture information collection and evaluation that adds to system and network load, reduces modularity of solutions, and increases integration costs.\nDifficult Content Creation and Limited Content Availability: Development of content in SCAP v1 usually requires 1) familiarity with complex SCAP v1 languages; and 2) knowledge of the low-level system artifacts needed to direct collection and evaluate endpoint posture. Finding SCAP content developers that have the necessary skills and knowledge to do both can be challenging. This has increased the time and expense necessary to create content, causing limited content availability. Limited Software Inventory and Patch Support: In SCAP v1, the Common Platform Enumeration (CPE) [3] provides the ability to identify the software product vendor, name, and version, along with a limited set of additional metadata. Unfortunately, CPEs inadequately express granular metadata about software releases and version ranges needed to accurately identify vulnerable software. Another limitation of CPE is the inability to identify software patches, which further hampers software inventory and vulnerability management capabilities. A revised SCAP approach is needed to address these gaps. Such an effort is larger than what can be realistically accomplished in a minor SCAP v1 revision. Due to the scope of these changes, a major revision of SCAP, SCAP v2, is needed. ## 3 SCAP v2\n\nSCAP v2 is the next major release of SCAP. SCAP v2 will focus on addressing the SCAP v1 gaps identified in section 2. SCAP v.2 will continue to support the same use cases of SCAP v1 while also adding support for use cases not supported by SCAP v1. SCAP v2 will be developed iteratively. The first version of SCAP v2, SCAP 2.0, will focus on improving support for software inventory and vulnerability management use cases."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to 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 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 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 does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events:\n\n• Provides ability to enforce policy across the enterprise. • Provides ability to quarantine devices across the enter- prise. • Provides ability to sanitize files through file reconstruc- tion. • Provides ability to revert changes to domain services. | DE.CM-5, RS.RP-1, RS.MI-1, RS.MI-2 |\n| Reporting | Micro Focus ArcSight ESM v7.0 Patch 2 | • Provides ability to send security alerts based on organi- zational policy. • Provides ability to provide reports of enterprise health. • Provides ability to provide reports of malware detection across the enterprise. | DE.AE-5, RS.RP-1, RS.CO-2 |"}], "metadata": {"source": "Data Integrity_ Detecting and Responding to Ransomware and Other Destructive Events", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 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 require for Incident Response?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| | | requirements, as defined by the organization, throughout their life cycles."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls:\n\n3.1.3 | Vulnerabilities of Media | 6-7 |\n| | 3. 3.1.3 Threats from Within and Threats from Without | 3. 3.1.3)."}], "metadata": {"source": "Audit and Evaluation of Computer Security II_ System Vulnerabilities and Controls", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n3.1.2 | Obtaining Training Content... 3.1.2 Obtaining Training Content\n\nWe asked how the participant's organization obtained required security awareness training content (select all that apply) (see Figure 2)."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Overview and Considerations of Access Control Based on Attribute Encryption:\n\nSeptember 2023 INCLUDES UPDATES AS OF 12-20-2023; SEE APPENDIX A\n\nHu VC (2023) Overview and Considerations of Access Control Based on Attribute Encryption. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8450-upd1, Includes updates as of December 20, 2023. https://doi.org/10.6028/NIST.IR.8450-upd1\n\n| [SHINDE] | Shinde S (2020) Privacy Teaching Series: What is Functional Encryption? OpenMined Functional Encryption. Available at https://blog.openmined.org/privacy-teaching-series-what-is-functional-encryption |\n|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [SP800-162] | Hu VC, Ferraiolo D, Kuhn R, Schnitzer A, Sandlin K, Miller R, Scarfone K (2014) Guide to Attribute-Based Access Control (ABAC) Definition and Considerations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-162, Includes updates as of August 02, 2019. https://doi.org/10.6028/NIST.SP.800-162 |\n| [SP800-186] | Chen L, Moody D, Regenscheid AR, Robinson AY, Randall K (2023) Recommendations for Discrete Logarithm-based Cryptography: Elliptic Curve Domain Parameters. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-186. https://doi.org/10.6028/NIST.SP.800-186 |\n| [SP800-56A] | Barker EB, Chen L, Roginsky AL, Vassilev A, Davis R (2018) Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography."}], "metadata": {"source": "Overview and Considerations of Access Control Based on Attribute Encryption", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.5.2 of SP 800-63\n\n16."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Media Sanitization provide? (Part 5)"}, {"role": "assistant", "content": "------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2.\nBackground....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5. Traceability of CE Operations.....................................................................................................16 |\n| Media Sanitization Program .........................................................................................................18 |\n| 4. |\n| 4.3.1."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Access Control on NoSQL Databases provide? (Part 9)"}, {"role": "assistant", "content": "tructured data like documents, emails, and social media. NoSQL databases are particularly useful for managing unstructured or very large data objects stored across distributed and cooperating devices.\nUse cases for retrieving such data range from critical scenarios (e.g., storing financial data and healthcare records) to more casual applications (e.g., chat log data, video, and images, readings from smart devices). Major Web 2.0 companies have developed or adopted different flavors of NoSQL databases to meet their growing data and infrastructure needs. NoSQL database systems and data stores often outperform traditional RDBMS in various aspects, such as data analysis efficiency, system performance, ease of deployment, flexibility/scalability of data management, and users' availability. However, with an increasing number of people storing sensitive data in NoSQL databases, security issues have become critical concerns. NoSQL databases suffer from vulnerabilities, particularly due to the lack of effective support for data protection, including weak authorization mechanisms. As access control is a fundamental data protection requirement of any database management system (DBMS), this document discusses access control on NoSQL database systems by illustrating the NoSQL database types along with their support for access control models and describing considerations from the perspective of access control. ## 1. Introduction\n\nNoSQL stands for 'not only SQL' or 'non-SQL,' which typically refers to any non-relational database that stores data in a format other than relational tables. It emerged in the late 2000s, triggered by the growing popularity of distributed systems, such as cloud computing and big data, which required a shift away from relational databases (RDBMS) toward NoSQL databases."}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 8}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to 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 is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n3.4.2 | Intrusion Prevention Systems... 3.4.2 Intrusion Prevention Systems\n\nNetwork-based intrusion prevention systems (IPS) perform packet sniffing and analyze network traffic to identify and stop suspicious activity."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n## Secure Software Development Practices for Generative AI and Dual-Use Foundation Models\n\n## Secure Software Development Practices for Generative AI and Dual-Use Foundation Models\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF 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 Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 2)"}, {"role": "assistant", "content": "es even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nPrior industry surveys and research studies have revealed that organizational cybersecurity awareness (hereafter shortened to 'security awareness') programs may face a number of challenges, including lack of: leadership support; resources; and staff with sufficient background and skills to implement an effective and engaging program."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\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. - -Organizations should be prepared to shut down or block services used by malware to contain an incident and should understand the consequences of doing so. Organizations should also be prepared to respond to problems caused by other organizations disabling their own services in response to a malware incident. - -Organizations should be prepared to place additional temporary restrictions on network connectivity to contain a malware incident, such as suspending Internet access or physically disconnecting hosts from networks, recognizing the impact that the restrictions might have on organizational functions. -  Eradication. The primary goal of eradication is to remove malware from infected hosts. Because of the potential need for extensive eradication efforts, organizations should be prepared to use various combinations of eradication techniques simultaneously for different situations."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Validating the Integrity of Computing Devices provide? (Part 6)"}, {"role": "assistant", "content": "ompliance with any regulatory initiatives. Your organization's information security experts should identify the products that will best integrate with your existing tools and IT system infrastructure.\nYour organization can adopt this solution or one that adheres to these guidelines in whole, or you can use this guide as a starting point for tailoring and implementing parts of a solution. ## HOW TO USE THIS GUIDE\n\nDepending on your role in your organization, you might use this guide in different ways:\n\nBusiness decision makers, including chief information security and technology officers can use this part of the guide, NIST SP 1800-34a: Executive Summary , to understand the drivers for the guide, the cybersecurity challenge we address, our approach to solving this challenge, and how the solution could benefit your organization. Technology, security, and privacy program managers who are concerned with how to identify, understand, assess, and mitigate risk can use NIST SP 1800-34b: Approach, Architecture, and Security Characteristics . It describes what we built and why, including the risk analysis performed and the security/privacy control mappings. IT professionals who want to implement an approach like this can make use of NIST SP 1800-34c: HowTo Guides . It provides specific product installation, configuration, and integration instructions for building the example implementation, allowing you to replicate all or parts of this project. ## SHARE YOUR FEEDBACK\n\nYou can view or download the guide at https://www.nccoe.nist.gov/supply-chain-assurance. Help the NCCoE make this guide better by sharing your thoughts with us as you read the guide. If you adopt this solution for your own organization, please share your experience and advice with us."}], "metadata": {"source": "Validating the Integrity of Computing Devices", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 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 Workshop on Enhancing Security of Devices and Components Across the Supply Chain provide? (Part 10)"}, {"role": "assistant", "content": "tel's supply chain. Intel discovered that each of their teams approached the exercise of threat modeling in different ways, which made it difficult and time-consuming for them to exchange information.\nAs a result, Intel has been developing and deploying a unified Threat Modeling Tool that utilizes vulnerability resources like MITRE Common Weakness Enumeration (CWE) to automatically make design-based suggestions on potential vulnerabilities and mitigations. The tool also forms a closed loop that incorporates knowledge learned from Intel's own design processes. Matthew also described Intel's Transparent Supply Chain Initiative, whose goal is to provide customers with provenance and integrity data for various components during the supply chain process. He highlighted Project Amber - Intel's Trust Authority for validating execution environments. ## 2.1.2. Key Highlights\n\nThe following key points were identified during the speakers' presentations and the Q&A portion:\n\n- There is a definite need for continued public-private partnerships. - There is a need for more standards to guide how the supply chain process is structured. - There is a need for more standardized methods for threat modeling. - Quantifying the return on investment for security in the supply chain is still difficult, making it challenging for those who observe deficiencies to justify addressing them to higher-level management. Possible avenues of advancement include:\n- o Developing more standardized security metrics\n- o Continuing to leverage and develop CSF-style resources to better communicate risk\n- o Framing security as a service that can be used as a revenue stream\n\n- There is a tension between hardware security and software security due to the vastly different costs in remediating vulnerabilities at the hardware level. ## 2.2."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 9}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8.\nEvaluation (§ 164.308(a)(8)).......................................................................................................51 |\n| 5.2.1. Facility Access Controls (§ 164.310(a)).......................................................................................56 |\n| 5.1.9. Business Associate Contracts and Other Arrangements (§ 164.308(b)(1))................................54 |\n| 5.2.2. Workstation Use (§ 164.310(b)).................................................................................................59 |\n| 5.2.3. Workstation Security (§ 164.310(c)) ..........................................................................................61 |"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Access Control on NoSQL Databases:\n\n.....................................6 |\n| 2.2.4. Security Deficiencies.....................................................................................................................7 |\n| 3.\nAccess Control Model on NoSQL Database Systems.........................................................................8 |\n| 3.2.1. Key-Value Model ........................................................................................................................10 |\n| 3.2.2. Wide-Column and Document Models........................................................................................10 |\n| 3.2.3. Graph Model...............................................................................................................................12 |\n| 4. Considerations of Access Control for NoSQL Systems.....................................................................15 |\n| 5. Conclusion ...................................................................................................................................19 |\n| References.......................................................................................................................................20 |\n| Appendix A......................................................................................................................................22 |"}], "metadata": {"source": "Access Control on NoSQL Databases", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Media Protection?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n[SELECT FROM: maintenance policy and procedures; procedures for system maintenance tools; system maintenance tools; maintenance tool inspection records; equipment sanitization records; media sanitization records; system security plan; other relevant documents or records]\n\n[SELECT FROM: personnel with system maintenance responsibilities; personnel responsible for media sanitization; personnel with information security responsibilities]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\nns that a regulated entity must make regarding addressable implementation specifications, and requires the maintenance of security measures to continue reasonable and appropriate protection of ePHI\n2.\nAdministrative Safeguards - Defined in the Security Rule as the 'administrative actions and policies, and procedures to manage the selection, development, implementation, and maintenance of security measures to protect electronic protected health information and to manage the conduct of the covered entity's workforce in relation to the protection of that information'\n3. Physical Safeguards - Defined as the 'physical measures, policies, and procedures to protect a covered entity's electronic information systems and related buildings and equipment, from natural and environmental hazards, and unauthorized intrusion'"}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "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 Guidelines for the Use of PIV Credentials in Facility Access provide? (Part 8)"}, {"role": "assistant", "content": "d facilities. It does not address non-PIV credentials that may be issued to populations that do not fall under the scope of HSPD-12 but require access to federal facilities. ## Table of Contents\n\n| 1.\n| Introduction........................................................................................................................... 1 |\n|------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | Background....................................................................................................................1 |\n| 1.2 | Purpose and Scope.........................................................................................................1 |\n| 2. | Characteristics of PIV Implementations ............................................................................ 3 |\n| 2.1 | Benefits of the Complete Implementation.....................................................................3 |\n| 2.2 | Qualities of the Complete Implementation....................................................................4 |\n| 2.3 | Interoperability Qualities...............................................................................................5 |\n| 2.4 | Infrastructure Requirements ..........................................................................................6 |\n| 3. | Threat Environment............................................................................................................."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Access Control?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nT)\\_Security\\_and\\_Privacy\\_Recommendations.pdf\n- [7] Cloud Security Alliance (CSA) IoT Working Group (2015) Identity and Access Management for the Internet of Things. (Cloud Security Alliance [CSA]).\nhttps://cloudsecurityalliance.org/download/identity-and-access-management-for-the-iot/\n- [8] Council to Secure the Digital Economy (CSDE) (2019) The C2 Consensus on IoT Device Security Baseline Capabilities. (Council to Secure the Digital Economy [CSDE]). https://securingdigitaleconomy.org/wp-content/uploads/2019/09/CSDE\\_IoT-C2-Consensus-Report\\_FINAL.pdf\n- [9] CTIA (2018) CTIA Cybersecurity Certification Test Plan for IoT Devices, Version 1.0.1. (CTIA, Washington, DC). https://www.ctia.org/about-ctia/test-plans/\n- [10] European Union Agency for Network and Information Security (ENISA) (2017) Baseline Security Recommendations for IoT in the context of Critical Information Infrastructures. (European Union Agency for Network and Information Security [ENISA], Athens, Greece). https://www.enisa.europa.eu/publications/baseline-securityrecommendations-for-iot"}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Maintenance?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\n| | Time | Title | Speaker(s)/Facilitators | |-------------------|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| | 9:00AM - 9:15AM | Welcome, Agenda, Goals for the day | Michael Fagan, NIST | | 9:15AM - 9:55AM | Building More Secure Devices Using Threat Modeling with MITRE EMB3D | David Keppler, Senior Principal Cybersecurity Engineer, MITRE Jack Cyprus, Cybersecurity Engineer, MITRE | | 9:55AM - 10:35AM | Secure by Design considerations for OT | Matthew Rogers, Industrial Control System (ICS) Expert, CISA | | 10:35AM - 11:15AM | Life in Maintenance Mode: What it means to keep connected devices secure | Stacey Higginbotham, Policy Fellow at Consumer Reports | | 11:15AM - 11:55AM | Getting Smart: An Overview of IoT Privacy | Dylan Gilbert, Privacy Policy Advisor, NIST | | 11:55AM - 12:00PM | Closing of the Morning Hybrid Session | Michael Fagan, NIST | | 12:00PM - 1:00PM | Break | Break | | 1:00PM - 2:00PM | Discussion Session 1 - NIST IR 8259 Post-Market Activities update | Greg Witte, Palydin, Facilitator | | 2:00PM - 2:15PM | Break | Break | | 2:15PM - 3:15PM | Discussion Session 2 - NIST IR 8259 Pre-Market Activities | Christine Abruzzi, Cacapon Cyber Solutions, Facilitator | | 3:15PM"}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 7)"}, {"role": "assistant", "content": "reness positions; and advocate for federal security awareness professionals. The results may also be valuable to security awareness professionals outside of the government who face similar challenges.\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## PROFESSIONAL BACKGROUNDS, KNOWLEDGE, SKILLS, AND DEVELOPMENT ACTIVITIES\n\n## Table of Contents\n\n| EXECUTIVE SUMMARY........................................................................................................III | EXECUTIVE SUMMARY........................................................................................................III | EXECUTIVE SUMMARY........................................................................................................III |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 INTRODUCTION................................................................................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Security Assessment"], "type": "semantic_chunk", "chunk_id": 6}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to IoT Non-Technical Supporting Capability Core Baseline:\n\nory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nNon-technical supporting capabilities are actions a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device."}], "metadata": {"source": "IoT Non-Technical Supporting Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- Packet filters and network address translation: Packet filtering and Network address translation (NAT) are used to monitor and control packets moving across a network interface, apply predetermined security rules, and obscure the internal network from the public internet. - Stateful inspection: Stateful firewalling, also known as dynamic packet filtering, monitors the state of connections and makes determinations as to what types of data packets belong to a known active connection and can be allowed to pass through the firewall. - Deep packet inspection (DPI): This feature, also known as packet sniffing, examines the content of packets (both the header and the payload, unlike the stateful inspection that inspects only the packet header). In addition to the capability provided by stateful inspection, this has capabilities related to finding hidden threats within the data stream, such as attempts at data exfiltration, violations of content policies, malware, and more. - Threat detection and response: Modern firewalls can gather and analyze enough data across multiple packets and sessions to detect threats and security incidents targeted at a particular system or a family of systems. These data from multiple firewalls can also be directed toward security information and event management (SIEM) and correlated with data from other security tools and IT systems to detect enterprise-wide attacks that span multiple systems and network layers. In addition, these data can be used to understand evolving threats and define new access rules, attack patterns, and defensive strategies [6]. - Logging and auditing capabilities: Logging and auditing capabilities result in the construction of network events that can be used to identify patterns of performance and security issues. - Access control functions: Access control functions enforce granular sophisticated access control policies."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "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 High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nOften, the end users themselves best understand how to tune their software to the bespoke hardware of an HPC system to ensure sufficient performance for their workload. Users regularly modify and recompile their software to enhance performance, fix bugs, and adapt to changes in the underlying dependencies or kernel interfaces over time. The sharing of user-built software between teams may be common. User software that is widely used is often open source and, therefore, subject to open-source software supply chain concerns. - Tussles between performance and security: HPC users may consider security to be valuable only to the extent that it does not significantly slow down the HPC system and impede research. Ensuring the usability of security mechanisms with a tolerable performance penalty is therefore critical to adoption by the scientific HPC community. - Varying security requirements for different HPC applications: Individual platforms, projects, and data may have significantly different security sensitivities and need to follow different security policies. An HPC system may need to enforce multiple security policies simultaneously. - Limited resources for security tools: Most HPC systems are designed to devote their resources to maximizing performance rather than acquiring and operating security tools. - Open-source software and self-developed research software: Open-source software and self-developed research software are widely used in HPC. Open-source software is vulnerable to open-source software supply chain threats, while HPC software input data may be vulnerable to data supply chain threats. Self-developed software is susceptible to low software quality. - Granular access control on databases: Since different research groups may have a need to know for different portions of data, granular access control capabilities are necessary."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "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 Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\n| 100 | | 4.4.1 Primary Audit Objective of the Definition Phase | 4.4.1 Primary Audit Objective of the Definition Phase | 4.4.1 Primary Audit Objective of the Definition Phase | 100 | | 4.4.2 Overview of the Definition Phase | 4.4.2 Overview of the Definition Phase | 4.4.2 Overview of the Definition Phase | 100 | | 4.4.2.1 | Participants and Their Tasks | Participants and Their Tasks | 101 | | 4.4.2.2 | System Definition Phase Documents | System Definition Phase Documents | 102 | | 4.4.3 Audit Survey | 4.4.3 Audit Survey | 4.4.3 Audit Survey | 103 | | 4.4.3.1 | Review Initiation Phase Outputs | Review Initiation Phase Outputs | 104 | | 4.4.3.2 | Review Definition Phase Plans | Review Definition Phase Plans | 104 | | 4.4.3.3 | Gather Information on Definition Phase Status | Gather Information on Definition Phase Status | 104 | | 4.4.3.4 | Verify Information on Definition Phase Status | Verify Information on Definition Phase Status | 105 | | 4.4.3.4.1 | 4.4.3.4.1 | Review Documents | 105 | | 4.4.3.4.2 | 4.4.3.4.2 | Interview Key Participants | 106 | | 4.4.4 Customize Audit Objectives | 4.4.4 Customize Audit"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nontaining sensitive data that leave an organization without effective sanitization expose a significant vulnerability to 'dumpster divers' and overcurious employees. - Information storage media (ISM).\nISM commonly 2 takes the form of:\n- o Devices that contain bits and bytes, such as hard disk drives (HDDs), solid state drives (SSDs), random access memory (RAM), read-only memory (ROM), optical disks, magnetic tape, flash memory, memory devices, phones, mobile computing devices, networking devices, and office equipment\n- o Systems that provide 'virtual' or 'logical' storage that abstracts the underlying electronic media (e.g., cloud storage, object storage)\n\nSome types of ISM can contain more physical storage than the user addressable capacity (e.g., overprovisioning) for endurance and performance purposes. For example, an ISM can have 1024 GB of total physical capacity but only 900 GB of available capacity (i.e., user accessible storage). If the ISM implements data reduction techniques (e.g., data compression) internally, it is also possible for the user-addressable capacity to exceed the total physical capacity. In either case, user data may be stored on the full 1024 GB because of the mechanisms in the ISM, and the entire contents should be sanitized."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 require for Configuration Management?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\n- Illustrative diagram, schematic, or photograph of the module. A photograph included for hardware modules. If the security policy encompasses multiple versions of the module, each version is represented separately or annotated that the representation is illustrated for all versions. For a software or , firmware, hybrid, or sub-chip cryptographic module, the security policy includes a block diagram that illustrates:\n- o The location of the logical object of the software or firmware module with respect to the operating system, other supporting applications, and the cryptographic boundary so that all of the logical and physical layers between the logical object and the cryptographic boundary are clearly defined and\n- o The interactions of the logical object of the software or firmware module with the operating system and other supporting applications resident within the cryptographic boundary. - o Tested Operational Environment's Physical Perimeter (TOEPP) - The location of the cryptographic module with respect to the TOEPP that is part of the module's tested configuration but may be outside of the module's cryptographic boundary so that all of the logical and physical layers between the cryptographic module and the TOEPP are clearly defined. This also includes a description and components list of the TOEPP. - Precise definition of the module's physical TOEPP and cryptographic boundariesy\n\nIn addition to ISO/IEC 24759 Section 6.14 and ISO/IEC 19790 Annex B, other publications and documents specify the documentation requirements for the security policy. Many of these requirements relate to the specific conditions and configurations of modules and would not be applicable in many cases. These additional requirements are listed for each section of the security policy, grouped by the source publication or document, and reference the specific section from the document where the requirement is stated."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”:\n\nSecurity is a collective responsibility involving manufacturers, integrators, and asset owners and operators. CISA helps clarify security roles and ensures all parties uphold their responsibilities. The key component of secure by design is seeing where manufacturers can embed cyber security from the start to make it more difficult or impossible for an integrator or asset owner to open a cyber security risk. Current US critical infrastructure contains legacy systems without security functionality that inherently complicate adding security today. Infrastructure improvement options include the present 'Bubble Boy' method, which segments all traffic, ta rgeted improvements, and the 'rip and replace' method. Secure operational technology (OT) devices need to be available to provide that defense in depth, so that any failures in segmentation do not result in total data protection. It emphasizes open standards and autonomy at the asset and operator level. Resilience features should resemble those in the enterprise space, including secure compromise. Secure-by-design for OT considers threat categories like vulnerability handling and communications, resilience, logging, and end-device capabilities. Instead, participants recommended that the government could provide top-level support for broader cybersecurity objectives, integrating planning approaches to navigate the complexities of different sectors. Tools like effective consumer education awareness campaigns may drive better security practices to ensure consumers are well-informed about cybersecurity measures as they evolve. Participants agreed that one key aspect of government involvement is effective communication, which the participants agreed should be action-based messages directed at consumers. For example, simplifying communication and facilitating customer outreach are ways to promote awareness and understanding of cybersecurity practices."}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study provide? (Part 6)"}, {"role": "assistant", "content": "............................................................ 4 | 2.2 SURVEY METHODOLOGY .....................................................................................................\n4 |\n| 2.2.1 | Survey Design | ............................................................................................................. 4 |\n| 2.2.2 | Survey Recruitment ..................................................................................................... | 5 |\n| 2.2.3 | Survey Data Collection............................................................................................... | 6 |\n| 2.2.4 | Survey Data Analysis .................................................................................................."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 5}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach provide? (Part 3)"}, {"role": "assistant", "content": "n activities; provides scientific and technological advisory services and assistance to Federal agencies; and provides the technical foundation for computer-related policies of the Federal Government.\nThe Institute consists of the following divisions:\n\n## The Institute for Materials Science and Engineering\n\nConducts research and provides measurements, data, standards, reference materials, quantitative understanding and other technical information fundamental to the processing, structure, properties and performance of materials; addresses the scientific basis for new advanced materials technologies; plans research around cross-cutting scientific themes such as nondestructive evaluation and phase diagram development; oversees Bureau-wide technical programs in nuclear reactor radiation research and nondestructive evaluation; and broadly disseminates generic technical information resulting from its programs. The Institute consists of the following Divisions:\n\n'Headquarters and Laboratories at Gaithersburg, MD, unless otherwise noted; mailing address Gaithersburg, MD 20899. ^Some divisions within the center are located at Boulder, CO 80303. ^Located at Boulder, CO, with some elements at Gaithersburg, MD\n\n- Basic Standards^\n- Radiation Research\n- Chemical Physics\n- Analytical Chemistry\n- Applied Mathematics\n- Electronics and Electrical Engineering^\n- Manufacturing Engineering\n- Building Technology\n- Fire Research\n- Chemical Engineering^\n- Information Systems Engineering\n- Systems and Software Technology\n- Computer Security\n- Systems and Network Architecture\n- Advanced Computer Systems\n- Ceramics\n- Fracture and Deformation^\n- Polymers\n- Metallurgy\n- Reactor Radiation\n\n## Computer Science and Technology\n\nNBS Special Publication 500-153\n\n## Guide to Auditing for Controls and Security: A System Development Life Cycle Approach\n\nEditors/Authors:\n\nZella G. Ruthberg\n\nBonnie T. Fisher\n\nWilliam E' Perry\n\nJohn W. Lainhart SV\n\nJames G. Cox\n\n'\n\nMark Gillen\n\nDouglas B."}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n3.4.3e Employ automated discovery and management tools to maintain an up-to-date, complete, accurate, and readily available inventory of system components. 3.4.3. 3.4.3e | Employ automated discovery and management tools to maintain an up-to-date, complete, accurate, and readily available inventory of system components."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for 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 does CMMC Level 1 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n259 and this publication have manufacturers as the intended audience, the considerations and capabilities discussed across the two publications can be used by manufacturers, integrators, or consumers.\nFor more information on how these capabilities can be incorporated into a manufacturer's development processes, see NISTIR 8259. Other organizations can use the core baseline in the context that is available and appropriate to them."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n3.2.2 | Organization Size... 3.2.2 Organization Size\n\nOrganization size was determined by the number of federal employees."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "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 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 require for Planning?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nhosts. Because of the potential need for extensive eradication efforts, organizations should be prepared to use various combinations of eradication techniques simultaneously for different situations.\nOrganizations should also consider performing awareness activities that set expectations for eradication and recovery efforts; these activities can be helpful in reducing the stress that major malware incidents can cause. -  Recovery. The two main aspects of recovery from malware incidents are restoring the functionality and data of infected hosts and removing temporary containment measures. Organizations should carefully consider possible worst-case scenarios and determine how recovery should be performed, including rebuilding compromised hosts from scratch or known good backups. Determining when to remove temporary containment measures, such as suspension of services or connectivity, is often a difficult decision during major malware incidents. Incident response teams should strive to keep containment measures in place until the estimated number of infected hosts and hosts vulnerable to infection is sufficiently low that subsequent incidents should be of little consequence. However, even though the incident response team should assess the risks of restoring services or connectivity, management ultimately should be responsible for determining what should be done based on the incident response team's recommendations and management's understanding of the business impact of maintaining the containment measures. -  Post-Incident Activity. Because the handling of malware incidents can be extremely expensive, it is particularly important for organizations to conduct a robust assessment of lessons learned after major malware incidents to prevent similar incidents from occurring."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "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 Incident Response?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nAn attacker may develop Stuxnet-like malware [2], featuring zero-day exploits, rootkits, anti-virus evasion techniques, and process injection and hooking code, to target a specific process step within the entire chip manufacturing process. Industrial control systems (ICS) are rapidly becoming a new major target of cyber-criminals. This was pointed out in multiple occasions by security experts [1], [2] and was confirmed by a recent survey carried out by Symantec [3]. In this survey, 53% of the 1580 critical infrastructure companies that were interviewed admitted to having been targeted by cyber attacks. On average, the surveyed companies admitted to having been attacked 10 times in the last 5 years, with each of these attacks having an average cost of 850k USD. The survey provides a basis for a quantitative estimate of the extent of the problem and implies that the incidents reported by the press over the last several years are nothing but the tip of a considerably larger problem: the vast majority of incidents have never been disclosed. Still, the details of the publicly disclosed incidents give us a better understanding of the underlying issues we face. For instance, a recently discovered malware variant called Stuxnet which has been analyzed at length by Symantec [4] was shown to be part of a highly sophisticated targeted attack aiming at tampering with devices involved in the control of high speed engines, and compromise the associated industrial process [5]. The infection was only uncovered accidentally when an operational anomaly was discovered Stuxnet has probably been operating undetected since June of 2009 [6]. Stuxnet, and other related threats discovered recently [7], show that industrial control systems are evolving, bringing powerful capabilities into the critical infrastructure environment along with new and yet undiscovered threats."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development” provide? (Part 8)"}, {"role": "assistant", "content": "Table 2 - Agenda for the Workshop | Time | Title | Speaker(s)/Facilitators | |-------------------|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| | 9:00AM - 9:15AM | Welcome, Agenda, Goals for the day | Michael Fagan, NIST | | 9:15AM - 9:55AM | Building More Secure Devices Using Threat Modeling with MITRE EMB3D | David Keppler, Senior Principal Cybersecurity Engineer, MITRE Jack Cyprus, Cybersecurity Engineer, MITRE | | 9:55AM - 10:35AM | Secure by Design considerations for OT | Matthew Rogers, Industrial Control System (ICS) Expert, CISA | | 10:35AM - 11:15AM | Life in Maintenance Mode: What it means to keep connected devices secure | Stacey Higginbotham, Policy Fellow at Consumer Reports | | 11:15AM - 11:55AM | Getting Smart: An Overview of IoT Privacy | Dylan Gilbert, Privacy Policy Advisor, NIST | | 11:55AM - 12:00PM | Closing of the Morning Hybrid Session | Michael Fagan, NIST | | 12:00PM - 1:00PM | Break | Break | | 1:00PM - 2:00PM | Discussion Session 1 - NIST IR 8259 Post-Market Activities update | Greg Witte, Palydin, Facilitator | | 2:00PM - 2:15PM | Break | Break | | 2:15PM - 3:15PM | Discussion Session 2 - NIST IR 8259 Pre-Market Activities | Christine Abruzzi, Cacapon"}], "metadata": {"source": "Summary Report for “Workshop on Updating Manufacturer Guidance for Securable Connected Product Development”", "cmmc_level": "1", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 7}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\n|\n| 1.3 ORGANIZATION OF DOCUMENT..................................................................................................\n| 1 |\n| 1.4 SYSTEMS INVENTORY AND FEDERAL INFORMATION PROCESSING STANDARDS (FIPS 199) | ...... 2 |\n| 1.5 MAJOR APPLICATIONS, GENERAL SUPPORT SYSTEMS, AND MINOR APPLICATIONS | .................. 2 |\n| 1.6 OTHER RELATED NIST PUBLICATIONS ..................................................................................... | 3 |\n| 1.7 SYSTEM SECURITY PLAN RESPONSIBILITIES .............................................................................. | 3 |\n| 1.7.1 Chief Information Officer ................................................................................................ | 4 |\n| 1.7.2 Information System Owner | ..............................................................................................."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach:\n\nhe development of software could be discussed, identified a Development Phase including four stages -definition, design, programming, and testing. These are represented by Phases II-V described above.\nDuring the Development Phase the requirements for software are determined and the software is then defined, specified, programmed, and tested. Documentation is prepared within this phase to provide an adequate record of the technical information developed. The PCIE Work Group's phases are intended to cover not only softwcu-e but also hardware, telecommunications, etc., i.e., all the components of an automated information system"}], "metadata": {"source": "Guide to Auditing for Controls and Security_ A System Development Life Cycle Approach", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication NIST SP 800-140Dr2\n\n## Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods:\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nAlexander Calis\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-140Dr2\n\n\n\n## NIST Special Publication NIST SP 800-140Dr2\n\n## Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods:\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nAlexander Calis\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-140Dr2\n\nJuly 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Audit and Accountability", "System and Information Integrity", "Security Assessment", "Media Protection", "Identification and Authentication", "Awareness and Training", "System and Communications Protection", "Access Control", "Planning", "Incident Response", "Risk Assessment", "Personnel Security", "System and Services Acquisition", "Supply Chain Risk Management", "Maintenance", "Physical Protection", "Configuration Management"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nyland), NIST Special Publication (SP) 800-56C, Rev. 1, April 2018. https://doi.org/10.6028/NIST.SP.800-56Cr1\n- [SP 800-57] Barker EB (2016) Recommendation for Key Management, Part 1: General .\n(National Institute of Standards and Technology, Gaithersburg, Maryland), NIST Special Publication (SP) 800-57 Part 1, Rev. 4, January 2016. https://doi.org/10.6028/NIST.SP.800-57pt1r4\n- [SP 800-89] Barker EB (2006) Recommendation for Obtaining Assurances for Digital Signature Applications . (National Institute of Standards and Technology, Gaithersburg, Maryland), NIST Special Publication (SP) 800-89, November 2006. https://doi.org/10.6028/NIST.SP.800-89"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}}